yahoo-eng-team team mailing list archive

[Park <heijlong@xxxxxxxxxxxxxxxxxx>]

from Daniel P.Berrange(berrange@xxxxxxxxxx)

If you set  'cpu_mode=host-model' or 'cpu_mode=host-passthrough'
then it will take effect, as the guest will see the full CPU model
of the host that is picked. IMHO the capabilities:cpu_info:features
filter only makes sense when using those two cpu modes. If you
left the default cpu_mode=None or set cpu_mode=custom, then this
capabilities feature is meaningless from a conceptual POV. So the
fact that it has no effect on the guest CPU is not a bug it is
by design.
-----------------------
so this  is not a bug it is by design. I will close it...

** Changed in: nova
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1412930

Title:
  CPU feature request is not respected when create VM

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  When creating a VM requiring some specific CPU features, although the
  guest will be scheduled to a host with the capability, but such
  information is not  always exposed to guest.

  	a) started devstack by default, (means nova configuration libvirt.cpu_mode=none), the compute node has the SSE4.1 support
          b) create flavor with {"capabilities:cpu_info:features": "<in> sse4.1"} extra spec, i.e. requiring SSE4.1.
  	c) launch an instance with the flavor.
          d) ssh to instance and 'cat /proc/cpuinfo'.

  The SSE4.1 is not presented in guest.

  I think the reason is because when libvirt.cpu_mode is none, libvirt
  will not specify the feature request in the guest  vcpu config.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1412930/+subscriptions