virtualbox.org

Hi all!

I uninstalled VirtualBox 1.6.6 from my kubuntu 7.10 system, and installed the correct .deb of VirtualBox 2.0.0, but if I try to start my virtual install of win XP I get this error: I know perfectly fine what it means, but how do I fix it?
(I tried a reinstall, but that's completely pointless since installed deb packages are the same each time you try it again.)

I guess the VirtualBox kernel module is still the 1.6.6 version, but can I manually upgrade it?

I first thought I simply needed to reboot, so that the newer kernel module would get loaded but that's not the case.

Or you could simply update the Guest Additions from 1.6.6 to 2.0.0??

I do not think this has anything to do with the guest additions. These only work when the guest OS is booted up to the point where various drivers and services are started. I get the error immediately when I try to run the virtual machine, even before the 'fake' bios starts running, so the guest additions are in no way active or contributing to the problem. I would also think the guests are able to boot with older guest additions, otherwise the additions would need to be removed before one can upgrade VirtualBox itself.

The problem I have is the software that is needed on the host system, on linux this is a kernel module that provides various functions to the VirtualBox program. (At least this is the way that Vmware does it, it must be the same with VirtualBox.)

Thanks for thinking along though.

Did you reboot Ubuntu after the install?

I tried that, but it did not help.

I mentioned this in my first post, but I was not very clear in my writing.

I upgraded to 2.0 today too, and I saw some residual config left from 1.6.6 in my package manager. The only way to remove that, was uninstall 2.0, install 1.6.6 again and purge remove it. After that, I installed 2.0 again and it works like a charm. Be sure to clear your DKMS tree too before installing 2.0 after the full removal of 1.6.6.

Indeed, that helped. Thanks a lot!

Would this be a bug with the deb packaging system? Or is VirtualBox responsible?

I guess more people might encounter this.

I think both. First VB because it doesn't update the kernel module properly, second the install system of the distro for not clearing the files correctly.