Bug 1579699
Summary: | [Deployment][RHOSP-10] Lift the restriction on choices for `cpu_model_extra_flags` config attribute | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Rajesh Tailor <ratailor> |
Component: | puppet-nova | Assignee: | Rajesh Tailor <ratailor> |
Status: | CLOSED ERRATA | QA Contact: | OSP DFG:Compute <osp-dfg-compute> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 10.0 (Newton) | CC: | amcleod, jjoyce, jschluet, lyarwood, nlevinki, nova-maint, owalsh, ratailor, slinaber, tvignaud |
Target Milestone: | z9 | Keywords: | Triaged, ZStream |
Target Release: | 10.0 (Newton) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | puppet-nova-9.6.0-7.el7ost | Doc Type: | Enhancement |
Doc Text: |
With this enhancement, the Nova libvirt driver now allows the specification of granular CPU feature flags when configuring CPU models.
One benefit of this change is the alleviation of a performance degradation experienced on guests running with certain Intel-based virtual CPU models after application of the "Meltdown" CVE fixes. This guest performance impact is reduced by exposing the CPU feature flag 'PCID' ("Process-Context ID") to the *guest* CPU, assuming that the PCID flag is available in the physical hardware.
In this update, the restriction of using only the PCID flag is extended to expose multiple CPU feature flags.
For more details, refer to the documentation of ``[libvirt]/cpu_model_extra_flags`` in ``nova.conf`` for usage details.
|
Story Points: | --- |
Clone Of: | 1579681 | Environment: | |
Last Closed: | 2018-09-17 16:54:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1579681 | ||
Bug Blocks: | 1579691, 1579693, 1579694 |
Comment 9
Alex McLeod
2018-09-03 08:00:13 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2670 |