[!M03!]

I've been running kali on my laptop as my main OS for some time now and have always used virtualbox to run windows for development. Recently I did a dist upgrade and my virtualbox is now having issues with DKMS. I've googled everywhere for solutions, but this one seems unique in the sense that none of the solutions on google fix the problem!

I've purged virtualbox, dkms, and also did a locate for anything related to virtualbox and removed everything!
I've compiled from source, installed from deb, installed from apt & nothing seems to work! Really frustrated as I have a lot of development stuff not backed up on my windows vdi image.

here is the issue....

m03@KALI:~$ uname -a
Linux KALI 3.12-kali1-amd64 #1 SMP Debian 3.12.3-1~kali2 (2013-12-20) x86_64 GNU/Linux
m03@KALI:~$ file /usr/src/linux-headers-$(uname -r)
/usr/src/linux-headers-3.12-kali1-amd64: directory

root@KALI:/# virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (3.12-kali1-amd64) or it failed to
load. Please recompile the kernel module and install it by

sudo /etc/init.d/vboxdrv setup

You will not be able to start VMs until this problem is fixed.

okay so let's do what they said...

root@KALI:/# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMS ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)

fails.... here is dmesg...

root@KALI:/# dmesg | grep vboxdrv
[61718.158213] vboxdrv: disagrees about version of symbol sched_setscheduler
[61718.158219] vboxdrv: Unknown symbol sched_setscheduler (err -22)
[61718.158228] vboxdrv: disagrees about version of symbol wake_up_process
[61718.158230] vboxdrv: Unknown symbol wake_up_process (err -22)
[61718.158275] vboxdrv: disagrees about version of symbol preempt_notifier_register
[61718.158277] vboxdrv: Unknown symbol preempt_notifier_register (err -22)
[61718.158312] vboxdrv: disagrees about version of symbol preempt_notifier_unregister
[61718.158313] vboxdrv: Unknown symbol preempt_notifier_unregister (err -22)

any suggestions? any input would be appreciated. is it possible there is a conflict with what is in my /usr/src? I have a bit in there from older kernel builds.

thanks for reading this long-winded post.

[chmod]

Firstly you shouldn't use distros such as kali/backtrack as your main OS they are for pentesting so have security issues and can be quite unstable (as you have found out the hard way) I would suggest using a more stable distribution instead

On to your problem, from the information you have provided it looks as though virtualbox is not compatible with your current kernel, hence why you are having issues after a dist upgrade. To fix this you will need to roll back the kernel to the previous version using

Code:

aptitude install linux-headers=<version-number>

where <version-number> is the previous kernel version you where using (I imagine it would have been 3.11.10, but you will need to verify this as I'm not familiar with kali's development)

[!M03!]

Firstly you shouldn't use distros such as kali/backtrack as your main OS they are for pentesting so have security issues and can be quite unstable (as you have found out the hard way) I would suggest using a more stable distribution instead

On to your problem, from the information you have provided it looks as though virtualbox is not compatible with your current kernel, hence why you are having issues after a dist upgrade. To fix this you will need to roll back the kernel to the previous version using

Code:

aptitude install linux-headers=<version-number>

where <version-number> is the previous kernel version you where using (I imagine it would have been 3.11.10, but you will need to verify this as I'm not familiar with kali's development)

Thanks, for the quick reply. I'll give it a shot.
Yeah, I never wanted kali as my main OS. Had a dual boot setup, ended up using it so much that it's going to be so tedious to switch over at this point. Been thinking about scrapping it for a while now, this issue might push me to do it. I will let you know the outcome when trying to roll back the kernel.

Thanks again

---

Thanks for leading me in the right direction. I still had the kernel installed so I just had to mess with grub a bit to be able to boot to it (I removed the old kernel from the grub config after update)

After updating grub and booting to my old kernel I just ran
/etc/init.d/vboxdrv setup

Everything back to normal now, for the time being. Thanks so much

Will definately be changing distros ASAP