Virtualbox fails to start

English Virtualization
1

After a fairly recent update to TW all of my vbox instances crash on
startup. Starting them from a command line session dies immediately with
this error message:

Code
/usr/lib/virtualbox/VirtualBox --comment “LEAP” --startvm “ee8e7da2-
c6b4-4084-93ca-c0dee7711b10”
VirtualBox: Error -1908 in suplibOsInit!
VirtualBox: Kernel driver not installed

VirtualBox: Tip! Make sure the kernel module is loaded. It may also help
to reinstall VirtualBox.
will@will-HP-laptop:~> malloc_consolidate(): invalid chunk size
KCrash: Application ‘VirtualBox’ crashing…

/code

Forced re-install does not help - same result. Any suggestions about how
to get this mess back up and running would be welcome.

2

Pls post the exact zypper command you used to re-install or the package name you force -re-installed if you used YaST.

TSU

3

On Sun, 27 Jan 2019 16:16:04 +0000, tsu2 wrote:

> Pls post the exact zypper command you used to re-install or the package
> name you force -re-installed if you used YaST.
>
> TSU

I blindly forced Yast to update of every thing already installed related
to Virtualbox:

virtualbox
virtualbox-host-kmp-default
virtualbox-host-source
virtualbox-qt

Same crash/messages.

journalctl had 2 obviously relevant messages from a reboot:

code

Jan 26 14:27:48 will-HP-laptop vboxdrv.sh[1140]: vboxdrv.sh: failed:
modprobe vboxdrv failed. Please use ‘dmesg’ to find out why.
Jan 26 14:27:48 will-HP-laptop vboxdrv.sh[1235]: failed: modprobe vboxdrv
failed. Please use ‘dmesg’ to find out why.

/code

I could find nothing in the dmesg output related to vbox but a subsequent
attempt to open the session from the command line as root produced a
popup message suggesting running vboxconfig as root.

Bingo! Apparently, reloading the package(s) did not trigger that step.

Thanks for your time.

4

Glad to hear you were able to fix your problem.

FYI - When creating the CODE tags manually, they should be enclosed in square brackets, eg


Otherwise, if the "hash" button isn't displayed which creates the CODE tags, you can click on the "Advanced" to get the full text editor which will include the button.

TSU
5

It’s never a good idea to “blindly” force YaST to update VirtualBox or, indeed, anything else …

  • It is a good idea, to be very particular about defining which Repository YaST shall use for the update, forced re-install or, whatever …