The problem is that menu.lst is generated via the grub-legacy-ec2 package. In order to determine the appropriate kernels it looks for -virtual and then excludes the other kernels before adding the others. In this case, since -generic is the new -virtual, a valid kernel is not being choosen. This is a simple one-line fix.
Merge proposal is out for smoser.
=== modified file 'debian/update-grub-legacy-ec2'
--- debian/update-grub-legacy-ec2 2011-03-02 04:22:28 +0000
+++ debian/update-grub-legacy-ec2 2012-05-28 22:33:17 +0000
@@ -1401,7 +1401,7 @@
is_xen_kernel() {
case "${1}" in
*-ec2) return 0;;
- *-virtual)
+ *-virtual|*-generic)
# input is like /boot/vmlinuz-2.6.35-13-virtual
# get the version string out of it.
local ver=""
Tested and submitted fixed.
The problem is that menu.lst is generated via the grub-legacy-ec2 package. In order to determine the appropriate kernels it looks for -virtual and then excludes the other kernels before adding the others. In this case, since -generic is the new -virtual, a valid kernel is not being choosen. This is a simple one-line fix.
Merge proposal is out for smoser.
=== modified file 'debian/ update- grub-legacy- ec2' update- grub-legacy- ec2 2011-03-02 04:22:28 +0000 update- grub-legacy- ec2 2012-05-28 22:33:17 +0000 *-generic) 2.6.35- 13-virtual
--- debian/
+++ debian/
@@ -1401,7 +1401,7 @@
is_xen_kernel() {
case "${1}" in
*-ec2) return 0;;
- *-virtual)
+ *-virtual|
# input is like /boot/vmlinuz-
# get the version string out of it.
local ver=""