When starting a VirtualBox VM, I get:
Running sudo /sbin/vboxconfig does not fix the problem.
How to fix that?
VirtualBox 5.0.10 r104061
asked Dec 4, 2015 at 3:53
-
For me the fix was installing the latest version of virtualbox. (Received error on 6.1.12. Upgraded to 6.1.34). sudo dpkg -i <downloaded file.deb>– S2LMay 1 at 14:18
Add a comment
|
6 Answers
same problem with me, abort it if you not use vagrant.
the output when i run vagrant up:
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:
VirtualBox is complaining that the kernel module is not loaded. Please
run `VBoxManage --version` or open the VirtualBox GUI to see the error
message which should contain instructions on how to fix this error.
output VBoxManage --version:
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (3.19.0-47-generic) or it failed to
load. Please recompile the kernel module and install it by
sudo /sbin/rcvboxdrv setup
You will not be able to start VMs until this problem is fixed.
5.0.14r105127
output sudo /sbin/rcvboxdrv setup:
Bad argument setup
My problem solved after run this command sudo /usr/lib/virtualbox/vboxdrv.sh setup
$ sudo /usr/lib/virtualbox/vboxdrv.sh setup
Stopping VirtualBox kernel modules ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...done.
$ VBoxManage --version
5.0.14r105127
You can always use modprobe to add a kernel module. I solved the same problem on my server by doing:
[root@mageia5][/home/afk]# modprobe -a vboxdrv
-
In this case, it's mostly not a problem that the module hasn't been loaded. This error appears when you've installed another kernel (mostly as a package update) which doesn't contain the vboxdrv module yet. So you have to compile and install the module to that new kernel, with
sudo /sbin/rcvboxdrv setup. AFAIR nowadays this command is mentioned in the error message, instead ofsudo /sbin/vboxconfig. Dec 12, 2016 at 10:36
I found the following virtualbox dkms related packages:
- virtualbox-dkms
- virtualbox-guest-dkms
Did you install these packages?
-
-
This worked for me. After that I just did
vagrant upto have it running. Jun 11, 2019 at 11:45
WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (4.7.1-1-ARCH) or it failed to load. Please recompile the kernel module and install it by sudo
/sbin/vboxconfig
You will not be able to start VMs until this problem is fixed.
The fix for this for me was to install the linux-headers package
This seems to be a known bug.
Running the following commands fixes the problem:
sudo /sbin/vboxconfig
sudo /sbin/rcvboxdrv setup
Unfortunately, you will have to run these commands after each reboot.
answered Dec 4, 2015 at 3:53
-
You shouldn't have to run those commands after each reboot, only for each newly installed kernel (probably from a package update) that doesn't include the vboxdrv module yet.
rcvboxdrv setupcompiles the module and sets it up with the currently running kernel. Dec 12, 2016 at 10:38 -
I agree, we shouldn't have to run /sbin/vboxconfig after each reboot, but when I upgraded my system from 18.04 to 20.04 that is exactly the situation I find myself in now - with Virtualbox 6.1.– MangoCatAug 5, 2021 at 21:19
Had the same Problem. Was searching for the solution for days. In the end it was EFI blocking some functionality. My solve was to
- restart machine
- enter bios
- disable "secure boot" under "security" (your specific name of the config could vary depending on the machine and bios used, but should be similar)
Hope this could help some nomads seeking days for answers like myself.
