Search results
There is a page named "Features/" on QEMU. See also the other search results found.
Page title matches
- 9 KB (1,482 words) - 02:20, 17 September 2011
- 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
- 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
- 7 KB (1,041 words) - 12:40, 22 March 2022
- 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
- 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
- 861 bytes (130 words) - 14:59, 9 July 2020
- 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
- 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
- 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
- For the rationale behind the conversion and the development notes, see [[Features/Meson/Design]]. === Other features===8 KB (1,294 words) - 06:46, 14 June 2024
- 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
Page text matches
- 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/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
- ...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
- ...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
- ...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