After Kernel Update, Virtual Box Will Not Work. Needs Update. <SOLVED>

[n8xk]

After a kernel update I found that Virtual Box will not work and needs to be updated.

The dialog box says "kernel driver not installed (rc=-1908), and that I should reinstall the kernel module by running as root the following: /etc/init.d/vboxdrv setup
Is this this the best way to update, or should I run "Get Virtual Box" again?

I am concerned when I update, I will have to reinstall the two OS's that I currently have installed on Virtual Box.
Can the .vdi files be saved and reinstalled on the updated VB?

n8xk

[djohnston]

You need to reboot. You should have a DKMS module installed for VBox already. On reboot, it should insert into the new kernel.

[YouCanToo]

After a kernel update I found that Virtual Box will not work and needs to be updated.

The dialog box says "kernel driver not installed (rc=-1908), and that I should reinstall the kernel module by running as root the following: /etc/init.d/vboxdrv setup
Is this this the best way to update, or should I run "Get Virtual Box" again?

Try doing just what it said to do and it will work!

I am concerned when I update, I will have to reinstall the two OS's that I currently have installed on Virtual Box.
Can the .vdi files be saved and reinstalled on the updated VB?

n8xk[/color][/color]

Before jumping to conclusions about what may or may not be, try doing just what it said to do.  You might find that it works!

[n8xk]

Tried to reboot first and have the same problem. I then ran /etc/init.d/vboxdrv setup and this was the result:

[n8xk@localhost ~]$ su
Password:
[root@localhost n8xk]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules                              [  OK  ]
Uninstalling old VirtualBox DKMS kernel modules                 [  OK  ]
Trying to register the VirtualBox kernel modules using DKMS
Error! Bad return status for module build on kernel: 2.6.38.8-pclos1.bfs (i586)
Consult the make.log in the build directory
/var/lib/dkms/vboxhost/3.2.12/build/ for more information.
                                                                [FAILED]
  (Failed, trying without DKMS)
Recompiling VirtualBox kernel modules                           [FAILED]
  (Look at /var/log/vbox-install.log to find out what went wrong)

Tried to look at /var/log/vbox-install.log and got:

[root@localhost n8xk]#  /var/log/vbox-install.log
bash: /var/log/vbox-install.log: Permission denied


If I boot into the old kernel, VB works as it should. The reason I updated the kernel is the system will sometimes crash during boot with the old kernel. With the new kernel, boot up is fine but VB is broken.

[djohnston]

n8xk,

That's odd. I've never seen it fail like that before. First time for everything, I guess.

Rerun getvirtualbox. It should recreate the DKMS kernel module. Reboot immediately after VirtualBox is reinstalled. If there's a boot splash screen, press the Escape key at the prompt to see the boot messages and verify that a kernel module does build.

You won't have to reinstall any VMs, and the installation process won't erase any of them.

[Rudge]

Were you booted into the "current" kernel when you did the /etc/init.d/vboxdrv setup?

Don't try this from the old kernel.

[AS]

/var/lib/dkms/vboxhost/3.2.12/build/ for more information.

You need to update your virtualbox installation. Should be 4.0.12 actually.

AS

[Old-Polack]

/var/lib/dkms/vboxhost/3.2.12/build/ for more information.

You need to update your virtualbox installation. Should be 4.0.12 actually.

AS

Good catch. 

[AS]

/var/lib/dkms/vboxhost/3.2.12/build/ for more information.

You need to update your virtualbox installation. Should be 4.0.12 actually.

AS

Good catch. 

The advantage of being late to the party! 

[menotu]

I will have to reinstall the two OS's that I currently have installed on Virtual Box.
Can the .vdi files be saved and reinstalled on the updated VB?

Yes, they are separate files which can be used again and again;  If you set up a new VM you can simply point it to the VDI file and voila.  All it basically does is mimic being a real hard drive.

I find it worthwhile making copies of them and storing them on a backup drive/partition etc....

You can also export the whole VM which can then be imported into another machine and so on but I personally find the VDI copy far simpler.

[n8xk]

 Will post results later when I return home from helping a friend with a work project.

Thanks for all the replies.

n8xk

[n8xk]

After running "Get Virtual Box" and installing the latest version everything is working again.

Did not have to reinstall any OS to VB, that was my concern because a certain non Linux OS is a big hassle to install.

Glad to know the .vdi file can be saved and reinstalled. I will add those files to my back up.

Thanks for all the help, the PCLOS forum is a fantastic group.

n8xk

[djohnston]

Good to have you here, n8xk. Please edit your first post to include SOLVED in the title.