For maverick the -virtual kernel is generated directly in its own right
so this cannot occur there, will close for development.
Looking at the lucid meta packages for the linux-image-virtual, we seem
to be linking to the right linux binary image package:
Package: linux-image-virtual
Architecture: i386 amd64
Section: metapackages
Priority: optional
Depends: ${misc:Depends}, linux-image-${kernel-abi-version}-virtual,
linux-firmware
Description: Linux kernel image for virtual machines
This package will always depend on the latest kernel image available
for virtual machines.
Looking at the Lucid linux-image-xxx-virtual package it does indeed
contain the generic-pae binaries:
$ dpkg -x linux-image-2.6.32-23-virtual_2.6.32-23.37_i386.deb LL
$ ls LL/boot
config-2.6.32-23-generic-pae vmlinuz-2.6.32-23-generic-pae
System.map-2.6.32-23-generic-pae
This is also true in Karmic
$ dpkg -x linux-image-2.6.31-22-virtual_2.6.31-22.60_i386.deb KK
$ ls KK/boot
config-2.6.31-22-generic-pae vmlinuz-2.6.31-22-generic-pae
System.map-2.6.31-22-generic-pae
Back in Hardy we did include -virtual:
$ dpkg -x linux-image-2.6.24-28-virtual_2.6.24-28.71_i386.deb HH
$ ls HH/boot
abi-2.6.24-28-virtual System.map-2.6.24-28-virtual
config-2.6.24-28-virtual vmlinuz-2.6.24-28-virtual
This is intential and due to the way in which the virtual packages are
generated. In Hardy they were a complete separate flavour with their
own configuration. For release Intrepid thorugh Lucid the virtual
flavour was generated from the server flavour (generic-pae for i386 in
Karmic and later). For Maverick and later we are returning to
generating these as their own flavour.
--
linux-image-virtual installs PAE kernel instead
https://bugs.launchpad.net/bugs/601192
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
