d38d5767d1
Specifying a PF passthrough device in the pci_passthrough_whitelist using its fully qualified PCI address (no wildcard) causes the device to not be properly loaded. The PCI device is then not available to be assigned to any guest. In this case, the hypervisor reports the PF device without a 'parent_addr'. But in the PciAddress, match() is using it when doing the comparison to its own address. This commit changes the logic of the address matching method in PciDevSpec to only try to match the address with a physical function device when a 'parent_addr' is reported by the hypervisor. Change-Id: I5255240871d8ad5c216500f39520339efe46e84b Closes-Bug: #1613434
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
API
To learn how to use Nova's API, consult the documentation available online at:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at: