[Solved] Kernel driver signing procedure stopped working after update

[NginUS]

Tonight the steps I follow every time I upgrade to a new kernel stopped working. Probably doesn't help that there's a new VirtualBox app too- it was happening before & after I updated that for what its worth...

Usually I only have to re-run the script part, but after that failed I tried the whole thing over again but still no go. Here's my procedure:

Code: Select all

sudo -i
mkdir /root/module-signing
cd /root/module-signing
openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=ME/"
chmod 600 MOK.priv
mokutil --import /root/module-signing/MOK.der
<password>
<password>

(Reboot)
(Enroll Key)

Run Script:

Code: Select all

#!/bin/bash

for modfile in $(dirname $(modinfo -n vboxdrv))/*.ko; do
  echo "Signing $modfile"
  /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \
                                /root/module-signing/MOK.priv \
                                /root/module-signing/MOK.der "$modfile"
done

Code: Select all

sudo modprobe vboxdrv
sudo /sbin/vboxconfig

The error is:

Failed to open a session for the virtual machine Hostname.

The virtual machine 'Hostname' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

Screenshot of additional error detail:
https://imgur.com/a/RoHNX

Also here:

Untitled.jpg (64.49 KiB) Viewed 1362 times

[patrickdayton]

I have this issue as well. I cannot do anything with Chef, or vagrant. This happened after I ran:

Code: Select all

apt-get update -y && apt-get upgrade -y

So far, I have completely purged my system of VirtualBox and Vagrant, installed Vagrant 2.0.1, installed VirtualBox 5.2.6, ran 'sudo /sbin/vboxconfig', and restarted my system. I still receive this error below:

Code: Select all

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "553386fa-f3ef-4ee9-aab3-a5a0e7b13dab", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'vagrant2_default_1516280000608_98248' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

My system is running:
Linux 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

[socratis]

I cannot do anything with Chef, or vagrant.

Neither is supported in these forums, they have their own support. If you are having this problem with a standalone version of VirtualBox, then we can continue this discussion.

[NginUS]

For whatever reason, its working now after a few aptitude upgrade commands over the last week. Don't have any idea why...

[socratis]

Don't have any idea why...

Same here

Thanks for the feedback. And thank you for marking it as [Solved].