yahoo-eng-team team mailing list archive

["jiang, yunhong" <1412994@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I try to set the libvirt.cpu_mode=custom and libvirt.cpu_model=pentium,
and then boot a vm using cirros image. The 'nova boot' command create
the instance successfully while the instance failed to boot because the
image requires x86_64 while pentium has no x86_64 support.

Then I try to  set the image's architecture property to be x86_64, with
"glance image-update IMG-UUID --property architecture=x86_64". After
this, the instance is created successfully by 'nova boot' but instance
still fails to boot.

I think the reason is because, when libvirt_cpu_model=perntium, the
compute node should in fact report it's capability as that of Pertium
processor, instead of the host processor anymore.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1412994

Title:
  cirros image fails to boot when libvirt.cpu_mode=custom and
  libvirt.cpu_model=pentium

Status in OpenStack Compute (Nova):
  New

Bug description:
  I try to set the libvirt.cpu_mode=custom and
  libvirt.cpu_model=pentium, and then boot a vm using cirros image. The
  'nova boot' command create the instance successfully while the
  instance failed to boot because the image requires x86_64 while
  pentium has no x86_64 support.

  Then I try to  set the image's architecture property to be x86_64,
  with "glance image-update IMG-UUID --property architecture=x86_64".
  After this, the instance is created successfully by 'nova boot' but
  instance still fails to boot.

  I think the reason is because, when libvirt_cpu_model=perntium, the
  compute node should in fact report it's capability as that of Pertium
  processor, instead of the host processor anymore.

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