Ask Your Question
2

Install VirtualBox on Fedora 25 (UEFI Secure Boot & Kernel Modules Signing)

asked 2016-12-10 08:05:39 -0500

Marzian gravatar image

updated 2016-12-14 16:59:38 -0500

I have followed these guides to install VirtualBox on Fedora 25, in a system with UEFI Secure Boot:

https://www.if-not-true-then-false.co...

http://gorka.eguileor.com/vbox-vmware...

But when I get to the rebooting part (after using mokutil --import MOK.der), nothing happens, except for an error during boot:

[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.

If I give that command, this is the output:

Unit systemd-modules-load.service has begun starting up.
kernel: PKCS#7 signature not signed with a trusted key
systemd-modules-load[5134]: Failed to insert 'vboxdrv': Required key not available
kernel: PKCS#7 signature not signed with a trusted key
kernel: PKCS#7 signature not signed with a trusted key
kernel: PKCS#7 signature not signed with a trusted key
systemd-modules-load[5134]: Failed to insert 'vboxnetflt': Required key not available
systemd-modules-load[5134]: Failed to insert 'vboxnetadp': Required key not available
systemd-modules-load[5134]: Failed to insert 'vboxpci': Required key not available
systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-modules-load.service has failed.
-- The result is failed.

In the end, I still can't add the kernel module:

$ sudo modprobe -v vboxdrv
insmod /lib/modules/4.8.11-300.fc25.x86_64/misc/vboxdrv.ko 
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
edit retag flag offensive close merge delete

Comments

Did you receive any errors during installation? Try executing dnf history, identify the entry which represents your installation of the VirtualBox-5.1 package, and then do a dnf history info <id> where "<id>" is the number of the history entry which corresponds to that installation effort. Look and see if there are any error messages near the bottom of the output; it could be that the module build failed. Perhaps you are missing the kernel headers for your current kernel?

bitwiseoperator gravatar imagebitwiseoperator ( 2016-12-10 10:31:16 -0500 )edit

I found out the problem seems due to UEFI Secure Boot... But I'm still not out of it. The post has been updated.

Marzian gravatar imageMarzian ( 2016-12-10 11:03:45 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2016-12-11 17:18:02 -0500

updated 2016-12-11 17:19:31 -0500

That's happening because you can't load an unsigned kernel module with Secure Boot enabled. Here are instructions for signing the module, yourself: http://gorka.eguileor.com/vbox-vmware...

And in case you aren't aware of suitable alternatives to VirtualBox, I would recommend that you simply use KVM/QEMU/libvirtd with virt-manager. If you want something simpler (and more VirtualBox-esque), try GNOME Boxes. If you know about those alternatives but are choosing VirtualBox for some good reason, carry on. =)

edit flag offensive delete link more

Comments

I know: I had edited the question (also adding that reference). The fact is that I cannot complete the signing process, and I'm stuck: "when I get to the rebooting part (after using mokutil --import MOK.der), nothing happens, except for an error during boot suggesting to launch $ systemctl status akmods.service"

And yes, I do have a good reason to choose VirtualBox!

Marzian gravatar imageMarzian ( 2016-12-12 16:43:22 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2016-12-10 08:05:39 -0500

Seen: 5,191 times

Last updated: Dec 14 '16