c1179d1ff2
As explained in the SEV spec[0], SEV needs a q35 machine type in order to bind all the virtio devices to the PCIe bridge so that they use virtio 1.0 and not virtio 0.9, since QEMU's iommu_platform feature was added in virtio 1.0 only. So add an extra check to be run in the API layer whenever SEV is requested, to ensure that a machine type *outside* the q35 family (e.g. 'pc', or something like 'pc-i440fx-2.11') is not explicitly selected in the image via the hw_machine_type property. Since code in the API layer doesn't run on the compute host, at this stage we can't check CONF.libvirt.hw_machine_type via libvirt.utils. A subsequent commit will change the libvirt driver to trigger an extra, later check on the compute node, although if that late check fails, the best we can do is to fail the operation on that compute host, in which case it will potentially be retried on another compute host. nova's hardcoded default for x86_64 is 'pc' (which in fact matches QEMU's current default). This means that it will be recommended that SEV-capable compute hosts have CONF.libvirt.hw_machine_type configured to include 'x86_64=q35', otherwise attempts to boot SEV guests without the image property 'hw_machine_type=q35' will fail unpleasantly. In the future it is expected that both of these defaults will change to 'q35'[1]. Once that happens, x86_64 images will be bootable without needing to set either the hw_machine_type image property or CONF.libvirt.hw_machine_type. While extending the unit tests for invalid combinations of image properties, add tests for the case where the 'hw_firmware_type' property is not specified at all; previously the tests only covered the case where it was set to 'bios'. [0] http://specs.openstack.org/openstack/nova-specs/specs/train/approved/amd-sev-libvirt-support.html [1] https://bugs.launchpad.net/nova/+bug/1780138 blueprint: amd-sev-libvirt-support Change-Id: Ibf66a0b371685c673644493bf12663dbf71fab6c
Team and repository tags
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, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
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:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: