linux-image-virtual kernel contains -generic-pae kernel

[Der]

I installed on vmware server 2.0 Ubuntu karmic alpha#6 using virtual mode from the F4 options menu.

uname -a is showing the wrong name for the kernel:

root@karmic:~# uname -a
Linux karmic 2.6.31-11-generic-pae #36-Ubuntu SMP Fri Sep 25 07:50:01 UTC 2009 i686 GNU/Linux

aptitude shows:

i(nstalled) linux-image-2.6.31-11-virtual
i(nstalled) linux-image-virtual
p(not installed) linux-image-2.6.31-11-generic-pae

So the right kernel is being installed but something is naming the virtual kernel to generic-pae, all the contents of /boot show as *-generic-pae.

[mschaeffler (mschaeffler)]

Not only the naming is wroinmg, but several kernel modules are missing also.

[Shane O'Connell (shaneoc)]

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 difference was that PAE was enabled.. I'm not sure if there's other options that are supposed to be set for a -virtual kernel, but it looks like it's an actual -generic-pae kernel, not a -virtual one which was accidentally given the wrong name.

[mks99 (launchpad-schoenhaber)]

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).

[Soren Hansen (soren)]

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 image as well as some of the corresponding modules. It has been that way since 8.10 (Intepid Ibex).

If you find that this kernel does not work as a domU, file a different bug about it, as that's a different bug, and a regression that needs to be fixed.

[mks99 (launchpad-schoenhaber)]

Done: Bug #461127

[sid (skattoju)]

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 correctly (no wifi, low graphics mode etc.)

Booting with an earlier kernel and uninstalling linux-image-virtual and linux-virtual fixed the issue.

I am guessing this is an intermittent issue and not really a bug. Its strange that the updater wanted to install the linux-virtual package. Any feedback is much appreciated.