Search results

There is a page named "Features/" on QEMU. See also the other search results found.

Page title matches

  • * [{{PagesStartingWith|Features/}} All feature pages] * [[Features/COLO|COLO]]
    701 bytes (79 words) - 12:20, 17 January 2018
  • {{Special:PrefixIndex/Features/}}
    33 bytes (3 words) - 07:29, 19 March 2018
  • 758 bytes (111 words) - 14:43, 11 October 2016
  • 3 KB (434 words) - 13:35, 22 October 2018
  • ...s an attempt at creating a better performing image format by removing some features compared to qcow2. However, it turned out that the achieved performance imp ...converting to qcow2 should be considered as today qcow2 provides both more features and better performance, and has an actively maintained code base.
    2 KB (241 words) - 14:42, 16 October 2017
  • 15 KB (2,145 words) - 12:38, 22 March 2022
  • 8 KB (1,370 words) - 14:10, 18 February 2013
  • Proposed New Design Features:
    4 KB (709 words) - 18:15, 14 September 2016
  • HVF is mostly stable but some features are missing:
    467 bytes (67 words) - 19:16, 5 June 2020
  • ...It should integrate into the existing build system. Currently, we allow features to be specified in for inclusion in a boolean fashion (either 'y' or 'n' to ...mechanism to support third party extensions to QEMU or out of tree drivers/features
    9 KB (1,464 words) - 19:33, 11 August 2016
  • 911 bytes (141 words) - 14:50, 11 October 2016
  • Read [[Features/FVD/WhyFVD | Why FVD]]. Read [[Features/FVD/Design | How FVD Works]].
    2 KB (241 words) - 14:45, 11 October 2016
  • 542 bytes (73 words) - 15:01, 11 October 2016
  • 4 KB (531 words) - 14:54, 11 October 2016
  • The information about removed features has been integrated into the main QEMU documentation now. Please see this p https://www.qemu.org/docs/master/about/removed-features.html
    197 bytes (30 words) - 05:41, 18 August 2021
  • mainline QEMU (hopefully 0.14) to provide a basic set of Kemari features.
    4 KB (636 words) - 14:45, 11 October 2016
  • 4 KB (694 words) - 09:21, 5 January 2024
  • ...le that allows a user space program to utilize the hardware virtualization features of various processors. Today, it supports recent Intel and AMD processors
    847 bytes (133 words) - 12:11, 6 February 2017
  • 1 KB (136 words) - 14:51, 11 October 2016
  • 9 KB (1,482 words) - 02:20, 17 September 2011
  • In terms of features the SoftMMU is the mechanism by which the TCG allows the emulation of virtu
    1 KB (181 words) - 12:14, 17 January 2018
  • 2 KB (379 words) - 14:54, 11 October 2016
  • 6 KB (864 words) - 14:56, 11 October 2016
  • = Features = * [[Features/VirtioSCSI/TCM Overview|In-kernel SCSI target overview]]
    2 KB (303 words) - 15:39, 11 October 2016
  • When using [[Features/TCG|TCG]] emulation we need emulate the floating point unit of the guest. T [[Category:Completed Features]]
    1 KB (218 words) - 10:01, 27 June 2019
  • 7 KB (1,041 words) - 12:40, 22 March 2022
  • Note 1: KQEMU does not currently use the hardware virtualization features of newer x86 CPUs. We expect that the limitations would be different in tha
    16 KB (2,703 words) - 15:57, 11 October 2016
  • ...QAPI/GuestAgent Guest Agent]. Please check the guest [http://wiki.qemu.org/Features/QAPI/GuestAgent Guest Agent] page for design and implementation details. The two main guest agent features of interest to live snapshots are:
    21 KB (3,274 words) - 14:58, 11 October 2016
  • 7 KB (996 words) - 14:56, 11 October 2016
  • to postcopy and is designed to allow use with all of the standard kernel features (like transparent huge pages, KSM etc). Where possible the design attempts to build reusable components that other features can reuse.
    6 KB (885 words) - 12:28, 16 March 2017
  • #REDIRECT [[Features/tcg-multithread]]
    38 bytes (3 words) - 14:49, 29 June 2017
  • 861 bytes (130 words) - 14:59, 9 July 2020
  • See the [[Features/VirtIORNG | Virtio-RNG]] page for other examples of specifying RngBackends.
    3 KB (408 words) - 16:07, 17 October 2016
  • 2 KB (256 words) - 09:25, 10 July 2019
  • 3 KB (484 words) - 14:43, 11 October 2016
  • More detail: [[Features/Real rng device]] * [https://fedoraproject.org/wiki/Features/Virtio_RNG Fedora Feature Page]
    6 KB (994 words) - 16:08, 17 October 2016
  • ; QEMU User-mode Emulation User's Guide (docs/user, [[Features/Documentation/user]]) ; QEMU System Emulation User's Guide (docs/system, [[Features/Documentation/system]])
    11 KB (1,827 words) - 15:38, 31 March 2020
  • For the rationale behind the conversion and the development notes, see [[Features/Meson/Design]]. === Other features===
    8 KB (1,292 words) - 17:57, 18 May 2023
  • 2 KB (366 words) - 14:55, 11 October 2016
  • == Other proposed qemu features that solve the same problem == [http://wiki.qemu.org/Features/Snapshots snapshots]<br>
    4 KB (663 words) - 14:43, 11 October 2016
  • ...a 'set-migration-capabilities' command that can mask some of the supported features. A management tool would query-migration features on the source and destination, take the intersection of the two masks, and
    5 KB (812 words) - 23:50, 25 July 2011
  • 3 KB (455 words) - 08:09, 13 October 2016
  • ...the internal implementation of QMP to simplify maintainability and enable features such as asynchronous command completion and rich error reporting. Minimize
    16 KB (2,377 words) - 18:10, 2 April 2015
  • 20 KB (2,929 words) - 12:14, 12 October 2016
  • 950 bytes (139 words) - 16:58, 10 November 2016
  • The gdbstub doesn't support all the features of the gdbserver protocol which is documented [https://sourceware.org/gdb/o
    687 bytes (102 words) - 12:44, 20 May 2019
  • 8 KB (1,149 words) - 15:59, 17 October 2016
  • 204 bytes (33 words) - 08:10, 16 July 2020
  • #REDIRECT [[Features/Meson]]
    28 bytes (3 words) - 15:03, 21 August 2020
  • 2 KB (358 words) - 14:45, 11 October 2016
  • 374 bytes (54 words) - 13:44, 9 July 2020
  • An alternative implementation has been merged in QEMU 2.5: [[Features/PostCopyLiveMigration]]
    3 KB (432 words) - 06:04, 25 November 2015
  • * COLO Block Replication (Please refer to [http://wiki.qemu.org/Features/BlockReplication BlockReplication]) For automatically managed colo: [[Features/COLO/Managed HOWTO]]
    16 KB (1,321 words) - 18:38, 30 January 2023
  • ...ecation chapter (see https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features for details)
    2 KB (354 words) - 16:20, 27 April 2018
  • * [[Features/Tracing/Roadmap|Roadmap]]
    1 KB (159 words) - 15:48, 24 February 2021
  • 465 bytes (58 words) - 21:04, 23 August 2019
  • 2 KB (378 words) - 14:52, 11 October 2016
  • 7 KB (1,068 words) - 09:21, 25 January 2013
  • 2 KB (353 words) - 17:48, 15 April 2020
  • * [[Features/Usability]]
    2 KB (314 words) - 14:54, 11 October 2016
  • 527 bytes (77 words) - 15:01, 11 October 2016
  • 2 KB (306 words) - 04:52, 24 June 2013
  • 10 KB (1,240 words) - 06:29, 17 August 2016
  • * [https://clearlinux.org/features/clear-containers Clear Containers] - kvmtool-based KVM containers implement
    2 KB (372 words) - 10:10, 22 March 2016
  • | '''6 - Add a fast path when QEMU block layer features are not in use .'''
    2 KB (234 words) - 18:17, 23 May 2019
  • 20 KB (3,092 words) - 14:55, 11 October 2016
  • ...es) which are considered as deprecated since other more generic interfaces/features have been established instead. We cannot carry the old code around forever. This page was used to gather ideas about such deprecated features and interfaces, which finally culminated in the official deprecation chapte
    969 bytes (153 words) - 10:45, 4 August 2021
  • ...rectly modeling this interaction is necessary to properly support advanced features like PCI IOMMUs and also to support PCI-based endian conversion in a more r ...virtio uses different memory access functions to manipulate the ring. [[Features/RamAPI|RamAPI]] would simplify the implementation by allowing the virtio ri
    2 KB (263 words) - 14:45, 11 October 2016
  • ...ions and get it into usable state, as basis for [[Features/40p|40p]] and [[Features/BeBox|BeBox]] emulation.
    688 bytes (105 words) - 14:52, 9 July 2020
  • 8 KB (1,395 words) - 15:25, 16 April 2012
  • ...he two parts above, e.g. link script to generate flat image. Some specific features will be listed here. ...e mini hypervisor neeeded in this project doesn't need so many complicated features (e.g. Buddy system). Only CPU management, memory management, interrupt cont
    6 KB (976 words) - 15:40, 11 October 2016
  • 1 KB (180 words) - 15:15, 11 October 2016
  • 8 KB (1,079 words) - 17:00, 1 February 2023
  • 3 KB (482 words) - 15:36, 12 April 2022
  • The [[Features/IncrementalBackup|Incremental Backup]] feature was merged into QEMU instead ...the old feature proposal, please see [http://wiki.qemu.org/index.php?title=Features/Livebackup&oldid=1188 Livebackup (2011-05-09)]'''
    467 bytes (65 words) - 15:00, 11 October 2016
  • 4 KB (549 words) - 12:39, 22 March 2022
  • #REDIRECT [[Features/LegacyRemoval]]
    36 bytes (3 words) - 11:15, 8 March 2017
  • 7 KB (902 words) - 17:35, 12 April 2022
  • 1 KB (204 words) - 14:43, 11 October 2016
  • 2 KB (271 words) - 12:56, 10 July 2020
  • 1 KB (152 words) - 15:37, 11 October 2016
  • 1 KB (219 words) - 15:36, 11 October 2016
  • There are several features still pending:
    26 KB (4,022 words) - 16:28, 16 July 2019
  • 1 KB (149 words) - 15:01, 11 October 2016
  • 6 KB (948 words) - 11:23, 3 June 2016
  • 1 KB (192 words) - 14:54, 11 October 2016
  • Future qemu is expected to support these features (some already implemented): = Live features =
    21 KB (3,397 words) - 15:04, 11 October 2016
  • 8 KB (1,143 words) - 11:04, 12 April 2023
  • ...oleted by <tt>query-cpu-model-expansion</tt> QMP commands and <tt>filtered-features</tt> property ** Actually, the new mechanism is based on the "filtered-features" X86CPU property
    15 KB (2,336 words) - 13:50, 30 October 2017
  • 1 KB (181 words) - 13:57, 9 March 2020
  • feature. See [[Features/ACPITableGeneration|Features/ACPITableGeneration]]
    1 KB (194 words) - 15:41, 11 October 2016
  • 12 KB (1,604 words) - 15:26, 11 October 2016
  • features that change the format in an incompatible way, so that older increase in order to introduce some incompatible features, however it's
    9 KB (1,281 words) - 10:12, 9 September 2016
  • 860 bytes (138 words) - 14:50, 11 October 2016
  • 891 bytes (139 words) - 07:15, 5 February 2020
  • ...scales to several hundreds nodes, and supports advanced volume management features such as snapshot, cloning, and thin provisioning. ...no central node such as a meta-data server. This design enables following features.
    2 KB (247 words) - 14:55, 11 October 2016
  • * [[Features/DiskIOLimits/Requirements|Requirements]] * [[Features/DiskIOLimits/TestCases|Test cases]]
    1 KB (211 words) - 14:54, 11 October 2016
  • Wiki: [http://wiki.qemu.org/Features/MicroCheckpointing http://wiki.qemu.org/Features/MicroCheckpointing]
    25 KB (4,019 words) - 14:39, 20 July 2015
  • 724 bytes (116 words) - 14:54, 11 October 2016
  • 1 KB (216 words) - 01:45, 13 March 2019

Page text matches

  • * [{{PagesStartingWith|Features/}} All feature pages] * [[Features/COLO|COLO]]
    701 bytes (79 words) - 12:20, 17 January 2018
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should have initial code committed by this date. == Targeted Features ==
    898 bytes (130 words) - 15:38, 11 October 2016
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. All features should have patches on the list by this date; major features should
    882 bytes (126 words) - 16:12, 21 October 2015
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should have initial code committed by this date. == Targeted Features ==
    761 bytes (113 words) - 07:37, 4 November 2011
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. All features should have patches on the list by this date; major features should
    852 bytes (125 words) - 08:31, 12 October 2016
  • ...s an attempt at creating a better performing image format by removing some features compared to qcow2. However, it turned out that the achieved performance imp ...converting to qcow2 should be considered as today qcow2 provides both more features and better performance, and has an actively maintained code base.
    2 KB (241 words) - 14:42, 16 October 2017
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. All features should have patches on the list by this date; major features should
    931 bytes (133 words) - 11:24, 30 July 2015
  • ...es) which are considered as deprecated since other more generic interfaces/features have been established instead. We cannot carry the old code around forever. This page was used to gather ideas about such deprecated features and interfaces, which finally culminated in the official deprecation chapte
    969 bytes (153 words) - 10:45, 4 August 2021
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. All features should have patches on the list by this date; major features should
    949 bytes (134 words) - 20:30, 6 August 2014
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should have initial code committed by this date. == Targeted Features ==
    1 KB (159 words) - 15:38, 11 October 2016
  • ...reeze]]. All features should have patches on the list by this date; major features should have initial code committed. == Targeted Features ==
    986 bytes (138 words) - 16:58, 8 July 2014
  • {{Special:PrefixIndex/Features/}}
    33 bytes (3 words) - 07:29, 19 March 2018
  • #REDIRECT [[Features/LegacyRemoval]]
    36 bytes (3 words) - 11:15, 8 March 2017
  • #REDIRECT [[Features/Meson]]
    28 bytes (3 words) - 15:03, 21 August 2020
  • #REDIRECT [[Features/Documentation/specs]]
    42 bytes (4 words) - 15:26, 6 June 2017
  • #REDIRECT [[Features/tcg-multithread]]
    38 bytes (3 words) - 14:49, 29 June 2017
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should have initial code committed by this date. == Targeted Features ==
    898 bytes (128 words) - 10:34, 12 October 2016
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should have initial code committed by this date. == Targeted Features ==
    991 bytes (144 words) - 08:31, 12 October 2016
  • == Targeted Features ==
    896 bytes (128 words) - 15:28, 15 April 2024
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should have initial code committed by this date. == Targeted Features ==
    1 KB (162 words) - 00:32, 4 December 2013
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. All features should have patches on the list by this date; major features should
    1 KB (209 words) - 08:31, 12 October 2016
  • == Targeted Features ==
    966 bytes (145 words) - 09:28, 23 April 2024
  • Read [[Features/FVD/WhyFVD | Why FVD]]. Read [[Features/FVD/Design | How FVD Works]].
    2 KB (241 words) - 14:45, 11 October 2016
  • The information about removed features has been integrated into the main QEMU documentation now. Please see this p https://www.qemu.org/docs/master/about/removed-features.html
    197 bytes (30 words) - 05:41, 18 August 2021
  • ...ions and get it into usable state, as basis for [[Features/40p|40p]] and [[Features/BeBox|BeBox]] emulation.
    688 bytes (105 words) - 14:52, 9 July 2020
  • '''Summary:''' Fix bugs and add extra features for QEMU's emulation of AMD virtualization instructions. * adding support for new features such as vGIF or vVMLOAD/vVMSAVE
    810 bytes (108 words) - 10:16, 9 February 2021
  • == Targeted Features ==
    1 KB (189 words) - 03:48, 16 April 2024
  • | Soft feature freeze. Major features should have initial code committed by this date. = Merged Features =
    2 KB (231 words) - 21:37, 4 August 2011
  • == Targeted Features ==
    1 KB (212 words) - 20:19, 18 January 2024
  • QEMU features are classified into a number of support tiers, which serve as guidance to u These are the top class features, suitable for use in a virtualization scenario and expected to be fully fun
    3 KB (405 words) - 12:12, 4 November 2020
  • == Targeted Features ==
    1 KB (209 words) - 20:51, 3 September 2020
  • == Targeted Features ==
    2 KB (247 words) - 12:54, 18 January 2024
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should have initial code committed by this date. == Targeted Features ==
    959 bytes (141 words) - 19:14, 12 August 2013
  • == Targeted Features ==
    2 KB (288 words) - 03:51, 16 April 2024
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. All features should have patches on the list by this date; major features should
    2 KB (366 words) - 00:42, 15 December 2016
  • ...rs must have sent their pull request to the mailing list. This means that features, and in particular non-trivial ones, must have been merged into maintainer ...maintainer enough time to review, test and apply your patches. For major features you should probably communicate with the maintainer about his intentions.
    1 KB (192 words) - 12:24, 9 January 2017
  • == Targeted Features ==
    2 KB (278 words) - 23:59, 14 December 2021
  • HVF is mostly stable but some features are missing:
    467 bytes (67 words) - 19:16, 5 June 2020
  • The [[Features/IncrementalBackup|Incremental Backup]] feature was merged into QEMU instead ...the old feature proposal, please see [http://wiki.qemu.org/index.php?title=Features/Livebackup&oldid=1188 Livebackup (2011-05-09)]'''
    467 bytes (65 words) - 15:00, 11 October 2016
  • === Removed features and incompatible changes === ...[https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features'] page for details of suggested replacement functionality.
    2 KB (229 words) - 17:13, 25 April 2024
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. All features should have patches on the list by this date; major features should
    3 KB (421 words) - 08:31, 12 October 2016
  • ...contains block layer and storage features that have been proposed. These features may not be in active development and questions about them should be address
    1 KB (196 words) - 10:51, 11 November 2020
  • == Targeted Features ==
    2 KB (288 words) - 13:58, 16 June 2020
  • * [[Features/DiskIOLimits/Requirements|Requirements]] * [[Features/DiskIOLimits/TestCases|Test cases]]
    1 KB (211 words) - 14:54, 11 October 2016
  • feature. See [[Features/ACPITableGeneration|Features/ACPITableGeneration]]
    1 KB (194 words) - 15:41, 11 October 2016
  • When using [[Features/TCG|TCG]] emulation we need emulate the floating point unit of the guest. T [[Category:Completed Features]]
    1 KB (218 words) - 10:01, 27 June 2019
  • ...h a more modern TUI interface that is asynchronous and provides improvised features compared to the existing interfaces. ...tions to operate a running QEMU instance. QMP is a JSON based protocol and features the following
    5 KB (823 words) - 15:54, 23 August 2021
  • ...scales to several hundreds nodes, and supports advanced volume management features such as snapshot, cloning, and thin provisioning. ...no central node such as a meta-data server. This design enables following features.
    2 KB (247 words) - 14:55, 11 October 2016
  • === Hardware features ===
    2 KB (269 words) - 14:56, 9 July 2020
  • ...rectly modeling this interaction is necessary to properly support advanced features like PCI IOMMUs and also to support PCI-based endian conversion in a more r ...virtio uses different memory access functions to manipulate the ring. [[Features/RamAPI|RamAPI]] would simplify the implementation by allowing the virtio ri
    2 KB (263 words) - 14:45, 11 October 2016
  • ! colspan="2" | Features | If the emulated guest support can run on [[Features/tcg-multithread|multiple host threads]]
    3 KB (331 words) - 02:59, 25 March 2022
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. All features should have patches on the list by this date; major features should
    4 KB (636 words) - 08:31, 12 October 2016
  • == Targeted Features ==
    3 KB (468 words) - 08:45, 20 August 2020
  • == Targeted Features ==
    3 KB (393 words) - 20:09, 23 July 2018
  • ...find bugs or missing features in upstream iPXE, and implement bugfixes and features for upstream iPXE. These proposed iPXE changes usually relate to PXE bootin
    2 KB (372 words) - 15:15, 17 February 2017
  • The [[features]] page provides a description of in-progress features.
    2 KB (312 words) - 11:51, 25 January 2022
  • The gdbstub doesn't support all the features of the gdbserver protocol which is documented [https://sourceware.org/gdb/o
    687 bytes (102 words) - 12:44, 20 May 2019
  • ...arushi Mehta is working on the project for Outreachy. Project status is [[Features/IOUring|here]]. * Stretch goal: Adding a fast path when QEMU block layer features are not in use
    2 KB (365 words) - 15:12, 17 May 2019
  • ...couple of minor fixes for structured load/stores and rounding cases for [[Features/ARM/SVE|SVE]] will be in 3.0.1 == Targeted Features ==
    3 KB (523 words) - 20:58, 1 April 2019
  • == Targeted Features ==
    3 KB (397 words) - 00:07, 29 August 2017
  • = Features = * [[Features/VirtioSCSI/TCM Overview|In-kernel SCSI target overview]]
    2 KB (303 words) - 15:39, 11 October 2016
  • ...rk in libqos to enable combinatorial testing. For more information, see [[Features/qtest_driver_framework]].
    760 bytes (114 words) - 15:35, 20 March 2018
  • * snowridge cpu name/features == Targeted Features ==
    3 KB (488 words) - 20:51, 5 November 2019
  • * See [[Features/TCGPlugins]]
    891 bytes (140 words) - 22:19, 17 February 2021
  • ...ng the mailing list nor a place to announce cool new [[Contribute#Features|features]] for users. ...ced with a QOM hierarchy by [[User:Marcel|Marcel Apfelbaum]], details on [[Features/QOM/Machine]].
    4 KB (664 words) - 13:40, 26 July 2017
  • ...in a pull request]; other improvements on top include implementing missing features of the old API (importing from mailing lists, tracking git repositories), O
    967 bytes (146 words) - 15:35, 20 March 2018
  • == Targeted Features ==
    4 KB (610 words) - 14:09, 19 October 2021
  • ...for using remote storage within QEMU. NBD can also be coupled with other features such as streaming or copy-on-read. However, the NBD implementation in QEMU
    932 bytes (132 words) - 14:56, 11 October 2016
  • ...le that allows a user space program to utilize the hardware virtualization features of various processors. Today, it supports recent Intel and AMD processors
    847 bytes (133 words) - 12:11, 6 February 2017
  • ==Features to add==
    4 KB (568 words) - 08:17, 2 March 2017
  • ...he two parts above, e.g. link script to generate flat image. Some specific features will be listed here. ...e mini hypervisor neeeded in this project doesn't need so many complicated features (e.g. Buddy system). Only CPU management, memory management, interrupt cont
    6 KB (976 words) - 15:40, 11 October 2016
  • ...tants, keeping differences minimal. This will make it easy to add for new features like live migration later once they have been introduced in the VFIO commun QEMU's modules system can be used to load features on demand at runtime. Device emulation code can be extended to support mod
    4 KB (603 words) - 18:25, 17 August 2020
  • == Targeted Features ==
    4 KB (634 words) - 23:44, 1 October 2019
  • uint64_t features; /* format feature bits */ /* if (features & QED_F_BACKING_FILE) */
    9 KB (1,374 words) - 14:45, 11 October 2016
  • == Targeted Features ==
    897 bytes (137 words) - 23:05, 20 March 2017
  • == Other proposed qemu features that solve the same problem == [http://wiki.qemu.org/Features/Snapshots snapshots]<br>
    4 KB (663 words) - 14:43, 11 October 2016
  • Template to use for new features and changes that update user-visible interface options (command line option == Conflicts with / enhances / deprecates any existing features ==
    4 KB (547 words) - 04:52, 1 December 2015
  • ...s written for other CPU architectures can be run on any host. Modern CPUs features vector processing instruction sets, sometimes called Single Instruction Mul
    1 KB (172 words) - 15:16, 17 May 2019
  • * See [[Features/TCGPlugins]]
    1 KB (190 words) - 16:51, 20 January 2020
  • ...oleted by <tt>query-cpu-model-expansion</tt> QMP commands and <tt>filtered-features</tt> property ** Actually, the new mechanism is based on the "filtered-features" X86CPU property
    15 KB (2,336 words) - 13:50, 30 October 2017
  • == Targeted Features ==
    3 KB (531 words) - 15:15, 4 September 2019
  • * [[Features/Tracing/Roadmap|Roadmap]]
    1 KB (159 words) - 15:48, 24 February 2021
  • === [[Features/VNC_Tight_PNG|Tight PNG]] ===
    4 KB (662 words) - 07:54, 13 October 2016
  • * Looked over the design of coroutine-ucontext.c and added some features to the stub by basically copying and pasting code from coroutine-ucontext..
    876 bytes (123 words) - 00:06, 14 July 2013
  • In terms of features the SoftMMU is the mechanism by which the TCG allows the emulation of virtu
    1 KB (181 words) - 12:14, 17 January 2018
  • ...language (QEMU is mainly written in C) and to experiment with optimization features that would be hard to deploy inside QEMU itself.
    2 KB (231 words) - 08:39, 29 March 2021
  • ...vm-unit-tests making it match (where possible) VMX and adding SVM-specific features.
    1 KB (221 words) - 16:55, 23 January 2019
  • * [[Features/RemovedFeatures|Replacements for removed features]]
    4 KB (580 words) - 07:28, 9 January 2023
  • ...rnel use cases (such as KVM with SVE) require additional work to support [[Features/ARM/VHE]]
    1 KB (200 words) - 10:57, 13 March 2019
  • * Wrote up [[Features/Continuation-Passing_C | Feature page]]
    972 bytes (146 words) - 20:59, 21 June 2013
  • == Targeted Features ==
    1 KB (180 words) - 10:00, 13 April 2022
  • features that change the format in an incompatible way, so that older increase in order to introduce some incompatible features, however it's
    9 KB (1,281 words) - 10:12, 9 September 2016
  • RDP being the most supported protocol, with more features and efficiency, this project idea is to develop a RDP server to export `-di
    2 KB (231 words) - 13:33, 9 February 2023
  • ...iting emulated devices (like virtio-ccw or 3270). This can be used to test features mandated by the architecture that are not yet implemented for any device th
    1 KB (223 words) - 08:46, 18 September 2017
  • ...a 'set-migration-capabilities' command that can mask some of the supported features. A management tool would query-migration features on the source and destination, take the intersection of the two masks, and
    5 KB (812 words) - 23:50, 25 July 2011
  • '''Summary:''' Enable tests for the [[Features/qtest_driver_framework|qgraph driver framework]] to discover devices using
    1 KB (239 words) - 16:28, 29 January 2019
  • * [[Features/IncrementalBackup]]
    2 KB (248 words) - 17:18, 23 January 2017
  • '''Summary:''' Flesh out aarch64 (ARM) support in vmm-reference to make its features comparable to x86_64
    2 KB (251 words) - 12:53, 25 February 2022
  • =Important Features= ..., copy-on-read, and adaptive prefetching, with the following two important features.
    4 KB (688 words) - 14:45, 11 October 2016
  • [[Features/QED | QED]] is another new QEMU image format. Below is the FVD developer’ .../ext4, reiserFS, Reiser4, XFS, JFS, VMFS, ZFS, etc) provide many different features and are optimized for different objectives (flash wear leveling, seek dista
    8 KB (1,278 words) - 14:45, 11 October 2016
View (previous 100 | ) (20 | 50 | 100 | 250 | 500)