[Bug 1031063] Re: domain type is always 'kvm', even when kvm is not available

[Jamie Strandboge]

** Summary changed:

- libvirt_type=qemu is not honored
+ domain type is always 'kvm', even when kvm is not available

** Description changed:

  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 or kvm_intel 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. However, the option for overriding with
- 'libvirt_type=qemu' doesn't seem to work.
+ 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">.

** Description changed:

  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">.
+ type="kvm"> and nova-compute.log shows the same error ("libvirtError:
+ internal error no supported architecture for os type 'hvm'").

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1031063

Title:
  domain type is always 'kvm', even when kvm is not available

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