Maui Forums

Full Version: Can't run virtual box
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi guys,
I have run an update and after that, I am not able to run Virtual Box anymore.
When I try to open a virtual maschine I get this:

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please install virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'


linux-headers it's installed and it's the same kernel version 4.4.0-104

I have tried:
sudo systemctl restart systemd-modules-load.service

and get this:
Job for systemd-modules-load.service failed because the control process exited with error code. See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details.

and this one:
sudo systemctl status systemd-modules-load.service

systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset:
Active: failed (Result: exit-code) since Do 2017-12-21 23:01:21 CET; 1min 17s ago
Docs: manConfusedystemd-modules-load.service(8)
man:modules-load.d(5)
Process: 3017 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 3017 (code=exited, status=1/FAILURE)

Dez 21 23:01:21 Maui-Notebook systemd[1]: Starting Load Kernel Modules...
Dez 21 23:01:21 Maui-Notebook systemd[1]: systemd-modules-load.service: Main process exited,
Dez 21 23:01:21 Maui-Notebook systemd[1]: Failed to start Load Kernel Modules.
Dez 21 23:01:21 Maui-Notebook systemd[1]: systemd-modules-load.service: Unit entered failed
Dez 21 23:01:21 Maui-Notebook systemd[1]: systemd-modules-load.service: Failed with result '
lines 1-13/13 (END)

-- Logs begin at Do 2017-12-21 22:43:01 CET, end at Do 2017-12-21 23:09:22 CET. --
Dez 21 23:01:21 Maui-Notebook systemd-modules-load[3017]: Failed to find module 'ashmem_linux'
Dez 21 23:01:21 Maui-Notebook systemd-modules-load[3017]: Failed to find module 'binder_linux'



then I run:
systemctl status virtualbox.service
and get this:
virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Do 2017-12-21 22:43:36 CET; 29min ago
Docs: manConfusedystemd-sysv-generator(8)
Process: 1463 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Dez 21 22:43:31 Maui-Notebook systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Dez 21 22:43:32 Maui-Notebook virtualbox[1463]: * Loading VirtualBox kernel modules...
Dez 21 22:43:36 Maui-Notebook virtualbox[1463]: * No suitable module for running kernel found
Dez 21 22:43:36 Maui-Notebook virtualbox[1463]: ...fail!
Dez 21 22:43:36 Maui-Notebook systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Dez 21 22:43:36 Maui-Notebook systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Dez 21 22:43:36 Maui-Notebook systemd[1]: virtualbox.service: Unit entered failed state.
Dez 21 22:43:36 Maui-Notebook systemd[1]: virtualbox.service: Failed with result 'exit-code'.


that is what I found in internet, but I am lost. Don't know what to do next.

I hope there are a solution for that,
If I make a new virtual drive and erase the old one, will I have the same problem?

Thanks a lot
Hmm... try reinstalling the virtualbox-dkms package which should rebuild the kernel part necessary for virtualbox.
(22nd December 2017, 10:54)leszek Wrote: [ -> ]Hmm... try reinstalling the virtualbox-dkms package which should rebuild the kernel part necessary for virtualbox.

It works! thank you Leszek
long life Maui Smile