search for: inactivepcihostdev

In attempting to isolate vfio-pci problems between two different guest instances, the creation of a second guest (with existing guest shutdown) resulted in:. Aug 09 12:43:23 grit libvirtd[6716]: internal error: Device 0000:01:00.3 is already in use Aug 09 12:43:23 grit libvirtd[6716]: internal error: Device 0000:01:00.3 is already in use Aug 09 12:43:23 grit libvirtd[6716]: Failed to allocate PCI

...>          return -1; > > Is this too simplistic or undesirable a feature request/implementation? Only devices that are currently in use by a guest (activePCIHostdevs), or that libvirt is in the process of detaching from the guest + vfio and rebinding to the device's host driver (inactivePCIHostdevs) are on either list of PCI devices maintained by libvirt. Once a device is completely detached from the guest and (if "managed='yes'" was set in the XML config) re-binded to the natural host driver for the device, it is removed from the list and can be used elsewhere. I just...

...> > > > Is this too simplistic or undesirable a feature request/implementation? > > Only devices that are currently in use by a guest (activePCIHostdevs), > or that libvirt is in the process of detaching from the guest + vfio and > rebinding to the device's host driver (inactivePCIHostdevs) are on > either list of PCI devices maintained by libvirt. Once a device is > completely detached from the guest and (if "managed='yes'" was set in > the XML config) re-binded to the natural host driver for the device, it > is removed from the list and can be used el...