Kernel driver not installed (rc=-1908)

[Peter83]

Hi,
After updating to kernel 5.10.6-200.fc33.x86_64 x86_64 on Fedora 33 I get the following error,

Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing
'/sbin/vboxconfig'
as root.
If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

After running

Code: Select all

/sbin/vboxconfig

I get the following message:

Code: Select all

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.

I'm not using EFI Secure Boot. I enclose the log file for your reference. I'm just not sure that re-installing would fix this issue but having said that I haven't tried it.

Best regards,

EDIT:
Downgrading to 5.9.16-200.fc33.x86_64 seems to fix the issue.

[scottgus1]

I wonder if updating the Linux Kernel drivers are needed too? https://www.virtualbox.org/manual/ch02. ... nux-prereq

[Martin]

Something changed from kernel 5.9 to 5.10 which broke VirtualBox 6.1.16.
(also the same on Fedora 32)

[i386x]

Debian GNU/Linux bullseye/sid
Linux debian 5.10.0-1-amd64 #1 SMP Debian 5.10.4-1 (2020-12-31) x86_64 GNU/Linux

same problem.

[efftee]

Same issue on 3 machines running
Linux a 5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Linux b 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Linux c 5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Terrifying... nothing works anymore, 6 really important vms that can't be started anymore since yesterday !
Halp !

However VB is working on mac. Would this seem to be more likely linked to a linux upgrade more than an issue with VB ?

Messages :
WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.

You will not be able to start VMs until this problem is fixed.


Or :

WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (5.8.0-38-generic) or it failed to
load. Please recompile the kernel module and install it by

sudo /sbin/vboxconfig

You will not be able to start VMs until this problem is fixed.
/usr/lib/virtualbox/VirtualBox: error while loading shared libraries: libQt5PrintSupport.so.5: cannot open shared object file: No such file or directory

[efftee]

EDIT:
Downgrading to 5.9.16-200.fc33.x86_64 seems to fix the issue.

Hi Peter, how did you proceed exactly for the downgrade ?

[efftee]

For what it's worth... Might help someone...

Corrected the problem by doing :

Uninstall Virtualbox
Download pkg from http://download.virtualbox.org/virtualbox/6.1.16/
sudo dpkg -i virtualbox-6.1_6.1.16-140961~Ubuntu~eoan_amd64.deb
sudo apt-get update
sudo apt-get ugprade
sudo apt-get dist-upgrade
got error message about unmet dependencies
sudo apt --fix-broken install
sudo apt autoremove

All was back in working order... Sorry, I don't exactly know why, proceed with caution.

[Martin]

It would be helpful if you could provide package names which were mentioned by the last three steps "error message about unmet dependencies, sudo apt --fix-broken install, sudo apt autoremove".
That way others could compare what was missing or in conflict.

[efftee]

It would be helpful if you could provide package names which were mentioned by the last three steps "error message about unmet dependencies, sudo apt --fix-broken install, sudo apt autoremove".
That way others could compare what was missing or in conflict.

Hi Martin, you are correct. Sorry, I have lost them in the terminal unfortunately...
Not sure in which logs to look for them.

I remember however they were related to the Qt components in regards to VirtualBox UI.

EDIT :
Ok found the components mentionned in the history log

Code: Select all

Commandline: apt --fix-broken install
Install: libqt5printsupport5:amd64 (5.12.8+dfsg-0ubuntu1, automatic), libqt5x11extras5:amd64 (5.12.8-0ubuntu1, automatic), python-is-python2:amd64 (2.7.17-4, automatic)

Commandline: apt autoremove
Remove: libvncserver1:amd64 (0.9.12+dfsg-9ubuntu0.3), libgsoap-2.8.91:amd64 (2.8.91-2)

[Peter83]

Hi,
Sorry I just saw your message. Fedora 33 keeps the 3 most recent kernels I believe so I just ran

Code: Select all

sudo grubby --set-default /boot/vmlinuz-5.9.16-200.fc33.x86_64

I'll keep this kernel for a while while updating with -x kernel* until a feasible solution for Fedora comes up.

Cheers,
Peter

EDIT:
Downgrading to 5.9.16-200.fc33.x86_64 seems to fix the issue.

Hi Peter, how did you proceed exactly for the downgrade ?