** Description changed: 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 + + ===========================
-- kvm disabled in bios (was: Unable to start EUC instances - no supported architecture for os type 'hvm') https://bugs.launchpad.net/bugs/452323 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
