Add a check in eucalyptus-nc to verify that the target can run KVM
Bug #426830 reported by
Etienne Goyer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Wishlist
|
Dustin Kirkland | ||
Karmic |
Fix Released
|
Wishlist
|
Dustin Kirkland |
Bug Description
Binary package hint: eucalyptus-nc
This is a wishlist item.
As it can be hard to track problems running instances on a node controller caused by the node controller not supporting HVM, it would be good if the package installer would warn of the situation. For example, we could just run kvm-ok in the preinst, and report status in a dialog box. This would improve the out-of-the-box experience significantly, reduce the number of people who request help following installation and simplify documentation.
Changed in eucalyptus (Ubuntu Karmic): | |
status: | Triaged → Fix Committed |
To post a comment you must log in.
Etienne-
Hmm, this is a bit easier said than done.
We can't run kvm-ok directly, because the package that provides kvm-ok may be being installed at that time. Note that there's another bug where we're trying to get kvm-ok into the base system files and out of qemu-kvm, Bug #429443.
However, kvm-ok's real meat is a very simple grep of /proc/cpuinfo. That's certainly something that we can do.
I disagree with the concept of a "dialog box", or anything interactive that would hamper unattended installations.
But I can throw a warning message echo'd in the nc postinst, such that the message is at least logged *somewhere*.
:-Dustin