Bug 1571744

Summary: [RFE][Deployment] add ability to configure extra CPU flags for named CPU models
Product: Red Hat OpenStack Reporter: Rajesh Tailor <ratailor>
Component: puppet-novaAssignee: Rajesh Tailor <ratailor>
Status: CLOSED ERRATA QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: awaugama, berrange, dasmith, eglynn, jamsmith, jhakimra, jjoyce, jschluet, kchamart, lyarwood, mtessun, nlevinki, owalsh, ratailor, rhos-docs, sbauza, sferdjao, sgordon, slinaber, srevivo, tvignaud, vromanso
Target Milestone: z3Keywords: FutureFeature, InstallerIntegration, Triaged, ZStream
Target Release: 12.0 (Pike)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: puppet-nova-11.5.0-2.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 the ``nova.conf`` file for usage details.
Story Points: ---
Clone Of: 1547954 Environment:
Last Closed: 2018-08-20 12:59:48 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, 1571750, 1571756, 1612360    
Bug Blocks: 1571741    

Comment 13 errata-xmlrpc 2018-08-20 12:59:48 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/RHSA-2018:2331