Bug 1571756
Summary: | [RFE][Deployment] add ability to configure extra CPU flags for named CPU models | ||
---|---|---|---|
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: | high | Docs Contact: | |
Priority: | high | ||
Version: | 10.0 (Newton) | CC: | amcleod, awaugama, berrange, dasmith, egallen, eglynn, jamsmith, jhakimra, jjoyce, jschluet, kchamart, lyarwood, mtessun, nlevinki, owalsh, ratailor, rhos-docs, sbauza, sferdjao, sgordon, slinaber, srevivo, tvignaud, vromanso |
Target Milestone: | z9 | Keywords: | FutureFeature, InstallerIntegration, TestOnly, Triaged, ZStream |
Target Release: | 10.0 (Newton) | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | puppet-nova-9.6.0-4.el7ost | Doc Type: | Enhancement |
Doc Text: |
Nova's 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 that has been 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 itself.
For more details, refer to the documentation of ``[libvirt]/cpu_model_extra_flags`` in ``nova.conf`` for usage details.
|
Story Points: | --- |
Clone Of: | 1547954 | Environment: | |
Last Closed: | 2018-09-17 16:54:10 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: | 1398343, 1547954, 1570610, 1570611, 1570614, 1570617 | ||
Bug Blocks: | 1571741, 1571744, 1571750 |
Comment 3
Jon Schlueter
2018-06-28 19:35:43 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 |