linux-image-2.6.27(-7)-virtual contains server kernel ...
Hi,
according to http://
Best Regards
Ulf
P.S. Found (from my point of view) related issues/bugs:
https:/
https:/
https:/
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://
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-
make -C /lib/modules/
make[1]: Entering directory `/usr/src/
CC [M] /tmp/vmware-
CC [M] /tmp/vmware-
CC [M] /tmp/vmware-
/tmp/vmware-
/tmp/vmware-
CC [M] /tmp/vmware-
LD [M] /tmp/vmware-
Building modules, stage 2.
MODPOST 1 modules
WARNING: "VMCIDatagram_
WARNING: "VMCIDatagram_
WARNING: "VMCIEvent_
WARNING: "VMCI_DeviceGet" [/tmp/vmware-
WARNING: "VMCIMemcpyFrom
WARNING: "VMCIQueuePair_
WARNING: "VMCI_GetContextID" [/tmp/vmware-
WARNING: "VMCIDatagram_Send" [/tmp/vmware-
WARNING: "VMCIQueuePair_
WARNING: "VMCIEvent_
WARNING: "VMCIMemcpyToQu
CC /tmp/vmware-
LD [M] /tmp/vmware-
make[1]: Leaving directory `/usr/src/
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- 2009-10-08
- Last reply:
- 2010-08-02
BenHoltz (benholtz) said : | #1 |
Try virtual Box.
http://
It should also be able to be found under "Applications>Add/ Remove..."
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
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.
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/
I'll look into enabling PAE and if that is sucessfull trying to compile the VMWare-Tools again.
Best Regards
Ulf
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.