[Solved] VirtualBox VMs crash after update

[fmolina2b]

Hi,
Have just run the update after blue icon appearance, essentially upgrading vbox from 5.2.6 to 5.2.8, apparently removing the old version; vbox was not running, have just powered up the machine. After that, all VMS refuse to start with the message:

Failed to open/create the internal network 'HostInterfaceNetworking-wlp3s0' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).

One of the kernel modules was not successfully loaded. Make sure that no kernel modules from an older version of VirtualBox exist. Then try to recompile and reload the kernel modules by executing '/sbin/vboxconfig' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Result Code: NS_ERROR_FAILURE (0x80004005)
Componente: ConsoleWrap
Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

/sbin/vboxconfig has 0 bytes

uname -a:

Linux Octopus 4.14.20-desktop-1.mga6 #1 SMP Sun Feb 18 01:22:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Please help. Should I reboot?

[fmolina2b]

Update: rebooting solves the problem. But it shouldn't be needed, I think; or advised otherwise.

[benmc]

Hi

when the virtualbox modules are loaded, to be loaded, the originals need to be unloaded first. (English, don't you just love it)
dkms would normally unload and remove the old virtualbox modules and kernel and build new modules against the new kernel.
for the completion of the update, the kernel needs to be booted for the modules to be completely installed/registered (for want of a better description).

this is also true for nvidia graphics and broadcom wifi (and likely others)