Search results

...ill in the configuration files, and no way to express dependencies between features. The project seeks to adopt Linux's Kconfig in QEMU, and possibly to impro QEMU can serialize state for its devices. This feature is used by migration and save to disk. We want to exercise that state to be sure that we are no

=== New deprecated options and features === ...eprecated Features"] appendix for the full list of historically deprecated features/options.

There are several features still pending: == Migration ==

** migration ...O: rustfmt configuration currently requires nightly due to use of unstable features

The first patchset that brings basic tracing features to QEMU. http://wiki.qemu.org/Features/Tracing/Roadmap

=== Deprecated options and features === ...eprecated Features"] appendix for the full list of historically deprecated features/options.

...[https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features' ] page for details of suggested replacement functionality. === New deprecated options and features ===

* Support migration for the GICv3 when using KVM * Support for network boot, see http://wiki.qemu-project.org/Features/S390xNetworkBoot

* COLO Block Replication (Please refer to [http://wiki.qemu.org/Features/BlockReplication BlockReplication]) : Modifications of save/restore flow to realize continuous migration, to make sure the state of VM in Secondary side

...[https://qemu-project.gitlab.io/qemu/system/removed-features.html 'Removed features' ] page for details of suggested replacement functionality ...'' machine types have been removed (they likely could not be used for live migration from old QEMU versions anymore anyway). Use a newer ''pc-i440fx-...'' machi

* virtio-gpu 2d live migration support === Migration ===

=== Postcopy migration: Recovery from a broken network connection === ...e postcopy migration mode so it can cope with a network failure during the migration.

* Support for several new CPUID features related to AVX-512 instruction set extensions. === Migration ===

...than q35 does (e.g. interrupt remapping). As time permits, some additional features could already be added so that q35 could be manually configured to expose t Minimally required VT-d features for q35 are:

More detail: [[Features/Real rng device]] ...ity of the RDRAND instruction on the host may not be desirable due to live migration constraints. Using RDRAND on the host, if available, as a source of entrop

=== New deprecated options and features === ...eprecated Features"] appendix for the full list of historically deprecated features/options.

The preferred way to implement state save/load for migration is to describe the device state using a VMStateDescription struct. Some dev * QEMUMachine has been replaced with a QOM hierarchy, details on [[Features/QOM/Machine]].

Note that we don't have to port the code from "dd", or try to support all the features. A similar user interface is good enough. That is, if there's a long running job on a domain, e.g. migration, libvirt

...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:

* No more modifying guest drivers to add simple storage protocol features ====Block migration [Juan?]====