Using /sbin/vboxconfig in 5.0.8

[stephanecharette]

In the 5.0.8 release notes, it mentions the /etc/init.d/vboxdrv init command has been renamed to /sbin/vboxconfig. This would also seem to be supported by this message when I try to start any of my VMs:

screenshot.png (68.72 KiB) Viewed 40102 times

However, I cannot figure out how to get the VirtualBox driver updated. Where I'd previously run the vboxdrv init command, the vboxconfig command doesn't seem to do anything for me:

Code: Select all

> sudo /sbin/vboxconfig
> sudo /sbin/vboxconfig init
Bad argument init
> sudo /sbin/vboxconfig help
Bad argument help
> sudo /sbin/vboxconfig --help
Bad argument --help
> sudo /sbin/vboxconfig init
Bad argument init
> sudo /sbin/vboxconfig --init
Bad argument --init

For the record, I do have dkms installed.

screenshot2.png (26.27 KiB) Viewed 40102 times

[Buford T. Justice]

I am having the EXACT same problem on Ubuntu MATE 14.04.2 LTS

[stephanecharette]

I created a bug for this: https://www.virtualbox.org/ticket/14723

This is a showstopper for me, since none of my VMs can start in VB 5.0.8.

[loukingjr]

FWIW, i had no trouble upgrading to VB 5.0.8 on an Ubuntu 15.04 host and a Linux Mint 17.2 host and all my guests launch from the GUI or created shortcuts.

[stephanecharette]

I am having the EXACT same problem on Ubuntu MATE 14.04.2 LTS :(

Running this command manually fixed the issue for me:

Code: Select all

sudo /sbin/rcvboxdrv setup

[Buford T. Justice]

I am having the EXACT same problem on Ubuntu MATE 14.04.2 LTS

Running this command manually fixed the issue for me:

Code: Select all

sudo /sbin/rcvboxdrv setup

And that fixed it for me. Thank you!

Code: Select all

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 ...done.

[hellomynameisjeff]

I have the same issue:

Ubuntu 15.04

Code: Select all

$ uname -a
Linux 3.19.0-28-generic #30-Ubuntu SMP Mon Aug 31 15:52:51 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

I did:

Code: Select all

for i in vboxhost vboxdrv vboxnetflt vboxnetadp; do

sudo rm -rf "/var/lib/dkms/${i}"*

done

Then:

Code: Select all

$ sudo rcvboxdrv setup
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Removing old VirtualBox kernel module ...done.
Trying to register the VirtualBox kernel modules using DKMSERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-5.0.0.crash'
Error! Bad return status for module build on kernel: 3.19.0-28-generic (x86_64)
Consult /var/lib/dkms/vboxhost/5.0.8/build/make.log 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)

In /var/log/vbox-install.log:

Code: Select all

$ tail /var/log/vbox-install.log 
include/net/netns/mib.h:4:22: fatal error: net/snmp.h: No such file or directory
 #include <net/snmp.h>
                      ^
compilation terminated.
scripts/Makefile.build:257: recipe for target '/tmp/vbox.0/linux/VBoxNetFlt-linux.o' failed
make[2]: *** [/tmp/vbox.0/linux/VBoxNetFlt-linux.o] Error 1
Makefile:1395: recipe for target '_module_/tmp/vbox.0' failed
make[1]: *** [_module_/tmp/vbox.0] Error 2
Makefile:205: recipe for target 'vboxnetflt' failed
make: *** [vboxnetflt] Error 2

Can anyone help?

[stephanecharette]

I have the same issue:

Code: Select all

$ tail /var/log/vbox-install.log 
include/net/netns/mib.h:4:22: fatal error: net/snmp.h: No such file or directory
 #include <net/snmp.h>
                      ^
compilation terminated.

Can anyone help?

Shot in the dark here, but have you done this: https://www.virtualbox.org/manual/ch02. ... nelmodules

I don't know if SNMP is a new/old dependency. Personally, my host is also where I do some software development, so I already had SNMP installed.

If you're looking for the Ubuntu package with those headers: sudo apt-get install libsnmp-dev

[Filippo Cas]

I am having the EXACT same problem on Ubuntu MATE 14.04.2 LTS

Running this command manually fixed the issue for me:

Code: Select all

sudo /sbin/rcvboxdrv setup

Ok. The solution of Stephane works on Kubuntu 14.04 LTS too.

[mdalacu]

"Kernel driver not installed" - after VirtualBox upgrade.
I have the same problem using Virtualbox 5.0.14. I cannot start VMs on Ubuntu 15.10 x64. (sudo /sbin/rcvboxdrv setup - Bad argument setup)


The workaround is this:

Code: Select all

sudo /usr/lib/virtualbox/vboxdrv.sh setup

[mce128]

Thanks! I also had the same issue as you where the /sbin/rcvboxdrv was complaining of "Bad argument setup". I looked in the script and not only was it missing the shebang line (amazing that it ran at all given that) but it only has one possible argument as acceptable in the case statement which is '--nostart' and that argument sets a bash variable called $START to be an empty string and then later when it is tested with a -n only if it is populated does it do anything, but there is no way for the logic to ever have the initially set value of 'true' as either it is cleared by running with the argument '--nostart' or it exits and complains about the 'bad argument <any arg here>'.

The workaround you gave worked beautifully! Well, after I signed the kernel module that it built anyway, but that is a whole different ball 'o wax.

"Kernel driver not installed" - after VirtualBox upgrade.
I have the same problem using Virtualbox 5.0.14. I cannot start VMs on Ubuntu 15.10 x64. (sudo /sbin/rcvboxdrv setup - Bad argument setup)


The workaround is this:

Code: Select all

sudo /usr/lib/virtualbox/vboxdrv.sh setup

[stephanecharette]

... I looked in the script and not only was it missing the shebang line (amazing that it ran at all given that) but ...

I mentioned that shebang issue a few months ago. Disappointing to see it hasn't been fixed. https://www.virtualbox.org/ticket/14723#comment:1

I'll open up another bug specifically for that issue.

[Roshi]

I hit the same issue today after upgrading to 5.0.14 (I am on Ubuntu 15.10, using the official Virtualbox apt repo)

I fixed it with:

sudo /usr/lib/virtualbox/vboxdrv.sh setup

[jay_m]

I hit the same issue today after upgrading to 5.0.14 (I am on Ubuntu 15.10, using the official Virtualbox apt repo)

I fixed it with:

sudo /usr/lib/virtualbox/vboxdrv.sh setup

Same thing worked for me. Ubuntu 14.04.

[dabo man]

I am running VirtualBox 5.0.14 on openSUSE 13.2. After an openSUSE kernel update earlier today, the command "/sbin/rcvboxdrv setup" returned the error "Bad argument setup."

"sudo /usr/lib/virtualbox/vboxdrv.sh setup" fixed this problem for me.