| [[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
| [[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
| [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should have initial code committed by this date.
* [[Planning/1.4/Migration compatibility]]
898 bytes (128 words) - 10:34, 12 October 2016
post-copy based live migration
This is yet another live migration mechanism for QEMU/KVM, which
3 KB (432 words) - 06:04, 25 November 2015
...fgang Bumiller; fixed by stefan's virtio-balloon: fix QEMU 4.0 config size migration incompatibility 2019-07-10 - fixed by 2bbadb08ce272d65e1f78621002008b07d1e
...ost from 14th July - 'migration: always initial RAMBlock.bmap to 1 for new migration' - fixed by 40c4d4a835453452a262f32450a0449886aa19ce
3 KB (488 words) - 20:51, 5 November 2019
We need to decompose migration into three different problems:
...a 'set-migration-capabilities' command that can mask some of the supported features.
5 KB (812 words) - 23:50, 25 July 2011
=== 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 (214 words) - 15:30, 15 April 2024
...crash with -device hda-duplex - fix posted: 2018-07-24: audio/hda: Fix migration
* Arm migration of v8M CPUs is broken (not quite a regression)
3 KB (523 words) - 20:58, 1 April 2019
* migration failure of usb storage on xhci under a PCI bridge; works in 2.8 (See patch
...devices don't allow writes to the image on the destination even while the migration is still running)
3 KB (397 words) - 00:07, 29 August 2017
* Storage migration is broken at dst side ("nbd_server_add -w" not working with "-incoming").
* NBD storage migration broken; see https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1711602
1 KB (222 words) - 19:15, 6 December 2017
Post-copy based live migration
A postcopy implementation that allows migration of guests that have large page change rates (relative to the available band
6 KB (885 words) - 12:28, 16 March 2017
* Various minor bugfixes; no new features in this release.
* Many fixes to the Q35 chipset emulation, including experimental AHCI migration support and support for device assignment.
4 KB (589 words) - 12:24, 19 February 2013
migration.
...e basic code of the packet virtqueue in vhost-shadow-virtqueue.c, ignoring features like indirect.
3 KB (405 words) - 14:57, 12 February 2024
* Pending migration PR https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg04457.html
* migration of intel_iommu due to root_scalable field
4 KB (634 words) - 23:44, 1 October 2019
* Source QEMU crashes during migration when format and protocol block nodes were created separately (typical -bloc
* fix some segmentation faults and migration issues -- issues are minor and not regressions
3 KB (531 words) - 15:15, 4 September 2019
...or Mode Execution Prevention) and SMAP (Supervisor Mode Access Prevention) features of newer x86 processors.
...se, bmi1, hle, avx2, smep, bmi2, erms, invpcid, rtm) and "Opteron_G5" (new features: tbm, f16c, fma)
6 KB (951 words) - 16:38, 15 January 2013
* ESP acceptance test/migration fix (see https://lists.gnu.org/archive/html/qemu-devel/2021-04/msg00860.htm
* migration: Deprecate redundant query-migrate result @blocked
4 KB (610 words) - 14:09, 19 October 2021
* no dirty logging support, since that live migration is not included in this version;
...erences minimal. This will make it easy to add for new features like live migration later once they have been introduced in the VFIO community.
4 KB (603 words) - 18:25, 17 August 2020
* [[Documentation/Migration with shared storage|Set up storage for live migration]]
* [[Features/RemovedFeatures|Replacements for removed features]]
4 KB (580 words) - 07:28, 9 January 2023
...and can be used by firmware directly. This will in the future enable new features without modifications of all firmware components (SeaBIOS, OVMF, CoreBoot)
=== Migration ===
4 KB (563 words) - 11:31, 10 December 2013
...ant to generate included JSON files, but only the primitives introduced in migration.json.
We should have an unified place for migration documentation in general. The plan for now is we make it:
17 KB (2,909 words) - 17:02, 28 March 2024
existing live migration facility in QEMU.
...ndary servers. Please prepare a SAN to place the guest image same as live migration.
4 KB (636 words) - 14:45, 11 October 2016
This page lists areas in the implementation of [[Features/Channel_I/O_Passthrough|vfio-ccw for channel I/O passthrough]] that still n
== Missing architecture features ==
9 KB (1,396 words) - 11:18, 11 December 2019
=== Migration ===
No problems found during instance creation, live migration and deletion. For these activities, Ganeti sends commands to QEMU both via
7 KB (1,052 words) - 16:41, 29 November 2011
| [[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
* Migration of virtio-blk is broken (patch posted: "[PATCH] virtio-blk: correctly dirty
...ry-command-line-options shows no options for -machine, breaks some libvirt features (will be fixed in 2.3.0-rc2)
2 KB (255 words) - 21:28, 16 April 2015
...igration of KVM guests with up to 8TB of memory continues to work, as will migration of >8TB guests from QEMU 4.2 on.
=== New deprecated options and features ===
11 KB (1,631 words) - 11:24, 3 December 2019
* Migration and vm save/load now works correctly on the vexpress-a15 and vexpress-a9 mo
...cpu-add QMP command. More details [[Features/CPUHotplug#cpu-add_interface|Features/CPUHotplug]].
7 KB (1,120 words) - 18:28, 27 May 2013
* {{git|77a0262}} hw/9pfs: use migration blockers to prevent live migration when virtfs export path is mounted
...s without a native code generator can use the TCG interpreter (TCI). See [[Features/TCI]] for more information.
6 KB (908 words) - 20:51, 17 February 2012
...irtualization is enabled. The next version of QEMU will be able to do live migration when nested virtualization is enabled, if supported by the kernel.
=== New deprecated options and features ===
7 KB (1,028 words) - 16:56, 21 February 2019
* ghes migration broken (looped vmstate https://lists.gnu.org/archive/html/qemu-devel/2020-1
* migration incompatibility of nec-usb-xhci ( https://lists.gnu.org/archive/html/qemu-d
5 KB (755 words) - 10:12, 3 December 2020
...[https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features' ] page for details of suggested replacement functionality
=== New deprecated options and features ===
8 KB (1,060 words) - 18:28, 9 December 2021
* Live migration support for NVRAM
* Support for cpu state handling and migration.
7 KB (980 words) - 15:30, 14 December 2014
...g a pflash drive. This feature is not supported when KVM is enabled. See [[Features/PC System Flash]] for more information.
* KVM guests support Hyper-V enlightenments. These are enabled by the -cpu features hv_spinlocks, hv_relaxed and hv_vapic.
8 KB (1,276 words) - 05:38, 3 June 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
Future qemu is expected to support these features (some already implemented):
= Live features =
21 KB (3,397 words) - 15:04, 11 October 2016
:This change requires care when doing migration from 1.x to 2.x QEMU; you need to specify bus=NEW explicitly on the destina
...rename is pci to pci.0 for pseries. This does not require as much care on migration; if you were specifying "bus=pci" explicitly, QEMU will not start unless yo
10 KB (1,572 words) - 19:24, 16 April 2014
=== Removed features and incompatible changes ===
...[https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features'] page for details of suggested replacement functionality.
12 KB (1,752 words) - 14:51, 19 April 2023
* Changes to device "sdhci-pci" will make migration between old and new versions impossible.
* [[Features/HRandomHypercall | H_RANDOM hypercall]] device for providing good random da
13 KB (2,001 words) - 11:33, 17 December 2015
=== New deprecated options and features ===
...System Emulation User's Guide for the full list of historically deprecated features/options.
12 KB (1,689 words) - 16:12, 14 May 2021
...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
...6, 97, 98, 99, 139, 140) are the only ones). QEMU 2.1 fixes this, so that migration from QEMU 1.7 to QEMU 2.1 should always work. However, the fix breaks the
** migration from QEMU 2.0 to QEMU 2.1 with PCI bridges and machine types pc-i440fx-1.7/
10 KB (1,454 words) - 10:42, 29 July 2014
==Outstanding features==
* Live migration on shared storage
3 KB (397 words) - 14:45, 11 October 2016
...registers mean we can boot more recent Linux kernels that probe for these features
* Removed dependency on external kernel headers, all supported KVM features are now built into the binary
8 KB (1,151 words) - 06:40, 13 October 2011
** Tracing framework is described at [[Features/Tracing]] and in docs/tracing.txt in the source tree.
...and a bit of the human monitoring / control interface) is implemented in [[Features/QAPI|QAPI]] and [[Documentation/QMP|QMP]]. See also https://www.linux-kvm.
7 KB (1,227 words) - 07:18, 18 November 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.
15 KB (2,193 words) - 13:57, 18 December 2023
=== New deprecated options and features ===
...eprecated Features"] appendix for the full list of historically deprecated features/options.
12 KB (1,748 words) - 09:55, 28 April 2019
=== Removed features and incompatible changes ===
...[https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features'] page for details of suggested replacement functionality.
12 KB (1,709 words) - 00:37, 12 April 2024
...[https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features'] page for details of suggested replacement functionality.
==== Other removed features ====
11 KB (1,553 words) - 14:27, 3 February 2023
...[https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features' ] page for details of suggested replacement functionality
=== New deprecated options and features ===
13 KB (1,888 words) - 07:16, 11 April 2022
...eprecated Features"] appendix for the full list of historically deprecated features/options.
=== Migration ===
10 KB (1,457 words) - 01:21, 12 June 2018
...[https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features' ] page for details of suggested replacement functionality
=== New deprecated options and features ===
12 KB (1,665 words) - 16:02, 24 August 2021
That is, if there's a long running job on a domain, e.g. migration, libvirt
=== LXC driver migration implementation ===
13 KB (1,926 words) - 10:50, 22 March 2016
* Support for migration/savevm
...e. Only x3270 is supported as client. See https://wiki.qemu.org/index.php/Features/3270 for details.
11 KB (1,614 words) - 18:24, 24 August 2017
=== Postcopy migration: Recovery from a broken network connection ===
...e postcopy migration mode so it can cope with a network failure during the migration.
18 KB (2,911 words) - 10:51, 22 March 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.
14 KB (2,074 words) - 14:12, 15 August 2023
.../master/system/deprecated.html#recently-removed-features "Recently removed features"] chapter of the QEMU System Emulation User's Guide.
=== New deprecated options and features ===
18 KB (2,670 words) - 01:26, 7 May 2022
=== New deprecated options and features ===
...System Emulation User's Guide for the full list of historically deprecated features/options.
14 KB (2,072 words) - 20:38, 28 April 2020
* Numerous NCQ fixes and adjustments, principally relating to migration and pause/resume.
* scsi-generic now supports migration.
13 KB (2,067 words) - 17:11, 2 December 2015
...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
17 KB (2,629 words) - 15:07, 16 February 2016
=== New deprecated options and features ===
...eprecated Features"] appendix for the full list of historically deprecated features/options.
11 KB (1,707 words) - 08:58, 24 October 2019
There are several features still pending:
== Migration ==
26 KB (4,022 words) - 16:28, 16 July 2019
The first patchset that brings basic tracing features to QEMU.
http://wiki.qemu.org/Features/Tracing/Roadmap
4 KB (631 words) - 14:59, 11 October 2016
=== Deprecated options and features ===
...eprecated Features"] appendix for the full list of historically deprecated features/options.
18 KB (2,730 words) - 10:02, 26 April 2018
...[https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features' ] page for details of suggested replacement functionality.
=== New deprecated options and features ===
13 KB (1,895 words) - 13:55, 20 August 2022
* Support migration for the GICv3 when using KVM
* Support for network boot, see http://wiki.qemu-project.org/Features/S390xNetworkBoot
13 KB (1,919 words) - 09:03, 19 April 2017
* 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
16 KB (1,321 words) - 18:38, 30 January 2023
...[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
19 KB (2,811 words) - 07:39, 16 April 2021
* virtio-gpu 2d live migration support
=== Migration ===
12 KB (1,746 words) - 15:53, 1 September 2016
=== Postcopy migration: Recovery from a broken network connection ===
...e postcopy migration mode so it can cope with a network failure during the migration.
25 KB (4,050 words) - 10:36, 23 March 2017
...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:
19 KB (3,009 words) - 15:08, 16 February 2016
* Support for several new CPUID features related to AVX-512 instruction set extensions.
=== Migration ===
9 KB (1,253 words) - 11:05, 21 December 2016
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
6 KB (994 words) - 16:08, 17 October 2016
=== New deprecated options and features ===
...eprecated Features"] appendix for the full list of historically deprecated features/options.
25 KB (3,731 words) - 14:03, 23 October 2019
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]].
6 KB (988 words) - 06:57, 17 March 2022
...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
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
8 KB (1,290 words) - 01:32, 5 September 2014
* No more modifying guest drivers to add simple storage protocol features
====Block migration [Juan?]====
21 KB (3,159 words) - 10:43, 11 November 2020
* Improved support for migration of g3beige and mac99 machines
* Support for the XSAVE/XSAVEOPT, MPX, FSGSBASE and PKE features
20 KB (2,998 words) - 09:09, 19 July 2016
* Various bug fixes, no new features.
* Various fixes and stabilization for live-migration: {{git|783e7706937fe15523b609b545587a028a2bdd03}} {{git|954773230484f5afeb6
16 KB (2,781 words) - 08:34, 12 October 2016
- Fix incoming migration with iothread (Marcelo Tosatti)
- fdc: fix migration from 0.11 (Juan Quintela)
42 KB (6,720 words) - 12:21, 18 February 2011
...we don't inadvertently introduce the same problems again when adding newer features and/or bug fixes. For example, a bug was introduced a while back that incor
1. Writing unit tests for missing VMX features tests; eg- invvpid,
24 KB (3,706 words) - 10:39, 23 March 2017
...we don't inadvertently introduce the same problems again when adding newer features and/or bug fixes. For example, a bug was introduced a while back that incor
1. Writing unit tests for missing VMX features tests; eg- invvpid,
25 KB (3,900 words) - 10:50, 22 March 2016
...to flush a dynamic translator cache (when used with QEMU), to handle live migration or to optimize MMU emulation.
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
