Upgrade 2.1.4 (Intrepid) to 2.2.2 (Jaunty)

[Snowmiss]

After I upgraded my host from Kubuntu 8.10 (64bit) to 9.04 (64bit), I now want to upgrade my VBox from 2.1.4 to 2.2.2
Unfortunatly the .deb package I downloaded reports a conflict, which of course is because of the the original 2.1.4 was an Intrepid version and now I want to install a Jaunty one.

After reading some posts here, I concluded that:
- I needed to backup the .VirtualBox folder in my /home
- Uninstall VB 2.1.4
- put the backup folder back
- install VB 2.2.2

First question: how do I uninstall VB 2.1.4, I can't find VBox with Adept package installer and I'm not sure what I have to remove manual so VB 2.1.4. is completely removed (everything in /usr/bin ??)
Second question: Do I have to reinstall GA (since it was installed in the original guests)?

Thanx for reading and if any extra info is needed, please let me know.

[BassKozz]

After reading some posts here, I concluded that:
- I needed to backup the .VirtualBox folder in my /home
- Uninstall VB 2.1.4
- put the backup folder back
- install VB 2.2.2

You don't need to put the backup folder back... when you uninstall 2.1.4 the files for your virtual machines remain in place. But I do recommend backing them up just to be safe.

First question: how do I uninstall VB 2.1.4, I can't find VBox with Adept package installer and I'm not sure what I have to remove manual so VB 2.1.4. is completely removed (everything in /usr/bin ??)

Code: Select all

sudo apt-get remove virtualbox-2.1

Second question: Do I have to reinstall GA (since it was installed in the original guests)?

Not sure?
I just upgraded from Intrepid to Jaunty and VB from 2.1.4 to 2.2.2 and I did reinstall the Guest Additions just to be safe... I guess it doesn't hurt.

[Snowmiss]

Ok, now I have savely removed the old vbox and installed the new one.
Once I started this I got this error:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

First I checked if DKMS was installed, and it is.
Then I ran

Code: Select all

sudo /etc/init.d/vboxdrv setup

But something went wrong see this /var/log/vbox-install-log:

Attempting to install using DKMS
removing old DKMS module vboxdrv version 2.2.2

------------------------------
Deleting module version: 2.2.2
completely from the DKMS tree.
------------------------------
Done.

Creating symlink /var/lib/dkms/vboxdrv/2.2.2/source ->
/usr/src/vboxdrv-2.2.2

DKMS: add Completed.

Error! Your kernel source for kernel 2.6.27-11-generic cannot be found at
/lib/modules/2.6.27-11-generic/build or /lib/modules/2.6.27-11-generic/source.
You can use the --kernelsourcedir option to tell DKMS where it's located.
Failed to install using DKMS, attempting to install without
Makefile:140: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.

I noticed that I do have a /lib/modules/2.6.28-11-generic/build which holds the kernel source for my 2.6.28-11-generic kernel but
where to use the --kernelsourcedir option? or that other KERN_DIR=<directory> and run Make again?

[Sasquatch]

Error! Your kernel source for kernel 2.6.27-11-generic cannot be found at
/lib/modules/2.6.27-11-generic/build or /lib/modules/2.6.27-11-generic/source.

Which kernel did you boot? After upgrading to 9.04, you should be asked if the upgrade should remove old packages and that kernel is one of them to be removed. Boot to the latest kernel, 2.6.28-11, and then run the vboxdrv setup command again. Make sure you have the header files installed. You might want to remove the DKMS modules first before running the setup.

Code: Select all

sudo dkms remove -m vboxdrv -v 2.2.2 --all
sudo dkms remove -m vboxnetflt -v 2.2.2 --all

Check the versions with dkms status first in case other versions are in the dkms tree.

[Snowmiss]

Error! Your kernel source for kernel 2.6.27-11-generic cannot be found at
/lib/modules/2.6.27-11-generic/build or /lib/modules/2.6.27-11-generic/source.

Which kernel did you boot? After upgrading to 9.04, you should be asked if the upgrade should remove old packages and that kernel is one of them to be removed.

Good question, I just found out I was still booting the 8.10, kernel 2.6.27-11. I have added the new 2.6.28-11-generic kernel to grub.lst and rebooted.
I did not do anything else and vbox 2.2.2 is now running and so is my XP guest.

Boot to the latest kernel, 2.6.28-11, and then run the vboxdrv setup command again. Make sure you have the header files installed. You might want to remove the DKMS modules first before running the setup.

Code: Select all

sudo dkms remove -m vboxdrv -v 2.2.2 --all
sudo dkms remove -m vboxnetflt -v 2.2.2 --all

Check the versions with dkms status first in case other versions are in the dkms tree.

This I didn't do, and it's working, is there a reason why I still should do this?

Thanx so far

[Sasquatch]

If everything is working, you can run the status command just to be sure, but there should be only one module version now. Other versions should be removed when you upgraded to 2.2.2.

[Snowmiss]

after running dkms status I got this:

vboxdrv, 2.2.2, 2.6.28-11-generic, x86_64: installed (WARNING! Diff between built and installed module!)
fglrx, 8.600, 2.6.27-11-generic, x86_64: installed
fglrx, 8.600, 2.6.28-11-generic, x86_64: installed

So it's not complete right. But if it works, it works and we'll see what happens when I upgrade next october... (or earlier, if I deceide to do a complete re-install of everything (including OS) to a new HD)

[Sasquatch]

With that warning, I advise you to run the vboxdrv setup command again. If that doesn't fix the difference, then remove the module through dkms remove as noted above, then run the setup command again. That should clear all the errors there are.
A new VB release should also clear this error, as it will ship a new version of the kernel module.