busted virtualboxes

[mmikeinsantarosa]

Ever since I upgraded to the liquorix kernel, none of my virtualbox devices will run. The app launches but every device fails to start.

The app launches but the machine quits with a message similar to.

Code: Select all

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 virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. [code]System:    Host: mx17mainlt Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
Distro: MX-18.1_x64 Continuum March 14  2018 

The first thing I did was to boot back on the stock kernel and remove the liquorix kernel.
Then on the stock kernel, I tried virtualbox and got the same error.
I ran

Code: Select all

sudo dpkg-reconfigure virtualbox-dkms

It's good up until the end then...

Code: Select all

DKMS: install completed.
[ ok ] Unloading VirtualBox kernel modules....
[....] Loading VirtualBox kernel modules...[....] modprobe vboxdrv failed. Please use 'dmesg' to fin[FAIL why ... failed!
 failed!
invoke-rc.d: initscript virtualbox, action "restart" failed.

I removed virtualbox and reinstalled, got the same error, tried the dpkg-reconfigure command again and got the same results.

This was on my MX18.1 laptop. When I checked my desktop, it has the same problem.

I removed the virtualbox from test - 6.0.4-dfsg-1~mx17+1 and installed the one from main, went through the same gyrations with the same results. I'm sure I must have missed something simple but...

Any ideas would be much appreciated?

[dolphin_oracle]

Are the headers for the kernel installed?

[richb]

Had a similar problem with a different kernel . virtualbox-dkms was not installed. It was corrected by installing it.

[mmikeinsantarosa]

My mobile broadband has gotten flakey on the stock kernel so I just upgraded to the backported debiam 4.19.16 kernel and now the

Code: Select all

sudo dpkg-reconfigure virtualbox-dkms

is successful and launching a device produces a new error

Code: Select all

Implementation of the USB 2.0 controller not found!
Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings.
Note! This error could also mean that an incompatible version of the 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND).
Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I have virtualbox-6.0.4-dfsg installed now.
I don't see an extension in settings other than VNC

[dolphin_oracle]

we can't host the entensions, so you'll need to download those direct from oracle. although I though stevo had built an extensions pack for mx that does the downloading for you.

[mmikeinsantarosa]

Are the headers for the kernel installed?

Si

[Stevo]

Virtualbox-ext-pack gets them for you when you install it.

For what it's worth, everything works for me with

Code: Select all

Linux mx 4.20.0-15.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.20-13~mx17+1 (2019-03-11) x86_64 
GNU/Linux

and virtualbox-5.2.24 packages on the host. I think I had to boost the Vbox guest packages in the MX 17/18 guests to 6.0.4 to get shared folders working, but the MX 16 VMs have shared folders working with their virtualbox-guest-dkms 5.1.22, so now this seems more like voodoo.

[mmikeinsantarosa]

I try to keep both systems identical so whatever was done to one, the other was just as easily stepped on. It's just funny it had to happen rt when i really neede a vm.

[toto]

I have the same issue as I get this error message

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing

'/sbin/vboxconfig'

as root.

The headers for the kernel are installed and I did install virtualbox-dkms.

I installed VB 6.1 from the terminal but I get the same error when I install VB from MX Package Installer.

Any help would be greatly appreciated.

Thank you.

[timkb4cq]

I had this happen when migrating a VM from MX-15 -> MX-19 (two different partitions on same box, sharing a data partition where the VMs reside).
I had to open the VM on the old system and shut it down instead of Saving State. Then I could get it boot on the newer system.