[SOLVED] VirtualBox & The New 2.6.37.3 Kernel. (Solution: DKMS Required To Install VB Kernel Module)

cwizardone · 03-09-2011, 11:18 PM

Installed all the upgrades along with the new kernel and everything went well until I tried to install (re-install) VirtualBox. It goes through the motions and says it was installed successfully, but upon re-booting there was an error message about the VirtualBox module not loading.
That was with version 3.2.10-66896, so I went over to Sun and downloaded 4.04-7011, but the results where the same.
Is this a kernel problem or a VB problem?
Thanks.

slackass · 03-09-2011, 11:46 PM

I just did the upgrade and reinstalled VB 402 and mine worked.
Let me download 404 and see if it borks it.

slackass · 03-10-2011, 12:06 AM

VirtualBox 404 works here.

cwizardone · 03-10-2011, 12:17 AM

Thanks for your reply.
I get the following message on boot up:

Quote:

Starting VirtualBox modules.... failed! (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

I looked in dmesg, but there was nothing in it in reference to VB or vboxdrv.

BroX · 03-10-2011, 04:12 AM

No problems here either.
Virtualbox 4.0.4-70112 on Slackware64-current (13.37) and custom kernel 2.6.37.3.

Have a look at /var/log/vbox-install.log

dolphin77 · 03-10-2011, 04:28 AM

Quote:

Originally Posted by cwizardone

Thanks for your reply.
I get the following message on boot up:

I looked in dmesg, but there was nothing in it in reference to VB or vboxdrv.

you need to build vbox modules for the new kernel. Run as root
/etc/rc.d/rc.vboxdrv setup

Or something similar. Do not remember exactly if it is called rc.vboxdrv or something similar. Do not use is for quite a long already.

lonestar_italy · 03-10-2011, 06:15 AM

I have a different issue related to Virtualbox on 13.37

Everything is installed correctly, including the kernel driver.

Whenever I turn on the Windows XP guest, the machine boots and suddenly the window closes and the VM is interrupted, when services begin to startup.

If I start the machine in Safe mode, it stays up.

I have the same issue also on another current where I'm still using a 2.6.35.10 kernel, so I suppose it's not the kernel, but probably something in the new glibc-2.13-2 packages that gives some sort of incompatibility with Virtualbox (4.0.4).
Any confirmation?

My next test could be reverting to glibc-2.13-1 packages.

hughszg · 03-10-2011, 07:22 AM

I have got exactly the same issue here.

Quote:

Originally Posted by lonestar_italy

I have a different issue related to Virtualbox on 13.37

Everything is installed correctly, including the kernel driver.

Whenever I turn on the Windows XP guest, the machine boots and suddenly the window closes and the VM is interrupted, when services begin to startup.

If I start the machine in Safe mode, it stays up.

I have the same issue also on another current where I'm still using a 2.6.35.10 kernel, so I suppose it's not the kernel, but probably something in the new glibc-2.13-2 packages that gives some sort of incompatibility with Virtualbox (4.0.4).
Any confirmation?

My next test could be reverting to glibc-2.13-1 packages.

zhoun · 03-10-2011, 07:27 AM

login as root,
cd /usr/src/linux; make prepare; /etc/rc.d/rc.vboxdrv setup

Quote:

Originally Posted by cwizardone

Thanks for your reply.
I get the following message on boot up:

I looked in dmesg, but there was nothing in it in reference to VB or vboxdrv.

cwizardone · 03-10-2011, 09:39 AM

Quote:

Originally Posted by zhoun

login as root,
cd /usr/src/linux; make prepare; /etc/rc.d/rc.vboxdrv setup

Thanks for your reply.
I tried it and here are the results:

Quote:

bash-4.1# cd /usr/src/linux; make prepare; /etc/rc.d/rc.vboxdrv setup
CHK include/linux/version.h
CHK include/generated/utsrelease.h
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
CALL scripts/checksyscalls.sh
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMS ...failed!
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
bash-4.1#

artificiosus · 03-10-2011, 03:47 PM

I had the same issue as well. (VirtualBox 4.04(binary version), 32bit current)

In the VirtualBox settings, try disabling the shared clipboard. This seems to be causing the WinXP guest to abort but I don't know why.

Quote:

Originally Posted by lonestar_italy

I have a different issue related to Virtualbox on 13.37

Everything is installed correctly, including the kernel driver.

Whenever I turn on the Windows XP guest, the machine boots and suddenly the window closes and the VM is interrupted, when services begin to startup.

If I start the machine in Safe mode, it stays up.

I have the same issue also on another current where I'm still using a 2.6.35.10 kernel, so I suppose it's not the kernel, but probably something in the new glibc-2.13-2 packages that gives some sort of incompatibility with Virtualbox (4.0.4).
Any confirmation?

My next test could be reverting to glibc-2.13-1 packages.

lonestar_italy · 03-10-2011, 04:08 PM

Quote:

Originally Posted by artificiosus

I had the same issue as well. (VirtualBox 4.04(binary version), 32bit current)

In the VirtualBox settings, try disabling the shared clipboard. This seems to be causing the WinXP guest to abort but I don't know why.

LOL! It's unbelievable! I've just found this same solution right in this moment, and I've got on here to post this info in the thread! lol

Disabling shared clipboard makes the VM stay up and working. It would be nice to find out what kind of services or file permissions or whatever are involved in this feature and how they have changed with 13.37....

BroX · 03-10-2011, 04:15 PM

Quote:

Originally Posted by cwizardone

Thanks for your reply.
I tried it and here are the results:

Very strange indeed. Are you sure you are running the 4.0.4 version?

Code:

$ vboxmanage --version
4.0.4r70112

cwizardone · 03-10-2011, 11:12 PM

Quote:

Originally Posted by BroX

Very strange indeed. Are you sure you are running the 4.0.4 version?

Code:

$ vboxmanage --version
4.0.4r70112

Yes.

chrisretusn · 03-10-2011, 11:16 PM

I updated Slacware64-current to Slackware64 13.37RC1 this morning.

After the slackpkg stuff I said no to lilo. Switched my kernels back to generic, ran mkinitrd again, then lilo, then rebooted. Then I reinstalled VirtualBox 4.0.4r70112.

All is working well.