Since version 4.4 of the Linux kernel kernel module signing has been enforced with Secure Boot, but virtualbox cannot function properly as its kernel module is not signed
Bug #1587184 reported by
Wise Melon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| virtualbox (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
I have recently found that after upgrading to Ubuntu GNOME 16.04 with GNOME 3.20 that VirtualBox is no longer able to launch VMs, and that dkms cannot register its kernel module. This is due to the fact that kernel module signing has been enforced with those using Secure Boot since Linux kernel version 4.4 and as the virtualbox kernel module is not signed it is unable to run. So the best way of fixing this problem would be to start signing virtualbox kernel modules.
As can be seen here I am not the only one experiencing issues: https:/
| Changed in virtualbox (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| Gianfranco Costamagna (costamagnagianfranco) wrote | #1 |
| Changed in virtualbox (Ubuntu): | |
| importance: | Undecided → Medium |
To post a comment you must log in.
Hi, yes, unfortunately I don't know how to fix that.
The kernel modules should be ship also in the kernel package, so they should be installable anyway.