Vbox Kernel not installed

[curano]

Hi all,

My Fedora 25 upgraded to Kernel 4.9.12-200.fc25.x86_64 today.
Usually the vbox will be integrated into the new kernel automatically
Today I did get the following error message when I tried to start the virtualbox :

Code: Select all

kernel driver not installed (RC=1908)

I tried sudo /sbin/vboxconfig which terminated with the following error message:

Code: Select all

Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /usr/lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /usr/lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /usr/lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /usr/lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.

I started dmesg but I didn't see any problem. Well probably I don't know what to look at...

I've no idea what happened here.
Any help would be appreciated

Rudolf

[socratis]

My Fedora 25 upgraded to Kernel 4.9.12-200.fc25.x86_64 today.

People are having trouble with the 4.9.11 kernel, so you can imagine what's going on with 4.9.12. The test builds seem to have addressed some problems, at least with the 4.9.11, don't have a clue about 4.9.12, it's the first I'm hearing about it. See: https://www.virtualbox.org/wiki/Testbuilds and try out the latest and greatest.

[Martin]

I had a similar problem and after some time I found that switching off secure boot in BIOS allowed building the kernel modules again.

[socratis]

I've seen that in a recent thread, but about the Guest Additions. I guess it's the same mechanism that stops both of these procedures. I guess the developers have got to find a way around Secure Boot and its intricacies.

And I have to admit that the lined thread also talked about the 4.9.12 kernel.

[Perryg]

I had a similar problem and after some time I found that switching off secure boot in BIOS allowed building the kernel modules again.

IIRC this is caused by a signing issue with the latest kernels. VBox can not use the Fedora signing key and no one really should as it would defeat the purpose of the key, so it has to do with creating your own key. This also cropped up in Ubuntu I believe but the idea is to fix the way the kernel modules are installed/loaded which the DEVs are working on.

[curano]

I switched to SELinux permissive under /etc/selinux/config by rewriting SELINUX=enforced to SELINUX=permissive and this did the job!

Thank you all!