Ask Your Question

VirtualBox not working on Fedora 20

asked 2014-09-20 11:13:30 -0600

Daniel01 gravatar image

updated 2014-09-20 12:48:41 -0600

Hi, I know this question has been asked but I still can't get VirtualBox to work on my machine. I have a Acer Aspire V5-552G with UEFI and Secure Boot. Ihave installed VirtualBox from the official repository but when I want to launch a vm I get the following error message:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

I have installed kerne-devel, and DKMS, but still nothig. By running sudo /etc/init.d/vboxdrv setup I get the message:

sudo /etc/init.d/vboxdrv setup 
Stopping VirtualBox kernel modules                         [  OK  ]
Uninstalling old VirtualBox DKMS kernel modules            [  OK  ]
Trying to register the VirtualBox kernel modules using DKMS[  OK  ]
Starting VirtualBox kernel modules                         [FAILED]
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

And finally by running dmesg I get:

[ 3637.632521] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
edit retag flag offensive close merge delete

5 Answers

Sort by ยป oldest newest most voted

answered 2014-09-21 00:51:49 -0600

cgonz31 gravatar image

updated 2014-11-17 15:36:08 -0600

I had the same issue some time ago. Apparently, Secure Boot was to blame. VirtualBox needs to load its own kernel modules which are not signed using the Fedora key. So with Secure Boot enabled, the VirtualBox kernel modules will not load and you can't run VMs. See links below:

The easiest workaround is to disable Secure Boot. To have VirtualBox work in Secure Boot requires extensive knowledge of working with Secure Boot, which I don't have. But here's a link to get you started:

Also make sure you have the latest kernel and make, binutils, gcc, dkms, kernel-headers, kernel-devel, and kernel-modules-extra packages installed. If you have to install any of these, reboot, and reinstall VirtualBox.


This method below worked perfectly for me. I can now use VirtualBox in Secure Boot. Note that I'm using the VirtualBox release from the Oracle RPM repo.

edit flag offensive delete link more



Thanks a lot, It worked well for me.

ihsun gravatar imageihsun ( 2015-02-10 20:13:43 -0600 )edit

The signing does not work on F23. After sign-file stage, modinfo does not show any difference, plus this issue does not let you import the key. Best is to ditch secureboot, and along with it Windows 10. It was never going to be easy, or useful

dashesy gravatar imagedashesy ( 2016-05-08 13:55:20 -0600 )edit

answered 2016-02-26 12:50:59 -0600

lmaurin gravatar image
edit flag offensive delete link more

answered 2015-10-02 12:04:38 -0600

Mce128 gravatar image

If you are having the problem with secureboot, signing the kernel module is easy. Check out

edit flag offensive delete link more

answered 2014-09-20 13:12:05 -0600

Glenn gravatar image

Is this a 32Bit or a 64Bit OS? Have you installed the newest kernel? Have you booted into the newest kernel?

I recommend checking to see if there is a kernel update available before going any further. Update the kernel if available and reboot into that kernel. Either way, make sure you're running the newest installed kernel. Then install kernel-devel and gcc.

yum install kernel-devel-$(uname -m) gcc

One installed try running /etc/init.d/vboxdrv setup.

edit flag offensive delete link more

Question Tools



Asked: 2014-09-20 11:13:30 -0600

Seen: 14,983 times

Last updated: Feb 26 '16