yahoo-eng-team team mailing list archive

[Joe Gordon <1031063@xxxxxxxxxxxxxxxxxx>]

** 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/1031063

Title:
  internal error no supported architecture for os type 'hvm'

Status in OpenStack Compute (Nova):
  Invalid
Status in “libvirt” package in Ubuntu:
  Expired
Status in “nova” package in Ubuntu:
  Expired

Bug description:
  On a new 12.10 install following https://wiki.ubuntu.com/SecurityTeam/TestingOpenStack, if I set 'libvirt_type=qemu', restart nova and then try to start an instance, I can see in /var/log/nova/nova-compute.log that it is defaulting to 'kvm' and not 'qemu'. I then end up with the following error:
  2012-07-30 14:55:48 TRACE nova.openstack.common.rpc.amqp libvirtError: internal error no supported architecture for os type 'hvm'

  This might be a problem in libvirt on the host. I noticed that
  nested=1 for kvm_intel on my host and 'vmx' shows up in 'virsh
  capabilities' in the openstack guest, but in the guest I am unable to
  load kvm_intel (bug #1031090). However, the option for overriding with
  'libvirt_type=qemu' doesn't seem to work. Also, if I reload the
  kvm_intel module with nested=0, and start the guest, it correctly does
  not load the kvm module, but nova incorrectly tries to start guests
  with <domain type="kvm"> and nova-compute.log shows the same error
  ("libvirtError: internal error no supported architecture for os type
  'hvm'").

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