So, my take on that is that this is not technically a bug, rather a current limitation (hence Opinion/Wishlist)
That needs at least a blueprint to be created and possibly some discussion around the implementation design, see https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule#How_do_I_get_my_code_merged.3F ** Changed in: nova Importance: Undecided => Wishlist ** Changed in: nova Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1498684 Title: Fail to use SR-IOV ports when VFIO is loaded Status in OpenStack Compute (nova): Opinion Bug description: Issue has been reproduced in kilo. There is a limitation when using VFIO with some PCI devices. Some PCI devices with multiple hardware components are places in the same IOMMU group (for example a NIC with multiple ports). In this case, the multiple PCI devices in that same IOMMU group can't be assigned to multiple guests, they are limited to be used by only one guest. It is possible to specify the driver name when generating the libvirt XML for a guest (name can be "vfio" or "kvm" for legacy PCI device assignment method). The proposed solution is to provide a configuration parameter to specify which driver to use when using PCI passthrough devices. Perhaps this can be specified by hardware model (PCI vendor and product). The issue was also described here: https://ask.openstack.org/en/question/62749/vfio-pci-vs-pci-assign- for-sr-iov-direct-ports/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1498684/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
