Mailinglist Archive: opensuse-bugs (4283 mails)

< Previous Next >
[Bug 1037291] VirtualBox fails to start VMs "Kernel driver not installed (rc=-1908)" and then VERR_SUPDRV_COMPONENT_NOT_FOUND
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 03 May 2017 17:08:11 +0000
  • Message-id: <>

Larry Finger <Larry.Finger@xxxxxxxxxxxx> changed:

What |Removed |Added

--- Comment #1 from Larry Finger <Larry.Finger@xxxxxxxxxxxx> ---
You have several problems.

1. Sometime between snapshots 20170407 and 20170414, Tumbleweed stopped
starting VB from the sysv init scripts in /etc/init.d/, even though this code
has worked on every previous version of openSUSE.

2. When you manually modprobed vboxdrv, you failed to get all the routines
needed to operate the network. A better command is
"sudo modprobe -av vboxnetflt vboxnetadp vboxpci"
That will load all the modules. Your network problem is due to the vboxnet*
modules not being loaded.

3. The openSUSE implementation is missing /sbin/vboxconfig as you noted.
Unfortunately, that file would not have helped you.

A version of VB is now building
( that fixes all of the above
problems. To fix #1 and #2, systemd service files have been created, thus the
sysv to systemd conversion routines are not needed. The new routine will load
all the drivers. For #3, /sbin/vboxconfig is created. In addition, that routine
will be called automatically by the systemd service for those cases that the
kernel fails to match the module versions, thus the user should never see the
popup telling them to run the script as it will already have been run.

I have no idea how long it will take until the new code is published. The TW
snapshot method takes longer than the update methods of Leap 42.1 and 42.2. My
request was submitted 4 days ago.

You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >