]> xenbits.xensource.com Git - libvirt.git/commit
qemu: skip hardcoded hostdev migration check if QEMU can do it for us
authorLaine Stump <laine@redhat.com>
Thu, 21 Jul 2022 06:03:49 +0000 (02:03 -0400)
committerLaine Stump <laine@redhat.com>
Thu, 21 Jul 2022 15:12:46 +0000 (11:12 -0400)
commit25883cd5f0b188f2417f294b7d219a77b219f7c2
treefd42b5991c7e0f8f599c67e5c3329cfdc1530c48
parent2dd5587f1dc8e2cf4e6e0a4e4cf576b8183b33cd
qemu: skip hardcoded hostdev migration check if QEMU can do it for us

libvirt currently will block migration for any vfio-assigned device
unless it is a network device that is associated with a virtio-net
failover device (ie. if the hostdev object has a teaming->type ==
VIR_DOMAIN_NET_TEAMING_TYPE_TRANSIENT).

In the future there will be other vfio devices that can be migrated,
so we don't want to rely on this hardcoded block. QEMU 6.0+ will
anyway inform us of any devices that will block migration (as a part
of qemuDomainGetMigrationBlockers()), so we only need to do the
hardcoded check in the case of old QEMU that can't provide that
information.

Signed-off-by: Laine Stump <laine@redhat.com>
Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
src/qemu/qemu_migration.c