Only in qemuhotplug test, in order to not fail when running the
test on macOS.
This is a temporary measure until I decice how best to make a mock
environment that allows virPCIDeviceFindBestVariant() to succeed on
non-Linux platforms (which is a bit nonsensical, since none of that
code will ever r
Add a surprisingly missing simple function to the arsenal.
Signed-off-by: Laine Stump
---
src/libvirt_private.syms | 1 +
src/util/virstring.c | 17 +
src/util/virstring.h | 1 +
3 files changed, 19 insertions(+)
diff --git a/src/libvirt_private.syms b/src/libvirt_priv
Historically libvirt has treated the concept of "loadable kernel
module" and "device driver" as being effectively the same (at least in
the case of the vfio-pci driver used for VFIO device assignment). The
code assumed that a module named "vfio-pci" implemented a driver named
"vfio-pci".
In realit
The hostdev version of the subelement appears in four places:
* The domain XML in the and
elements (that's 2)
* The network XML inside when the network is a pool of
SRIOV VFs
* the XML, which is used to communicate between the
hypervisor driver and network driver.
In order to m
Now if a new attribute is added to , we only need to update
the formatting/parsing in one place.
Signed-off-by: Laine Stump
---
src/conf/network_conf.c | 24
src/conf/virnetworkportdef.c | 21 ++---
2 files changed, 10 insertions(+), 35 deletions(-)
This is done so that we can re-use the same parser/formatter for
and
Signed-off-by: Laine Stump
---
src/conf/device_conf.c | 41 +
src/conf/device_conf.h | 7 +++
src/conf/domain_conf.c | 28 +---
3 files changed, 53 insertio
The exact same element can appear in and , and nearly identical in and
(these latter two don't include "xen" as a possible driver, but that's
coincidental - there's no reason Xen couldn't also use the VF pools in
virtual networks, it just doesn't).
This patch modifies all 4 to use the same
so
The new struct is virDeviceHostdevPCIDriverInfo, and the "backend"
enum in the hostdevDef will be replaced with a
virDeviceHostdevPCIDriverInfo named "driver'. Since the enum value in
this new struct is called "type", it means that all references to
"backend" will become "driver.type".
This will a
(Thisis "V2 of Part 2". "V1 of Part 2" is here:
https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/5GF4N5D2HR37HIST3QZ6GXZ6CLIEWOVN/#5GF4N5D2HR37HIST3QZ6GXZ6CLIEWOVN
)
Part 1 (which simply made it possible to use virsh nodedev-detach to
bind a device to a manually-specified va
