One of the ways Secure Boot maintains system security is by only allowing trusted kernel extensions to load. You must intervene if you want to run third-party modules like the VirtualBox Kernel Driver (vboxdrv).
OnmacOS, this is very easy to do as you canallow the module to loadfromSystem Preferences.
OnLinuxsystems, you should ensure the kernel and GCC versions are compatible with the vboxdrv module. you may alsomanually sign the moduleusing mokutil.
If such methods fail or you don’t care about Secure Boot, you may alwaysdisable Secure Bootto resolve this error.
How to Fix This Error on MacOS
Users must manually allow the loading of kernel extensions (KEXTs) on macOS 10.13 and newer versions. To do this,
Restart VirtualBoxStartup Service
utilize the following one-liner in the terminal to restart the startup service for loading the kernel module.
Repeat the steps from the previous section and reboot. Then, verify if you may start your VM in VirtualBox.
Register the vboxdrv Module
Registering the VirtualBox kernel extension directly via the terminal can also help. Enter the following one-liner in the terminal to do this:
Reboot and verify if you may launch the VM now.
Approve Oracle’s Dev ID
If manually loading vboxdrv doesn’t work,add Oracle’s developer ID to the security assessment policy. This will allow programs from Oracle (i.e. VirtualBox) to access the kernel.
Enter the following command in the terminal to do this:
