Monthly Archives: March 2017

You are here: Home . Archive

Virtualbox in Secure Boot Kernel upgrade error

If you run Ubuntu (and probably many other Linux distros) and you run virtualbox/vagrant and have Secure Boot enabled, you are likely to run into the following error every time you upgrade your Kernel (which in Ubuntu’s case is very often):

username@host/vagrant/path$ sudo vagrant up
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

VirtualBox is complaining that the installation is incomplete. Please
run `VBoxManage --version` to see the error message which should contain
instructions on how to fix this error.

If you use vvv for WordPress development, you’ll run into this quite often.


Here’s what you should do:

#Sign the kernel modules again. Make sure you still have your X.509 Key Pair
for f in $(dirname $(modinfo -n vboxdrv))/*.ko; do echo "Signing $f"; sudo /usr/src/linux-headers-4.4.0-<span style="color: #ff0000;"><strong>xx</strong></span>-generic/scripts/sign-file sha256 ./iamlocal_MOK.priv ./iamlocal_MOK.der $f; done

Make sure xx is the latest/highest number in the /usr/src/linux-headers-4.4.0-* series.

and then reconfigure virtualbox:

 sudo dpkg-reconfigure virtualbox-dkms
 sudo dpkg-reconfigure virtualbox
 sudo modprobe vboxdrv

If you haven’t created a X.509 Key Pair before, there’s this great tutorial on how to go about it:

UPDATE 05/04/17: I’ve added a script for this here: VirtualBox DKMS Error Fix. Add this to your PATH and all you’ll need to do going forward is run the script to resolve the issue