docs: formatdomain: explain host-model/host-passthrough requirements

host-passthrough documentation menions that the source and destination
hosts are not identical in both hardware and configuration.  Configuration
actually includes microcode version and QEMU version, but this is not
clear so make it explicit

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20190802125415.15227-1-pbonzini@redhat.com>
Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
This commit is contained in:
Paolo Bonzini 2019-08-02 14:54:15 +02:00 committed by Jiri Denemark
parent 6b9fe4e53a
commit 0848af78ae

View File

@ -1590,8 +1590,8 @@
hand, the ABI provided to the guest is reproducible. During hand, the ABI provided to the guest is reproducible. During
migration, complete CPU model definition is transferred to the migration, complete CPU model definition is transferred to the
destination host so the migrated guest will see exactly the same CPU destination host so the migrated guest will see exactly the same CPU
model even if the destination host contains more capable CPUs for model for the running instance of the guest, even if the destination
the running instance of the guest; but shutting down and restarting host contains more capable CPUs or newer kernel; but shutting down and restarting
the guest may present different hardware to the guest according to the guest may present different hardware to the guest according to
the capabilities of the new host. Prior to libvirt 3.2.0 and QEMU the capabilities of the new host. Prior to libvirt 3.2.0 and QEMU
2.9.0 detection of the host CPU model via QEMU is not supported. 2.9.0 detection of the host CPU model via QEMU is not supported.
@ -1625,10 +1625,10 @@
environment cannot be reproduced on different hardware. Thus, if you environment cannot be reproduced on different hardware. Thus, if you
hit any bugs, you are on your own. Further details of that CPU can hit any bugs, you are on your own. Further details of that CPU can
be changed using <code>feature</code> elements. Migration of a guest be changed using <code>feature</code> elements. Migration of a guest
using host-passthrough is dangerous if the source and destination using host-passthrough is dangerous if the source and destination hosts
hosts are not identical in both hardware and configuration. If such are not identical in both hardware, QEMU version, microcode version
a migration is attempted then the guest may hang or crash upon and configuration. If such a migration is attempted then the guest may
resuming execution on the destination host.</dd> hang or crash upon resuming execution on the destination host.</dd>
</dl> </dl>
Both <code>host-model</code> and <code>host-passthrough</code> modes Both <code>host-model</code> and <code>host-passthrough</code> modes