Ticket #11577 (new defect)

Opened 5 years ago

Last modified 18 months ago

Secure Boot doesn't allow 'vboxdrv' module to load - Required key not available

Reported by: quickbooks Owned by:
Priority: major Component: other
Version: VirtualBox 4.2.8 Keywords:
Cc:… Guest type: all
Host type: Linux


Host - Fedora 18 64 bit Bios has Secure Boot enabled.

When I try to start any machine it says:

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.
[user@localhost ~]$ sudo /etc/init.d/vboxdrv setup
[sudo] password for user: 
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)

[user@localhost ~]$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available

Change History

comment:1 Changed 5 years ago by quickbooks

[user@localhost ~]$ sudo virtualbox
[sudo] password for user: 
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (3.8.2-206.fc18.x86_64) or it failed to
         load. Please recompile the kernel module and install it by

           sudo /etc/init.d/vboxdrv setup

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

comment:2 Changed 5 years ago by frank

  • Priority changed from blocker to major

This is not really a VirtualBox bug. Oracle cannot sign kernel modules using the Fedora key. See also the  Fedora FAQ in this regards.

comment:3 Changed 3 years ago by marcmerlin

If I build my own kernel with signed modules, I have the key, dkms builds the virtualbox modules on my laptop which has the kernel source and my signing key. Can you enhance the dkms script to use /usr/src/linux-xxx/signing_key.* and sign the modules if those files are present?


comment:4 Changed 3 years ago by bryanhundven

This is still an issue on Fedora 22, I cannot disable secure boot on my workstation. The change marcmerlin suggested would work.

comment:5 Changed 2 years ago by khatkarrohit

Still a major problem on Ubuntu 16.04 using VirtualBox 5.0

Last edited 2 years ago by khatkarrohit (previous) (diff)

comment:6 Changed 18 months ago by Jdot

im having problems too on Ubuntu 16.04 using VirtualBox 5.1.6. when will this be sorted?

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use