Ubuntu
virtualbox-ose package

Lucid-10.04-1 VirtualBox-v4.0.2 kernel-2.6.38

Asked by jcglt

I updated my Oracle VM VirtualBox to version 4.0.2 and it runs nicely Windows XP with a 2.6.36-1-generic kernel.
I updated the kernel to 2.6.38-1 then 2.6.38-2 then 2.6.38-4 and with these kernels VirtualBox is not anymore able to start Windows XP. I read somewhere that a patch was needed ? Anyway I might better wait for the official release of kernel 2.6.38 ?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu virtualbox-ose Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
jcglt (jcjglt) said : 		#1

I must add that I'm using VirtualBox 4.0.2 PUEL version, not OSE version, which more limited about USB use.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#2

How did you install the kernel?

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

How did you install the kernel?

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#4

How did you install the kernel?

Revision history for this message
jcglt (jcjglt) said : 		#5

I installed 2.6.38-1 and 2.6.38-2 with Synaptic.
I installed 2.6.38-4 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.38-rc4-natty/ and it installed also quite well by executing the three downloaded .deb files (linux-image...generic...i386, linux-headers and linux-headers-generic).
BUT these three installations had shown at the end of installation the same message of error about VirtualBox driver. VirtualBox 4.0.0 then 4.0.2 started well but inside it Windows XP did not start, showing 2 error boxes and requesting me to run the following command "sudo /etc/init.d/vboxdrv setup", which I'm used to as this command is required nearly every time I update the kernel BUT this time, with these three versions of 2.6.38 this command did not work.

Revision history for this message
Best actionparsnip (andrew-woodhead666) said : 		#6

Then you should contact the maintainer of the kernel to ask. You are using a 3rd party kernel

Revision history for this message
jcglt (jcjglt) said : 		#7

Thanks actionparsnip, that solved my question.

Revision history for this message
jcglt (jcjglt) said : 		#8

I got a working solution to my problem by posting it to "wiki.ubuntu.com/BugSquad".
I got the following answer :
QUOTE
as for your situation, it should be:

sudo ln -s /usr/src/linux-headers-2.6.38-1-generic/include/generated/autoconf.h /usr/src/linux-headers-2.6.38-1-generic/include/linux/

then compile the module again:

sudo service vboxdrv setup

I found another solution in the virtualbox forum but it asks to change several paths in the source code and I think this one is more easy.

(sorry for my poor English)

Felix Yan
UNQUOTE
Even if it is dirty it works perfectly - after I have replaced 2.6.38-1 by my current kernel number 2.6.38-3.
I eventually add that this kernel looks very promising : very fast execution and a working WiFi ! added to that now a working VirtualBox : wonderful.
jcglt