On Thu, Aug 13, 2020 at 05:41:46AM -0000, kortewegdevries wrote: > On, > > # cat /proc/version_signature > > Ubuntu 5.8.0-16.17-generic 5.8.0 > > After installing virtualbox, DKMS can now install modules against > current kernel but fails `modprobe vboxdrv` as a result: > > > DKMS: install completed. > Setting up virtualbox (6.1.12-dfsg-9) ... > Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb.service > Job for vboxweb.service failed because the service did not take the steps > required by its unit configuration. > See "systemctl status vboxweb.service" and "journalctl -xe" for details. > Job for virtualbox.service failed because the control process exited with > error code. > See "systemctl status virtualbox.service" and "journalctl -xe" for details. > invoke-rc.d: initscript virtualbox, action "restart" failed. > virtualbox.service - LSB: VirtualBox Linux kernel module > Loaded: loaded (/etc/init.d/virtualbox; generated) > Active: failed (Result: exit-code) since Thu 2020-08-13 03:44:26 UTC; > 17ms ago > Docs: man:systemd-sysv-generator(8) > Process: 5812 ExecStart=/etc/init.d/virtualbox start > (code=exited,status=1/FAILURE) > Aug 13 03:44:26 kortewegdevries systemd[1]: Starting LSB: VirtualBox Linux > kernel module... > Aug 13 03:44:26 kortewegdevries virtualbox[5812]: * Loading VirtualBox > kernel modules... > Aug 13 03:44:26 kortewegdevries virtualbox[5812]: * modprobe vboxdrv failed. > Please use 'dmesg' to find out why > Aug 13 03:44:26 kortewegdevries virtualbox[5812]: ...fail! > Aug 13 03:44:26 kortewegdevries systemd[1]: virtualbox.service: Control > process exited, code=exited, status=1/FAILURE > Aug 13 03:44:26 kortewegdevries systemd[1]: virtualbox.service: Failed with > result 'exit-code'. > Aug 13 03:44:26 kortewegdevries systemd[1]: Failed to start LSB: VirtualBox > Linux kernel module. > > I have secure boot on and also in previous releases it used to ask me to > sign the modules (ncurses menu) which it didn't now.
Some information about why the module didn't load may be found in dmesg; can you please supply that? The module will need to be signed if you are booted under secure boot, but just to check can you run 'cat /sys/kernel/security/lockdown' and confirm that the square braces appear around "integrity"? I don't routinely use any dkms modules, but iirc the prompt only happens the first time you install a dkms module for enrolling the MOK with shim. After that I thought the module signing happened silently, so could that be why you don't see any prompts? You can check whether the module is signed by running 'xxd /lib/modules/$(uname -r)/updaes/vboxdrv.ko | tail' (I think that should be the right path), and you should see "~Module signature appended~" appear at the end of the right-hand column. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884652 Title: virtualbox 6.1.10-dfsg-1 ADT test failure with linux-5.8 5.8.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1884652/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
