External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-02-21 19:02:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: domain: Clarify on the dangers of migrating with hyperv-passthrough enabled

Browse Source 
Signed-off-by: Tim Wiederhake <twiederh@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Tim Wiederhake 2021-12-14 17:21:16 +01:00
parent fdec0cbf43
commit 0519787f88
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/formatdomain.rst
View File

@ -1929,7 +1929,14 @@ are:
Set exactly the specified features.
``passthrough``
Enable all features currently supported by the hypervisor.
Enable all features currently supported by the hypervisor, even those that
libvirt does not understand. Migration of a guest using passthrough is
dangerous if the source and destination hosts are not identical in both
hardware, QEMU version, microcode version and configuration. If such a
migration is attempted then the guest may hang or crash upon resuming
execution on the destination host. Depending on hypervisor version the
virtual CPU may or may not contain features which may block migration
even to an identical host.
The ``mode`` attribute can be omitted and will default to ``custom``.