Allow ability to disable individual CPU features via `cpu_model_extra_flags`

Bug #1852437 reported by Kashyap Chamarthy on 2019-11-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)

Bug Description


When using a custom CPU model, Nova currently allows enabling
individual CPU flags/features via the config attribute,

    cpu_model_extra_flags="pcid,ssbd, md-clear"

The above only lets you enable the CPU features. This RFE is to also
allow _disabling_ individual CPU features.


A couple of reasons:

  - An Operator wants to generate a baseline CPU config (that facilates
    live migration) across his Compute node pool. However, a certain
    CPU flag is causing an inteolerable performance issue for their
    guest workloads. If the Operator isolated the problem to _that_
    specific CPU flag, then she would like to disable the flag.

  - More importantly, a specific CPU flag might trigger a CPU
    vulnerability. In such a case, the mitigation for it could be to
    simply _disable_ the offending CPU flag.

Allowing disabling of individual CPU flags via Nova would enable the
above use cases.


By allowing the notion of '+' / '-' to indicate whether to enable to
disable a given CPU flag.

E.g. if you specify the below in 'nova.conf' (on the Compute nodes):


Then, when you start an instance, Nova should generate the below XML:

    <cpu match='exact'>
      <model fallback='forbid'>IvyBridge</model>
      <feature policy='require' name='pcid'/>
      <feature policy='disable' name='mtrr'/>
      <feature policy='require' name='ssbd'/>

Note that the requirement to specify '+' / '-' for individual flags
should be optional. If neither is specified, then we should assume '+',
and enable the feature (as shown above for the 'ssbd' flag).

Matt Riedemann (mriedem) wrote :

This is a feature request, not really a bug, so a specless blueprint would be more appropriate for this.

Changed in nova:
importance: Undecided → Wishlist
tags: added: libvirt
Kashyap Chamarthy (kashyapc) wrote :

Blueprint for the above:

(Maybe should close this bug and track it in the blueprint above?)

Changed in nova:
status: New → Invalid
Kashyap Chamarthy (kashyapc) wrote :

A note on bug metadata: I marked this as "Invalid" only because (a) it is being tracked via the blueprint mentioned in comment#2 above, and the feature request is quite valid and enables important use cases; (b) I don't see a better 'Status' field in Launchpad to indicate point (a).

Changed in nova:
status: Invalid → Triaged
importance: Wishlist → Medium
sean mooney (sean-k-mooney) wrote :

setting this back to invalid as Matt Riedemann siad this is a feature not a bug fix.
it is trcked as a blueprint and we shoudl use that to track it
not this bug.

Changed in nova:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers