In 18.04 vboxdrv still taints the kernel:
May 26 12:23:53 cerberus virtualbox[3244]: * Loading VirtualBox kernel
modules...
May 26 12:23:53 cerberus kernel: vboxdrv: loading out-of-tree module taints
kernel.
May 26 12:23:53 cerberus kernel: vboxdrv: module verification failed: signature
and/or
I just bumped into this issue on Ubuntu 18.04.3 LTS
However, when I ran
sudo apt remove virtualbox-dkms virtualbox
and then
sudo apt install virtualbox-dkms
it guided me through the MOK process and after a reboot, Virtualbox was
happily loading again.
--
You received this bug notification beca
@Ed Peterson this bug is really fixed in 18.04 LTS release.
I'm sad to see you go, but we cared and fixed it almost one year ago.
(and such security feature was optional, and experimental, so people with
broken systems were not really using the default path)
--
You received this bug notification
This is my first post. I don't like to post. However, I've used ubuntu
and a few other linux versions for more than 10 years. I used to be able
to build a VM, install ubuntu, and be running in about 30 minutes. Now I
can't do that in a day (or unfortunately, sometimes days, or even
weeks...!). I'm
** Changed in: virtualbox (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgrade to Ubuntu 16.04 [required key
Nothing worked in http:
//askubuntu.com/questions/760671/could-not-load-vboxdrv-after-upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur
In my BIOS, there is no mention of "Enable support for legacy ...". So I
disabled secure boot (in the BIOS) & rebooted. Mow "Sudo modprobe vboxdrv"
works and so
You need to probably create a key and use it
http://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Doing sudo dpkg-reconfigure virtualbox-dkms didn't help.
VirtualBox is Version 5.0.24_Ubuntu r108355.
Attached are tar.gz of screenshots of dialog boxes in VirtualBox.
** Attachment added: "tar.gz of screenshots of dialog boxes in VirtualBox"
https://bugs.launchpad.net/ubuntu/+source/virtual
sudo dpkg-reconfigure virtualbox-dkms?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgrade to Ubuntu 16.04
To manage notifications about this bug go
I understand now about "on reboot, disable the secure boot through the
GUI". It came up after my entering "sudo apt install virtualbox". So I
selected Disable etc. The command finished OK as did "sudo apt install
virtualbox-dkms" though that didn't do anything as it must have been
installed by "sud
Thanks for reply about password. I entered the password twice and it
went into a mokutil screen for a few seconds. However, I don't
understand the instruction "on reboot, disable the secure boot through
the GUI". How do I do that?
--
You received this bug notification because you are a member of
That's not login password. You should enter some NEW password here,
which will be asked after reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgr
On "sudo sudo mokutil --disable-validation", I get:
john@NewLaptop:~$ sudo sudo mokutil --disable-validation
password length: 8~16
input password:
I've tried my login password and "password".
Any ideas please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: virtualbox (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgrade to Ubuntu 16.04
To manage not
@jaywink: thanks, it worked for me too!
For you all, here are the steps:
>sudo apt purge virtualbox-dkms
>sudo apt purge virtualbox
>sudo sudo mokutil --disable-validation
>reboot
then, on reboot, disable the secure boot through the GUI
>sudo apt install virtualbox
>sudo apt install virtua
Probably because kernel modules are built during installation, and you
have not the Ubuntu signing key, and moreover dkms doesn't support right
now the kernel signature done by the end user
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Can someone tell me why vboxdrv cannot be signed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgrade to Ubuntu 16.04
To manage notifications about t
Case of me, Virtualbox need upper gcc 5.0
2016. 6. 30. 오후 9:51에 "isabel" <1574...@bugs.launchpad.net>님이 작성:
> @jaywink, thanks, it worked after I uninstalled virtualbox, disabled,
> rebooted and confirmed disable, then reinstalled virtualbox.
>
> --
> You received this bug notification because you
@jaywink, thanks, it worked after I uninstalled virtualbox, disabled,
rebooted and confirmed disable, then reinstalled virtualbox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could
sudo dpkg-reconfigure virtualbox-dkms should fix the issue too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgrade to Ubuntu 16.04
To manage notifica
sudo dpkg-reconfigure virtualbox-dkms should fix the issue too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgrade to Ubuntu 16.04
To manage notifica
@isabel-t, maybe try to reinstall virtualbox, assuming your disabling of
the validation was successful and that isn't the problem any more.
Sorry, don't have much more on this, for me disabling validation solved
the problem.
--
You received this bug notification because you are a member of Ubuntu
anne@anne-Latitude-E7250:~$ systemctl status virtualbox
● virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2016-06-30 13:21:06 CEST; 6min
ago
Docs: man:systemd-sysv-
systemctl status virtualbox?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgrade to Ubuntu 16.04
To manage notifications about this bug go to:
https:
@jaywink
What did you do after disabling validation? Because I still get the same error
with virtualbox:
WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.
Ran into this after upgrading work computer from trusty to xenial. Tried
all possible install alternatives for VirtualBox (official and repos),
but module always refused to load.
In the end, as a hopefully temporary solution, disabled validation,
booted, confirmed to disable secure boot and voila,
Possible temporary workaround is to use different kernel version which
does not have EFI_SECURE_BOOT_SIG_ENFORCE option enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could no
I think the work is still ongoing according to the blueprints.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgrade to Ubuntu 16.04
To manage notifica
@LocutusOfBorg , the links you provided did not give any insight of the
problem at hand.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgrade to Ubuntu
somebody answered on the mail list :)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566221
https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot
https://blueprints.launchpad.net/ubuntu/+spec/foundations-x-installing-unsigned-secureboot
--
You received this bug notification because yo
@derlars, well, you can create your public - private key and import the private
key in your MOK, sign the vboxdrv module with your key combination and then
load the module.
But guess what, ubuntu does not load the key in the system keyring because of
bug #1461412 .
Fedora loads the keys in the k
well, this week somebody picked up the fact on Debian that dkms was
unmaintained.
Fortunately there have been a lot of activity and two uploads so far, seems it
is becoming again back on track.
https://lists.alioth.debian.org/pipermail/pkg-dkms-maint/2016-April/thread.html
I think forwarding the
@costamagnagianfranco yes, but what should oracle do? the dkms framework
will rebuild the module every time a new kernel is installed, so oracle
can't really do much, since the problem is the dkms framework not having
a plan for UEFI systems with secure boot.
Anything I can do to solve the problem
Virtualbox uses dkms, so I expect the fix should be there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
Could not load 'vboxdrv' after upgrade to Ubuntu 16.04
To manage notification
@costamagnagianfranco From my understanding, all new modules will now
have to be signed since the signature enforcement was activated in the
kernel. So, the dkms system would have to generate a local system key,
add this local key to the trusted keystore and would have to sign all
third-party-modul
@derlars, I'm the virtualbox maintainer, I asked to sync the kernel modules,
because I'm pretty sure with signature verification enabled you can't just
install the dkms package.
So I was hoping the official kernel virtualbox module (the one embedded in
linux kernel) was signed with the same key.
Does the proposed kernel disable signature verification by default? If
not, the bug will persist.
Moreover, this enforcement was by design.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title
*** This bug is a duplicate of bug 1571156 ***
https://bugs.launchpad.net/bugs/1571156
@costamagnagianfranco where did you find the information, that the
proposed kernel contains a fix? Does not solve the problem for me.
--
You received this bug notification because you are a member of Ubunt
*** This bug is a duplicate of bug 1571156 ***
https://bugs.launchpad.net/bugs/1571156
There is already a fix in the kernel -proposed. just try it, help in
debugging instead of bothering about having a fix.
You are the community, and testing is the best way to get a fix
released.
** This bu
there is Bug #1461412 that stops this workaround process, and it is open since
2015-06-03.
That gives you a hint at how much canonical developers and community cares
about systems security and LTS releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@ejohn Yes, I did the same too.
output of
> sudo mokutil --list-enrolled
lists the key I created.
And also,
> strings driver.ko
has a `~Module signature appended~` at the end, with my signature name.
Inference is that I have successfully enrolled the key which I created in
mokutils.
The mo
I am struggling with the same issue. This page gives some information on
what I have been trying. http://gorka.eguileor.com/vbox-vmware-in-
secureboot-linux/. I have successfully done mokutils --import but that
key does not appear in the keyctl system_keyring list. In my case
modinfo does not show
I used the kernel-source/scripts/sign-file utility to sign the driver,
but still I get the same error. How to find out if a module is signed or
not?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157430
Please do not close this.
using mokutil to "disable-validation" did not help, I'm still stuck and
vboxdrv will not load.
Am I missing something?
How can I fix this without disabling secure boot, or go through the loops and
sign the module?
--
You received this bug notification because you are
are you sure that
sudo mokutil --disable-validation"
is equivalent to disable EFI_SECURE_BOOT_SIG_ENFORCE?
Could it be that the latter disables only validation of modules, the
former of the kernel too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Thanks for the info. This is not a bug,
"Since Ubuntu kernel 4.4.0-20 the EFI_SECURE_BOOT_SIG_ENFORCE kernel
config has been enabled. That prevents from loading unsigned third party
modules if UEFI Secure Boot is enabled.
Since Ubuntu kernel build 4.4.0-21.37 this can be fixed by running
sudo ap
But if something works in 15.10 and breaks in 16.04 LTS, then it can be
considered a bug :)
it does not seem a bug, but a policy; see
https://answers.launchpad.net/ubuntu/+question/292158
https://www.virtualbox.org/ticket/11577#comment:2
to disable validation of modules (and maybe of kernel too
it does not seem a bug, but a policy; see
https://answers.launchpad.net/ubuntu/+question/292158
https://www.virtualbox.org/ticket/11577#comment:2
to disable validation of modules (and maybe of kernel too?) see
http://askubuntu.com/a/762248/534960
** Bug watch added: Virtualbox Trac #11577
h
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title:
systemctl status virtualbox.service output
● virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-04-24 20:34:40 IST; 1min
1s ago
Docs: man:systemd-sysv-generator(
This is the apt-get install output
DKMS: install completed.
Setting up virtualbox (5.0.18-dfsg-2build1) ...
vboxweb.service is a disabled or a static unit, not starting it.
Job for virtualbox.service failed because the control process exited with error
code. See "systemctl status virtualbox.servi
51 matches
Mail list logo
