Kernel driver not installed (rc=-1908)

[Peter83]

After update to kernel 5.8.4-200.fc32.x86_64 on Fedora I get the following error (see attachement #1) when trying to load a VM using VirtualBox 6.1.12
Running the following code gives me back the following:

Code: Select all

sudo dnf install akmod-VirtualBox kernel-devel-$(uname -r)
Package akmod-VirtualBox-6.1.12-1.fc32.x86_64 is already installed.
Package kernel-devel-5.8.4-200.fc32.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

Running the akmods outputs the follwing information (See attachement #2)

I have not EFI Secure Boot enabled. Any suggestions are welcome!

Best regards

[zen-fedora]

I updated to 5.8 as well (dnf update) and have exact same symptoms. I can reboot with the last kernel (5.7.17-200) and VirtualBox works just fine. I have looked at a bunch of troubleshooting posts and have not found one that works. I have completely removed VB and reinstalled using the repository rpms (dnf install VirtualBox-server and dnf install VirtualBox) with no luck. I then removed all of VB and tried the rpms on the virtualbox site but still see the same error messages. I have had a lot of kernel updates since moving to F32 but this update to 5.8 is the only one to kill VB. I have checked the usual suspects like dev packages being present. I have included the working 5.7.17 log as well as the 5.8 non-working log.

Any ideas?
Thanks

-------------------------
journalctl -xe:

Aug 31 17:42:52 phoenix /usr/libexec/gdm-x-session[29045]: WARNING: The vboxdrv kernel module is not loaded. Either there is no module
Aug 31 17:42:52 phoenix /usr/libexec/gdm-x-session[29045]: available for the current kernel (5.8.4-200.fc32.x86_64) or it failed to
Aug 31 17:42:52 phoenix /usr/libexec/gdm-x-session[29045]: load. Please try load the kernel module by executing as root
Aug 31 17:42:52 phoenix /usr/libexec/gdm-x-session[29045]: dnf install akmod-VirtualBox kernel-devel-5.8.4-200.fc32.x86_64
Aug 31 17:42:52 phoenix /usr/libexec/gdm-x-session[29045]: akmods --kernels 5.8.4-200.fc32.x86_64 && systemctl restart vboxdrv.service
Aug 31 17:42:52 phoenix /usr/libexec/gdm-x-session[29045]: You will not be able to start VMs until this problem is fixed.
---------------------

[root@phoenix Download]# dnf install akmod-VirtualBox kernel-devel-5.8.4-200.fc32.x86_64
Last metadata expiration check: 1:04:57 ago on Mon 31 Aug 2020 04:40:34 PM PDT.
Package akmod-VirtualBox-6.1.12-1.fc32.x86_64 is already installed.
Package kernel-devel-5.8.4-200.fc32.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

---------------------
[root@phoenix Download]# akmods --kernels 5.8.4-200.fc32.x86_64 && systemctl restart vboxdrv.service
Checking kmods exist for 5.8.4-200.fc32.x86_64 [ OK ]
Building and installing VirtualBox-kmod [FAILED]
Building rpms failed; see /var/cache/akmods/VirtualBox/6.1.12-1-for-5.8.4-200.fc32.x86_64.failed.log for details

Hint: Some kmods were ignored or failed to build or install.
You can try to rebuild and install them by by calling
'/usr/sbin/akmods --force' as root. (this did not work)...

Job for vboxdrv.service failed because the control process exited with error code.
See "systemctl status vboxdrv.service" and "journalctl -xe" for details.
------------------

[root@phoenix Download]# systemctl restart vboxdrv.service
Job for vboxdrv.service failed because the control process exited with error code.
See "systemctl status vboxdrv.service" and "journalctl -xe" for details.
[root@phoenix Download]# systemctl status vboxdrv.service
● vboxdrv.service - Linux kernel module init script
Loaded: loaded (/usr/lib/systemd/system/vboxdrv.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-08-31 17:19:39 PDT; 30s ago
Process: 27887 ExecStart=/sbin/modprobe vboxdrv (code=exited, status=1/FAILURE)
Main PID: 27887 (code=exited, status=1/FAILURE)
CPU: 6ms


-----------------------
Aug 31 17:19:39 phoenix systemd[1]: Starting Linux kernel module init script...
Aug 31 17:19:39 phoenix modprobe[27887]: modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.8.4-200.fc32.x86_64
Aug 31 17:19:39 phoenix systemd[1]: vboxdrv.service: Main process exited, code=exited, status=1/FAILURE
Aug 31 17:19:39 phoenix systemd[1]: vboxdrv.service: Failed with result 'exit-code'.
Aug 31 17:19:39 phoenix systemd[1]: Failed to start Linux kernel module init script.

[kaerock]

This is likely due to mmap locking API changes and a few other API changes in the 5.8.4 kernel.
https://www.virtualbox.org/ticket/19644

TL;DR: We'll likely need to wait for 6.1.13 to be released for a fix (maybe soon?)

[kaerock]

EDIT: Link posted in above post.

[ferb]

I have the same problem with kernel 5.8.4.200 in fedora 32 x86_64, i not have uefi o efi secure activated

[scottgus1]

Try the test builds. One 5.8 user had 6.1.13 work: viewtopic.php?f=7&t=99310

[robatino]

The newly released VB 6.1.14 fixes the problem for me.

[zen-fedora]

Team,

VB 6.1.14 fixes the problem for me as well.

Thanks for the help

[xris]

I'm having this exact problem w version 6.1.16... posted ticket report number 20030

Any idea why this issue should come back with later version, or if I might be doing something different to evoke the issue? Thanks for any suggestions...