Kernel 2.6.38 and VirtualBox 4.0

[felixonmars]

yes, you have to do it again and again until either the kernel or virtualbox
fix it. and I think it would be fixed soon :)
On Feb 18, 2011 12:54 AM, "jcjglt at lagoon.nc" <jcjglt at lagoon.nc> wrote:
> This closed my question :
>
> QUOTE
> A quick and dirty fix could solve this problem.
> create a symlink for generated/autoconf.h
>
> 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
>
> I have now a fully working 2.6.38-3-generic-lucid1 kernel, with a
perfectly steady WiFi (the most important for me), a perfectly working
VirtualBox and a faster laptop. About VirtualBox, the only drawback is that
VirtualBox does not anymore start Windows XP when booted on older kernels
(like 2.6.36-1 which was quite nice kernel also) but as I'm fully satisfied
with 2.6.38, it does not matter.
> One last question : shall I have to run this "dirty fix" each time I
upgrade the kernel ?
> Thanks again Felix yan for your efficiency.
>
> Jean-Claude
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20110218/bc96f1ec/attachment-0001.html>