]> xenbits.xensource.com Git - libvirt.git/commit
qemu: Handle host devices not being available better
authorAndrea Bolognani <abologna@redhat.com>
Thu, 24 Aug 2017 14:33:29 +0000 (16:33 +0200)
committerAndrea Bolognani <abologna@redhat.com>
Mon, 28 Aug 2017 14:16:12 +0000 (16:16 +0200)
commit1f43393283ff04d1a3905abb3669cdd5665610b4
tree157e6aeace6ddde29736cc0224b6daceddece5f7
parente02ff020cac1aa2b35c7eed4e0446be9a49496ac
qemu: Handle host devices not being available better

We can't retrieve the isolation group of a device that's not present
in the system. However, it's very common for VFs to be created late
in the boot, so they might not be present yet when libvirtd starts,
which would cause the guests using them to disappear.

Moreover, for other architectures and even ppc64 before isolation
groups were introduced, it's considered perfectly fine to configure a
guest to use a device that's not yet (or no longer) available to the
host, with the obvious caveat that such a guest won't be able to
start before the device is available.

In order to be consistent, when a device's isolation group can't be
determined fall back to not isolating it rather than erroring out or,
worse, making the guest disappear.

Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1484254

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
src/qemu/qemu_domain_address.c