At 09/15/2011 08:23 PM, Marc-André Lureau Write: > Hi Daniel > > On Thu, Sep 15, 2011 at 10:18 AM, Daniel P. Berrange > <berrange@xxxxxxxxxx> wrote: >> This isn't really desirable, because our PCI device address tracking >> code is still going to allow other devices to share the slot with >> QXL, and not know that the ARGV has been hacked to disable multifunction. > > How do we allow other devices to share the slot? It seems to me that > qemuDomainPCIAddressSetNextAddr() only allocate whole slot, while > making sure there is no conflicts on the same slot. If the user specifies pci address, we use the pci address. If the user does not specify pci address, we will allocate whole slot for the device. If the pci device is hot plugged, it should be single function(hotplugging multi function pci device is not supported now) So, if the user wants to use multi function pci device, he should specify the pci address. Thanks Wen Congyang -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list