[SOLVED] modprobe vboxdrv gives Required key not available
Posted: 23. Jan 2020, 02:53
Hi,
I've installed Virtualbox on a pretty new install of Ubuntu bionic (18.04) and downloaded a VDI image from osboxes. I loaded it in VirtualBox but when I want to start it I get the following dialogue:
but when I try to do the modprobe in the shell I get:
What am I missing? I've already tried purge & reinstall virtualbox-dkms but that didn't help either but I got a message like:
when I re-installed the package. I entered a password on the next dialogue and the rebooted.
Upon reboot, it brought me to a blue dialogue that let me Enroll in MOK upon which I entered that same password again, it then let me select reboot which brought my system back up but my Virtual Box still shows the above dialogue when I try to start the VM.
I've installed Virtualbox on a pretty new install of Ubuntu bionic (18.04) and downloaded a VDI image from osboxes. I loaded it in VirtualBox but when I want to start it I get the following dialogue:
Code: Select all
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please reinstall virtualbox-dkms package and load the kernel module by executing
'modprobe vboxdrv'
Code: Select all
# modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
Code: Select all
┌───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ Configuring Secure Boot ├────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ │
│ Your system has UEFI Secure Boot enabled. │
│ │
│ UEFI Secure Boot requires additional configuration to work with third-party drivers. │
│ │
│ The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. │
│ │
│ To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will │
│ be presented to you when this system reboots. │
│ │
│ If you proceed but do not confirm the password upon reboot, Ubuntu will still be able to boot on your system but any hardware that requires third-party drivers to work correctly may not be usable. │
│ │
│ <Ok> │
│ │
└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Upon reboot, it brought me to a blue dialogue that let me Enroll in MOK upon which I entered that same password again, it then let me select reboot which brought my system back up but my Virtual Box still shows the above dialogue when I try to start the VM.