2009-10-15 16:33:47 |
Joseph Salisbury |
bug |
|
|
added bug |
2009-10-15 17:25:29 |
Mathias Gug |
summary |
Unable to start EUC instance on i386 arch |
Unable to start EUC instances - no supported architecture for os type 'hvm' |
|
2009-10-15 17:33:13 |
Mathias Gug |
eucalyptus (Ubuntu): importance |
Undecided |
Medium |
|
2009-10-15 17:33:13 |
Mathias Gug |
eucalyptus (Ubuntu): status |
New |
Confirmed |
|
2009-10-15 20:45:40 |
Dustin Kirkland |
bug task added |
|
qemu-kvm (Ubuntu) |
|
2009-10-15 20:45:50 |
Dustin Kirkland |
eucalyptus (Ubuntu): status |
Confirmed |
Invalid |
|
2009-10-15 20:45:55 |
Dustin Kirkland |
qemu-kvm (Ubuntu): importance |
Undecided |
Wishlist |
|
2009-10-15 20:46:01 |
Dustin Kirkland |
qemu-kvm (Ubuntu): assignee |
|
Dustin Kirkland (kirkland) |
|
2009-10-15 20:46:04 |
Dustin Kirkland |
qemu-kvm (Ubuntu): status |
New |
Triaged |
|
2009-10-15 20:46:17 |
Dustin Kirkland |
summary |
Unable to start EUC instances - no supported architecture for os type 'hvm' |
kvm disable in bios (was: Unable to start EUC instances - no supported architecture for os type 'hvm') |
|
2009-10-16 20:38:32 |
Dustin Kirkland |
qemu-kvm (Ubuntu): status |
Triaged |
In Progress |
|
2009-10-29 16:11:35 |
Dustin Kirkland |
qemu-kvm (Ubuntu): milestone |
|
karmic-updates |
|
2009-10-29 16:11:48 |
Dustin Kirkland |
nominated for series |
|
Ubuntu Karmic |
|
2009-10-29 16:11:48 |
Dustin Kirkland |
bug task added |
|
eucalyptus (Ubuntu Karmic) |
|
2009-10-29 16:11:48 |
Dustin Kirkland |
bug task added |
|
qemu-kvm (Ubuntu Karmic) |
|
2009-10-29 16:21:57 |
Dustin Kirkland |
qemu-kvm (Ubuntu Karmic): importance |
Wishlist |
Low |
|
2009-10-29 16:56:03 |
Dustin Kirkland |
summary |
kvm disable in bios (was: Unable to start EUC instances - no supported architecture for os type 'hvm') |
kvm disabled in bios (was: Unable to start EUC instances - no supported architecture for os type 'hvm') |
|
2009-10-29 17:04:05 |
Dustin Kirkland |
description |
I'm having an issue starting an instance. I see errors stating "disk not found" and "no domain with matching name found". I'm also seeing an error saying "no supported architecture for os type 'hvm'":
Snippet from nc.log:
[Wed Oct 14 14:57:00 2009][001691][EUCAINFO ] currently running/booting: i-39A80763
[Wed Oct 14 14:57:00 2009][001691][EUCAERROR ] libvirt: internal error no supported architecture for os type 'hvm' (code=1)
[Wed Oct 14 14:57:00 2009][001691][EUCAFATAL ] hypervisor failed to start domain
[Wed Oct 14 14:57:00 2009][001691][EUCAERROR ] libvirt: Domain not found: no domain with matching name 'i-39A80763' (code=42)
[Wed Oct 14 14:57:00 2009][001691][EUCAINFO ] vrun(): [rm -rf /var/lib/eucalyptus/instances/admin/i-39A80763/]
[Wed Oct 14 14:57:01 2009][001691][EUCAINFO ] stopping the network (vlan=10)
I have complete log files if needed.
The host os is Karmic i386 and I'm trying to start an i386 instance. There might be a bug trying to run EMIs registered as i386 under
karmic/libvirt.
As a test, I disabled apparmor, but the problem did not go away. |
I'm having an issue starting an instance. I see errors stating "disk not found" and "no domain with matching name found". I'm also seeing an error saying "no supported architecture for os type 'hvm'":
Snippet from nc.log:
[Wed Oct 14 14:57:00 2009][001691][EUCAINFO ] currently running/booting: i-39A80763
[Wed Oct 14 14:57:00 2009][001691][EUCAERROR ] libvirt: internal error no supported architecture for os type 'hvm' (code=1)
[Wed Oct 14 14:57:00 2009][001691][EUCAFATAL ] hypervisor failed to start domain
[Wed Oct 14 14:57:00 2009][001691][EUCAERROR ] libvirt: Domain not found: no domain with matching name 'i-39A80763' (code=42)
[Wed Oct 14 14:57:00 2009][001691][EUCAINFO ] vrun(): [rm -rf /var/lib/eucalyptus/instances/admin/i-39A80763/]
[Wed Oct 14 14:57:01 2009][001691][EUCAINFO ] stopping the network (vlan=10)
I have complete log files if needed.
The host os is Karmic i386 and I'm trying to start an i386 instance. There might be a bug trying to run EMIs registered as i386 under
karmic/libvirt.
As a test, I disabled apparmor, but the problem did not go away.
===========================
SRU Justification
Users trying KVM for the first time often fail to realize that VT is not enabled in their BIOS. We created a kvm-ok script some time ago to help detect if the user's CPU has either the svm or the vmx flag. This has tremendously helped us support KVM, giving users a tool to detect the ability to use KVM. For no good reason, many new laptops shipping with VT extensions in the CPU actually disable this in BIOS by default. Usually, a message is emitted in dmesg. We can very easily detect that message as part of the kvm-ok script. We can and should also check that /dev/kvm exists, ensuring that the kvm kernel module is loaded.
This is a very low risk fix, that provides a a large, positive impact for new KVM users.
TEST CASE:
Assuming you have a system that really does support KVM...
1) Run kvm-ok. You should see that:
a) your cpu supports VT
b) your /dev/kvm device exists
c) no warning message in bios
d) that you can use KVM
2) Now manually cripple your ability to use KVM by doing each of the following, one at a time:
a) run this on a system that does not support VT (such as a virtual machine)
b) sudo modprobe -r kvm, and then re-run kvm-ok and see that /dev/kvm is gone
c) reboot into BIOS, disable VT, and re-run kvm-ok
=========================== |
|
2009-10-29 17:16:11 |
Dustin Kirkland |
attachment added |
|
452323.patch http://launchpadlibrarian.net/34608998/452323.patch |
|
2009-10-29 18:24:01 |
Dustin Kirkland |
qemu-kvm (Ubuntu Karmic): status |
In Progress |
Fix Committed |
|
2009-10-29 18:39:49 |
Martin Pitt |
qemu-kvm (Ubuntu): milestone |
karmic-updates |
|
|
2009-10-30 08:46:54 |
Martin Pitt |
tags |
|
verification-needed |
|
2009-10-30 17:03:18 |
Dustin Kirkland |
attachment added |
|
out http://launchpadlibrarian.net/34703999/out |
|
2009-11-03 17:49:33 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic-proposed/qemu-kvm |
|
2009-11-03 18:59:26 |
Martin Pitt |
tags |
verification-needed |
verification-donee |
|
2009-11-03 18:59:33 |
Martin Pitt |
tags |
verification-donee |
verification-done |
|
2009-11-03 23:33:16 |
Launchpad Janitor |
qemu-kvm (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
2009-11-03 23:34:27 |
Martin Pitt |
qemu-kvm (Ubuntu): status |
In Progress |
Fix Released |
|
2009-11-03 23:34:55 |
Martin Pitt |
qemu-kvm (Ubuntu Karmic): status |
Fix Released |
Fix Committed |
|
2009-11-09 10:14:25 |
Launchpad Janitor |
qemu-kvm (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
2010-04-07 05:39:14 |
mohanv |
attachment added |
|
Screenshot of the install process that warns that there is no hardware acceleration but proceeds witht he installation http://launchpadlibrarian.net/43322721/Eucalyptusnc-install.png |
|