Discuss the 5.0.12 release

[Armando]

So the fix is to make a registry backup before upgrading VBox? How does that prevent the broken NIC?

That is not a "fix" for the broken NIC, as it does not "repair" the broken NIC nor prevent the NIC from breaking.
It could have prevented ME, in that particular occasion, from having to re-install the whole system.

Obviously a whole system backup would be the best precaution, but a registry backup is quite faster to perform and can allow you to "get back" from a (just done) sad upgrade in a reasonably easy way.

[frank]

i can't start guests on debian sid 64-bit with 4.3.3-2 kernel, i get the error:

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 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. 

but /sbin/rcvboxdrv is symlinked to a file that doesn''t exist, /etc/init.d/vboxdrv doesn't exist anymore, systemd problems perhaps?

edit: seems to work now, i just ran ./vboxdrv.sh from /usr/lib/virtualbox/

Correct, the symlink from /usr/lib/virtualbox/vboxdrv.sh to /sbin/rcvboxdrv is missing in the 5.0.12 Linux packages. Typo in the installer script, will be fixed in the next 5.0.x maintenance release.