Error In suplibOsInit - wrong command "/sbin/rcvboxdrv setup" proposed in dialog -> fixed in 5.0 and later releases after Oct 20 2015

[doktor5k]

When starting a saved VM after update to VirtualBox-5.0-5.0.6_103037_el6-1.x86_64 it shows the following dialog because vboxdrv and related kernel modules have not been re-built yet for the current kernel after virtualbox update:

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 the kernel module by executing

'/sbin/rcvboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the > vboxdrv kernel module if necessary.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. "

The proposed command {{{ /sbin/rcvboxdrv setup }}}

does not exist. The actual command that should be proposed is

/usr/lib/virtualbox/vboxdrv.sh setup

Please adjust the string in the dialogue.

FWIW, not sure why the %post scripts of the rpm did not run this, logic can be see n via

rpm -q --scripts --triggers VirtualBox-5.0|grep vboxdrv.sh

and should have fixed this, but the dialog should still show the correct command.

[Michael Thayer]

Can you try one of the current test builds?<1>

<1> https://www.virtualbox.org/wiki/Testbuilds

[doktor5k]

Yep, tested with https://www.virtualbox.org/download/testcase/VirtualBox-5.0-5.0.7_103385_el6-1.x86_64.rpm

Installed cleanly, and also kernel modules were rebuild.

Before:

[14:01:44]─[~] sudo modinfo vboxdrv
filename:       /lib/modules/2.6.32-573.3.1.el6.x86_64/extra/vboxdrv.ko
version:        5.0.6 (0x00240000)
license:        GPL
description:    Oracle VM VirtualBox Support Driver
author:         Oracle Corporation
srcversion:     5DF3A6D8D0ADB66F4CA7A49
depends:        
vermagic:       2.6.32-573.3.1.el6.x86_64 SMP mod_unload modversions 
parm:           force_async_tsc:force the asynchronous TSC mode (int)

After:

[14:13:49]─[~] sudo modinfo vboxdrv
filename:       /lib/modules/2.6.32-573.3.1.el6.x86_64/extra/vboxdrv.ko
version:        5.0.7 (0x00240000)
license:        GPL
description:    Oracle VM VirtualBox Support Driver
author:         Oracle Corporation
srcversion:     5DF3A6D8D0ADB66F4CA7A49
depends:        
vermagic:       2.6.32-573.3.1.el6.x86_64 SMP mod_unload modversions 
parm:           force_async_tsc:force the asynchronous TSC mode (int)

[Michael Thayer]

Thank you, if I correctly understood it is working now.

[doktor5k]

Yes, the issue reported initially seems fixed now.

Although on a colleague's box we found a related issue. After the update from 5.0.6_103037_el6-1 to the testcase version 5.0.7_103385_el6-1 mentioned previously, the %post sripts in the package successfully built the kernel modules. After he shut down his running VM, and trying to start it he received the same error that I posted:

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 the kernel module by executing

'/sbin/rcvboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

In another window in the background there was this:

Failed to open a session for the virtual machine Win7.

The virtual machine 'Win7' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

The problem was simply that the vboxdrv module for the currently running kernel was not loaded. After we loaded it via

modprobe vboxdrv

then the VM started fine.

During the rpm update we saw the following:

Dependencies Resolved

=======================================================================================================================
 Package               Arch          Version                    Repository                                        Size
=======================================================================================================================
Updating:
 VirtualBox-5.0        x86_64        5.0.7_103385_el6-1         /VirtualBox-5.0-5.0.7_103385_el6-1.x86_64        166 M

Transaction Summary
=======================================================================================================================
Upgrade       1 Package(s)

Total size: 166 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
A copy of VirtualBox is currently running.  Please close it and try again.
Please note that it can take up to ten seconds for VirtualBox (in particular
the VBoxSVC daemon) to finish running.
error: %pre(VirtualBox-5.0-5.0.7_103385_el6-1.x86_64) scriptlet failed, exit status 1
Error in PREIN scriptlet in rpm package VirtualBox-5.0-5.0.7_103385_el6-1.x86_64
error:   install: %pre scriptlet failed (2), skipping VirtualBox-5.0-5.0.7_103385_el6-1
  Verifying  : VirtualBox-5.0-5.0.7_103385_el6-1.x86_64                                                            1/2 
VirtualBox-5.0-5.0.6_103037_el6-1.x86_64 was supposed to be removed but is not!
  Verifying  : VirtualBox-5.0-5.0.6_103037_el6-1.x86_64                                                            2/2 

Failed:
  VirtualBox-5.0.x86_64 0:5.0.6_103037_el6-1                 VirtualBox-5.0.x86_64 0:5.0.7_103385_el6-1

Is is expected, that all VMs need to be shutdown before virtualbox can be updated? Is that something new with 5.x or has that always been the case? I mean, the new kernel modules were built correctly, and could be loaded without issues, so not sure what the problem during the rpm update was about.

[Michael Thayer]

That is expected, and as far as I know was always the case. It is to prevent problems if the files needed by a running copy of VirtualBox are changed under it (so to speak), not to mention the fact that the old kernel modules cannot be unloaded while VirtualBox is running.

Could you please make sure that after a reboot the kernel modules are loaded? You might possibly want to upgrade to 5.0.8 too. If they are not loaded, you may be seeing the issue from ticket #14723 and want to add a comment to that.