internal error no supported architecture for os type 'hvm'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
libvirt (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
nova (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
On a new 12.10 install following https:/
2012-07-30 14:55:48 TRACE nova.openstack.
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'").
description: | updated |
summary: |
- libvirt_type=qemu is not honored + domain type is always 'kvm', even when kvm is not available |
description: | updated |
description: | updated |
summary: |
- domain type is always 'kvm', even when kvm is not available + internal error no supported architecture for os type 'hvm' |
Changed in nova: | |
status: | New → Incomplete |
Changed in nova (Ubuntu): | |
status: | New → Incomplete |
Changed in libvirt (Ubuntu): | |
importance: | Undecided → Medium |
Changed in nova (Ubuntu): | |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Incomplete → Confirmed |
Changed in nova: | |
status: | Confirmed → Invalid |
So Daviey tells me that 'libvirt_type=qemu' doesn't necessarily mean --disable-kvm. I think there is a bug in how even if I reload my host's kvm_intel with nested=0 that openstack does not fallback to qemu -disable-kvm, but that is probably not a priority. The bigger issue is that a precise host booting a quantal guest results in the quantal guest being unable to load the kvm_intel module. I'll file another bug for that.