@Axel: Very nice! Thanks for this solution. I didn’t think about that and jumping ship to the non ose version just seemed like a logical next step. Perhaps this will help someone who doesn’t want to make that leap. :)

You can repair your virtualbox install on gutsy with a 2.6.22-15 kernel by :
– removing virtualbox 2.6.22-14 module :

apt-get remove virtualbox-ose-modules-2.6.22-14-generic

– rebuild the module for the new kernel :

m-a auto-install virtualbox-ose-source

– reinstall virtualbox :

apt-get install virtualbox-ose

You are my hero. I’ve been holding off on the 2.6.22-14 -> 2.6.22-15 update for a long time because I knew my binary nvidia drivers would be an issue.. Anyways, I bit the bullet and upgraded to 2.6.22-15 and (OOPS) I didn’t expect vbox kernel modules to have a problem. Anyways– thanks for the advice.. moving to this non-opensource version was pretty much a breeze — it even converted my old Virtualbox config files from the “old” format to the “new” format. I didn’t loose any data on my virtualized host operating systems. Woo HOO!!!!!!

It’s pretty easy to build a .deb for the vboxdrv module for gutsy along the lines of:
apt-get source virtualbox-ose-modules-2.6.22-14-generic
apt-get build-dep virtualbox-ose-modules-2.6.22-14-generic

Then edit the debian/control file to change the version to -15 and build the package with dpkg-buildpackage -B

Installation of the resulting .deb requires removing the -14 version first with dpkg –force-depends

[quote post=”2554″]After a recent kernel upgrade it also complained over the kernel module not being compatible. However, my error message said something like: “run /etc/init.d/virtualbox setup”. This gave a “recompiling kernel module”, and then it worked again. But it may very well be that this only works for the manually installed non-ose version.[/quote]

Yep. The OSE version gives the same message, but /etc/init.d/virtualbox does not recognize the “setup” command. It only knows about start, stop and restart.

The non OSE version can recompile it’s own modules I believe.

Don’t expect a totally smooth upgrade to Hardy. I made a clean install on my home computer on the release day, and have had quite some issues with many components that have been swapped out with “better” alternatives I am less used to. Some examples: Pulseaudio for audio gives endless issues with Skype, Xrandr for multimonitor xorg support that I just failed to configure for my nvidia card, gnome-vfs -> gvfs breaks certain things, the default firefox (Firefox 3 beta 5) had freezing issues, the bluetooth layer seems to have changed subtly, there are new issues with suspend to ram for me, and for the first time in my life on Linux/unix I had an uninteruptable process take 100% cpu :(.

On that computer I actually have the non-ose Virtualbox. After a recent kernel upgrade it also complained over the kernel module not being compatible. However, my error message said something like: “run /etc/init.d/virtualbox setup”. This gave a “recompiling kernel module”, and then it worked again. But it may very well be that this only works for the manually installed non-ose version.

Same problem here.
Finally, I’ve done the same you did: installed the PUEL version.

If everything works I see no reason to upgrade. If I’m having problems, I will upgrade. As simple as that.

If a distro is unsupported, I’ll upgrade. I’ll also install Hardy if I ever want to make a new Ubuntu install.

Heh! Good to know I’m not the only “late adopter” out there. :)

Clinging to Gusty? I’m still on Fiesty on my primary machine, Edgy on one, and Gusty on my family’s computers. I haven’t even tried Hardy.