
cpu_model_extra_flags
Commit 6b601b7 (libvirt: Allow to specify granular CPU feature flags) added support for allowing to specify individual CPU feature flags, but restricted the options only to "PCID" (refer to its commit message for why). In this change we lift the restriction of choices, and allow to specify multiple CPU feature flags for all three CPU modes for the libvirt driver: 'custom', 'host-model', and 'host-passthrough'. For example: [libvirt] cpu_mode = custom cpu_model = IvyBridge cpu_model_extra_flags = pcid, vmx, pdpe1gb This will allow additional use cases such as: - Ability to use 1GB huge pages with models that don't provide it (such as Intel "Haswell" variants) as one use case for extra flags: cpu_mode = custom cpu_model = Haswell-noTSX-IBRS cpu_model_extra_flags = pdpe1gb - Nested Virtualization -- an operator can specify the Intel 'vmx' (or AMD 'svm') flags for the level-1 Nova guest CPU models. (Assuming the 'nested' flag is enabled on the level-0 / bare-metal kernel.) (A future Nova patch will also allow ability to remove CPU flags.) Change-Id: I9a862619f379057bb48cb85a84dfc50d763030a6 Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com> BluePrint: libvirt-cpu-model-extra-flags
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: