cedc850e4e
Add a new sev_enabled() function to the libvirt utils to detect that
SEV is required and return True if and only if the following are both
true:
a) the supports_amd_sev instance variable in the host is
true, *and*
b) the instance extra specs and/or image properties request
memory encryption to be enabled.
In this case we know that SEV functionality is required, so tweak the
guest config accordingly in various ways:
- Ensure that the machine type is some q35 variant. If the image had
an hw_machine_type property requesting some other type, an
InvalidMachineType exception will be raised.
- Set the "iommu" attribute to "on" for all relevant devices including
disk / network devices, but excluding input/graphics/video/serial
devices. This is achieved via a new set_driver_iommu_for_sev()
method added to nova.virt.libvirt.designer. In order to test this
thoroughly, beef up the fake KVM guest fixture with extra devices
of each type.
- Add the <launchSecurity> element to enable use of SEV. Two related
configuration values are extracted from domain capabilities and set
on the element.
- Enable memory locking. All the memory pages allocated by QEMU must
be pinned for SEV, which is achieved via <memoryBacking> and <locked />
elements.
blueprint: amd-sev-libvirt-support
Change-Id: Ie54fca066f3333d1d5d18a2c0e8f6c7d5042490b
|
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| playbooks | ||
| releasenotes | ||
| roles/run-post-test-hook | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| lower-constraints.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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: