Search results
There is a page named "Features/" on QEMU. See also the other search results found.
Page title matches
- In terms of features the SoftMMU is the mechanism by which the TCG allows the emulation of virtu1 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 tha16 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, and5 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. Minimize16 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/o687 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 implement2 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 chapte969 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 ri2 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
Page text matches
- | [[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
- | [[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
- == Targeted Features ==896 bytes (135 words) - 08:46, 14 May 2024
- | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. All features should have patches on the list by this date; major features should1 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
- * [[Features/SoftMMU]] * [[Features/MTTCG]]3 KB (421 words) - 19:59, 9 March 2022
- 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.html197 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
- These pages document QEMU features for users. Please consider [[Contribute|contributing]] patches to move the7 members (0 subcategories, 0 files) - 10:04, 12 October 2016
- These pages document QEMU features for users. Please consider [[Contribute|contributing]] patches to move the8 members (0 subcategories, 0 files) - 10:05, 12 October 2016
- '''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/vVMSAVE810 bytes (108 words) - 10:16, 9 February 2021
- * [[Features/CPUModels]]279 bytes (35 words) - 18:52, 20 March 2012
- == Features == Features that I'm working on:3 KB (524 words) - 00:04, 20 May 2013
- | 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 fun3 KB (405 words) - 12:12, 4 November 2020
- == Targeted Features ==1 KB (209 words) - 20:51, 3 September 2020
- These features have been completed. Information in the pages should be integrated in the50 members (0 subcategories, 0 files) - 15:17, 11 October 2016
- == 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 should2 KB (366 words) - 00:42, 15 December 2016
- * [[Features/IntegratedCopyPaste|Copy/Paste Integration into Qemu]] - [http://github.com320 bytes (39 words) - 08:02, 21 June 2013
- ...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 (342 words) - 08:43, 7 May 2024
- == 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
- | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. All features should have patches on the list by this date; major features should3 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 address1 KB (196 words) - 10:51, 11 November 2020
- == Targeted Features ==2 KB (288 words) - 13:58, 16 June 2020
- * [[Features/TCI|TCG interpreter]] (TCI) I'm also the maintainer of the [[Features/TCI|TCG interpreter]] (TCI).1 KB (191 words) - 18:11, 28 March 2014
- * [[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 following5 KB (823 words) - 15:54, 23 August 2021
- === Removed features and incompatible changes === ...[https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features'] page for details of suggested replacement functionality.3 KB (330 words) - 13:35, 16 May 2024
- ...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 ri2 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 should4 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 bootin2 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/o687 bytes (102 words) - 12:44, 20 May 2019
- ...n interesting subset of pages. For an example, see [[Documentation]] or [[Features]].732 bytes (96 words) - 09:13, 10 January 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 use2 KB (365 words) - 15:12, 17 May 2019