Virtualbox vboxdrv module load fails on kernel 4.4.0-20

[Harm van Bakel]

Since updating the Xenial kernel to the latest 4.4.0-20 version the vboxdrv module loading fails with the following error:

modprobe: ERROR: could not insert 'vboxdrv': Required key not available

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: virtualbox 5.0.16-dfsg-3
ProcVersionSignature: Ubuntu 4.4.0-20.36-generic 4.4.6
Uname: Linux 4.4.0-20-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 18 15:54:54 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-25 (23 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
SourcePackage: virtualbox
UpgradeStatus: No upgrade log present (probably fresh install)

[Supercomputing @ Government of Canada (ssc-hpc-chp-spc)]

Not sure if it is the same bug, but when I compile my MT7630 wireless driver, I just started getting that message also.
I'm on 4.4.0-19 generic #35. Cannot compile any modules:

message is always modprobe: ERROR: could not insert 'module': Required key not available.
fails for MT7630, and evdi modules which are both external to the source tree.

[Harm van Bakel (hvbakel)]

It looks like this is due to the changes implemented in Bug #1566221 to block loading of unsigned or incorrectly signed modules. I'm wondering if it's possible to have DKMS use the ubuntu signing key?

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1571815

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.