VirtualBox asks me to run vboxconfig each time
 

Hi, after each restart of my Debian Wheezy, when I want to launch a VM, I have message:

"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. Please reinstall the kernel module by executing

'/sbin/vboxconfig'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT."

Do you know why I need to do it each time, or otherwise where I should look for to find the explanations and thus making this driver installed automatically at each boot.

As it's telling you, the driver for Virtualbox is not installed and therefore you will not be able to start any VM's. Open a terminal window as superuser/root and run the command it's telling you to.

If this still does not work, try reinstalling Virtualbox.

Yes, that's what I do but I'd like to not be forced to do it everyday

Let's start with some basic info like;

How did you install Virtualbox (and where from, official repo's, etc)?

As I have Virtualbox installed myself and have not had any issues, that you are talking about. I have installed it from official repo's for my distro (PCLinuxOS).

The package from Debian Wheezy amd64 on
https://www.virtualbox.org/wiki/Linux_Downloads

Is there a package for Virtualbox in the official repo's for Debian Wheezy? If so, you should install it from there instead (uninstall your current Virtualbox installation first).

If you are still having the same problem, then you may need to check file permissions (as the output you posted, originally said). As that's the only other possibly I can think of, as to why you are getting that error message.

The correct file permissions are as follows;

Focussing on another part of the error message, what are you permissions for /dev/vboxdrv?:

ls -la /dev/vbox* should also provide info on vboxdrvu and vboxnetctl.

Probleme with VirtualBox
 

That's what I've done in the first place, but with this old one I couldn't use the window$ installer provided by my work.

They are like this

Did you run the command hydrurga has mentioned?

Here's my output for it;

Please post your output, thanks.

crw------- 1 root root 10, 58 févr. 23 14:35 /dev/vboxdrv
crw-rw-rwT 1 root root 10, 57 févr. 23 14:35 /dev/vboxdrvu
crw------- 1 root root 10, 56 févr. 23 14:35 /dev/vboxnetctl

/dev/vboxusb:
total 0
drwxr-x--- 4 root vboxusers 80 févr. 23 14:44 .
drwxr-xr-x 14 root root 3300 févr. 23 14:44 ..
drwxr-x--- 2 root vboxusers 80 févr. 23 08:41 001
drwxr-x--- 2 root vboxusers 60 févr. 23 14:44 002

Hmmm, what's with that sticky bit (I don't know if it's relevant or not)?

Yeah, that's the only difference, I can see as well, might be a clue ;)

Hi helpers, I'd like to understand something to debug the thing: where on your systeme do you have one or several vboxdrv.sh file(s)?

One place, here;
Are you still having any problems??

No changes, and I can't see how the sticky bit could be linked to it.