Ubuntu
linux-meta package

linux-image-2.6.27(-7)-virtual contains server kernel ...

Asked by Ulf

Hi,

according to http://packages.ubuntu.com/intrepid/i386/linux-image-2.6.27-7-virtual/filelist the package with the kernel which afaik is meant for virtual machines contains a server kernel. Lead to a problem for me as my system couldn't boot anymore, as this kernel requires PAE which VMware Workstation doesn't seem to provide. Had to go back to a generic kernel to make my system boot with a current kernel. Can somebody please shed some light on this? Maybe it's just me not understand how things work, but virtual and server sound like different things right? Thanks.

Best Regards

Ulf

P.S. Found (from my point of view) related issues/bugs:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/293831
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/247588
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/295347
Something has happened to the virtual package which is not only affecting me ...

P.P.S (edited) Looks to me like this change made the virtual package contain the server kernel (from http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-meta/linux-meta_2.6.27.9.13/changelog):

linux-meta (2.6.27.5.6) intrepid; urgency=low

  [ Soren Hansen ]

  * Re-add meta packages for virtual kernel flavour (LP: #276292)
  * Remove "restricted/" from linux-server's Section. It has no dependencies
    in restricted.

 -- Ben Collins <email address hidden> Tue, 07 Oct 2008 06:10:08 -0400

P.P.P.S. Using the generic kernel instead of the "real" virtual prevents me from successfully compiling the VMtools:

Building the vsock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vsock-only'
make -C /lib/modules/2.6.27-9-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.27-9-generic'
  CC [M] /tmp/vmware-config0/vsock-only/linux/af_vsock.o
  CC [M] /tmp/vmware-config0/vsock-only/linux/driverLog.o
  CC [M] /tmp/vmware-config0/vsock-only/linux/util.o
/tmp/vmware-config0/vsock-only/linux/util.c: In function ‘VSockVmciLogPkt’:
/tmp/vmware-config0/vsock-only/linux/util.c:157: warning: format not a string literal and no format arguments
  CC [M] /tmp/vmware-config0/vsock-only/linux/vsockAddr.o
  LD [M] /tmp/vmware-config0/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Subscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_DeviceGet" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyFromQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Detach" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Alloc" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Unsubscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyToQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
  CC /tmp/vmware-config0/vsock-only/vsock.mod.o
  LD [M] /tmp/vmware-config0/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-9-generic'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config0/vsock-only'
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/vsock.o': -1 Unknown symbol in module

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu linux-meta Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
BenHoltz (benholtz) said : 		#1

Try virtual Box.
http://virtualbox.org/

It should also be able to be found under "Applications>Add/ Remove..."

Revision history for this message
Ulf (ulf-bremer) said : 		#2

Hi Ben,

I agree that I could do this or go any of a dozend possible ways to avoid this problem, e.g. get rid of Ubuntu and even linux completely but this isn't really my intention.

Best Regards

Ulf

Revision history for this message
Andy Whitcroft (apw) said : 		#3

Generally virtualised use of the kernel is for server instances and as such the virtual kernel is derivative of the server kernel configs wise. Enabling PAE is generally a good things in any case as it brings NX support and greater security, particularly relevant for virtual servers.

Revision history for this message
Ulf (ulf-bremer) said : 		#4

Hi Andy,

I agree with you that PAE is a good thing, but changing this on the fly which prevents a VM from booting (without manual fallback/intervention) in VM Workstation and Player doesn't seem like a great idea to me.

I'll look into enabling PAE and if that is sucessfull trying to compile the VMWare-Tools again.

Best Regards

Ulf

Revision history for this message
Cameron W (cwill747) said : 		#5

Don't know if you still have this problem. The bugs have been invalidated or fixes released for them. Do you still have this problem? And virtualbox, by the way, is an ubuntu package. Not really a workaround.

Can you help with this problem?

Provide an answer of your own, or ask Ulf for more information if necessary.

To post a message you must log in.