Search results

Jump to: navigation, search

Page title matches

  • Migration roadmap. This page describes what are the changes planned for migration and who is supposed to do each of the changes.
    5 KB (737 words) - 06:10, 25 March 2015
  • 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
  • Migration compatibility is not affected by these changes, as the - Block migration
    8 KB (1,202 words) - 16:21, 24 April 2014
  • Use multiple FD's for migration Currently there is a single stream for migration, this causes several problems:
    2 KB (309 words) - 12:52, 16 December 2015
  • You're probably looking at this page because migration has just failed; sorry about that, but hopefully this page will give you so QEMU's migration is like lifting the state out of one machine and dumping it into another -
    14 KB (2,526 words) - 19:52, 22 November 2017

Page text matches

  • - 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
  • * 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
  • ...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
  • ...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
  • 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
  • ** 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,207 words) - 18:49, 27 February 2017
  • 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
  • * 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
  • * 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
  • ...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
  • ==Outstanding features== * Live migration on shared storage
    3 KB (397 words) - 14:45, 11 October 2016
  • Migration roadmap. This page describes what are the changes planned for migration and who is supposed to do each of the changes.
    5 KB (737 words) - 06:10, 25 March 2015
  • Future qemu is expected to support these features (some already implemented): = Live features =
    21 KB (3,397 words) - 15:04, 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
  • 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
  • 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
  • * {{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
  • * No more modifying guest drivers to add simple storage protocol features ====Block migration [Juan?]====
    4 KB (580 words) - 08:43, 12 October 2016
  • === 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
  • ...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
  • * 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
  • | [[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
  • ...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
  • 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
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should have initial code committed by this date. * [[Planning/1.4/Migration compatibility]]
    898 B (128 words) - 10:34, 12 October 2016
  • * 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
  • ...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
  • * 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
  • ...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
  • 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
  • ...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
  • :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
  • ...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
  • 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]].
    8 KB (1,232 words) - 18:25, 23 November 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
  • * Live migration support for NVRAM * Support for cpu state handling and migration.
    7 KB (980 words) - 15:30, 14 December 2014
  • 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
  • * 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
  • ...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
  • * 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
  • There are several features still pending: == Migration ==
    26 KB (4,021 words) - 23:28, 21 February 2017
  • 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
  • * 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
  • | [[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
  • === 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
  • | [[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
  • * 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
  • === 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
  • * virtio-gpu 2d live migration support === Migration ===
    12 KB (1,746 words) - 15:53, 1 September 2016

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)