conf file, put in the names of the vbox kernel modules you want to add, such as: vboxdrv and optionally vboxnetadp, vboxnetflt and vboxpci.

d directory your modprobe uses) and making a. Then you can activate the vboxdrv module permanently by going to /etc/modules-load.d/ (or whatever. If you Virtual Machine runs after that without giving you an error message, you've found the solution. If your error message is telling you that your missing another module, be sure to activate it as well. To load a module manually (such as vboxdrv), open a terminal prompt and put in: sudo modprobe vboxdrv If your vBox GUI starts without a hitch but get an error telling you to install the VBoxDrv kernel module (or any other modules) when you try to run a virtual machine, your problems are not related to installing the modules into your kernel but activating them in modprobe which the module installation script fails to do. I had dkms and all the modules already installed and compiled into my kernel, yet I still got a module related error message when I tried to run a vBox virtual machine.

Had this problem with vBox across 2 distros (Ubuntu and Arch).

Virtualbox kernel driver not installed