[libvirt PATCH 1/2] docs: domain: Clarify on the dangers of migrating with hyperv-passthrough enabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Signed-off-by: Tim Wiederhake <twiederh@xxxxxxxxxx>
---
 docs/formatdomain.rst | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
index 0c5e33c78f..2e9c450606 100644
--- a/docs/formatdomain.rst
+++ b/docs/formatdomain.rst
@@ -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``.
 
-- 
2.31.1




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux