I got a similar error when I upgraded karmic to lucid by running update-
manager -d. For some reason I was prompted to install linux-virtual and
linux-image-virtual.
This set grub to boot into a generic pae kernel which did not contain
some module required to boot my asus eeepc 1000he netbook corr
Done: Bug #461127
--
linux-image-virtual kernel contains -generic-pae kernel
https://bugs.launchpad.net/bugs/437331
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.u
This is working as designed.
The virtual kernel is supposed to be identical to the server kernel (or
since Karmic: the generic-pae kernel), except with a lot of the modules
removed. To save time and ressources, the -virtual kernel package simply
contains the -server (or now: -generic-pae) kernel i
I've seen this too. The annoying thing is, when you upgrade a Xen DomU
using the -virtual kernel from Jaunty to Karmic, you'll be left with an
unbootable VM (unless you have a different kernel which actually is
DomU-capable installed as a fallback, of course).
--
linux-image-virtual kernel contai
I'm seeing this one too, if you look here:
http://packages.ubuntu.com/karmic/i386/linux-
image-2.6.31-14-virtual/filelist you can see that the package contains
all of the -generic-pae kernel files.
I ran "diff /boot/config-2.6.31-14-generic /boot/config-2.6.31-14
-generic-pae" and the only differe
