virtualbox 6.1.10-dfsg-1 ADT test failure with linux-5.8 5.8.0-1.2

Status changed to 'Confirmed' because the bug affects multiple users.

Hi, also fails on 5.8.0-12-generic Groovy proposed with secure boot and TPM. I think it's mostly a similar make.log. Do you want me to add a bug report?

This bug was fixed in the package virtualbox - 6.1.12-dfsg-9

---------------
virtualbox (6.1.12-dfsg-9) unstable; urgency=medium

  * Try to fix another kernel 5.8 change LP: #1884652

 -- Gianfranco Costamagna <email address hidden> Mon, 10 Aug 2020 14:37:08 +0200

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.

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.

Hi,

> 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"?

# cat /sys/kernel/security/lockdown

none [integrity] confidentiality

# bootctl status

System:
     Firmware: n/a (n/a)
  Secure Boot: enabled
   Setup Mode: user
 Boot into FW: supported

Also see attached dmesg: lines 68-69,102 for secure boot; lines 699-709 where it loads two keys I signed manually at some point; lines 1106-1121 were probably after reinstalling virtualbox.

> 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),...

It was under dkms there...

# xxd /lib/modules/$(uname -r)/updates/dkms/vboxdrv.ko| tail

0008ca10: 3100 0000 3d05 0000 0800 0000 0000 0000 1...=...........
0008ca20: 1800 0000 0000 0000 0900 0000 0300 0000 ................
0008ca30: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0008ca40: 3013 0500 0000 0000 68cd 0000 0000 0000 0.......h.......
0008ca50: 0000 0000 0000 0000 0100 0000 0000 0000 ................
0008ca60: 0000 0000 0000 0000 1100 0000 0300 0000 ................
0008ca70: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0008ca80: 08bc 0800 0000 0000 df01 0000 0000 0000 ................
0008ca90: 0000 0000 0000 0000 0100 0000 0000 0000 ................
0008caa0: 0000 0000 0000 0000 ........

# systemctl status virtualbox

● virtualbox.service - LSB: VirtualBox Linux kernel module
     Loaded: loaded (/etc/init.d/virtualbox; generated)
     Active: failed (Result: exit-code) since Thu 2020-08-13 12:58:50 UTC; 8min ago
       Docs: man:systemd-sysv-generator(8)

Aug 13 12:58:50 kortewegdevries systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Aug 13 12:58:50 kortewegdevries virtualbox[6653]: * Loading VirtualBox kernel modules...
Aug 13 12:58:50 kortewegdevries virtualbox[6653]: * modprobe vboxdrv failed. Please use 'dmesg' to fin>
Aug 13 12:58:50 kortewegdevries virtualbox[6653]: ...fail!
Aug 13 12:58:50 kortewegdevries systemd[1]: virtualbox.service: Control process exited, code=exited, st>
Aug 13 12:58:50 kortewegdevries systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Aug 13 12:58:50 kortewegdevries systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Aug 13 12:58:50 kortewegdevries virtualbox[6653]: * Loading VirtualBox kernel modules...
Aug 13 12:58:50 kortewegdevries kernel: Lockdown: modprobe: unsigned module loading is restricted; see >
Aug 13 12:58:50 kortewegdevries virtualbox[6653]: * modprobe vboxdrv failed. Please use 'dmesg' to fin>
Aug 13 12:58:50 kortewegdevries virtualbox[6653]: ...fail!
Aug 13 12:58:50 kortewegdevries systemd[1]: virtualbox.service: Control process exited, code=exited, st>
 Subject: Unit process exited
 Defined-By: systemd
  Support: http://www.ubuntu.com/support

An ExecStart= process belonging to unit virtualbox.service has exited.

The process' exit code is 'exited' and its exit status is 1.
Aug 13 12:58:50 kortewegdevries systemd[1]: virtualbox.service: Faile...

Well it isn't signed, and that appears to be the reason why the module won't load. That issue isn't relevant to this bug though, you should file a new bug against the dkms package.

> Well it isn't signed, and that appears to be the reason why the module won't load. That issue
> isn't relevant to this bug though, you should file a new bug against the dkms package.

Thanks will do, I was replying to this to follow on, since my [bug](https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1890770) was marked as a duplicate of this.

Hi, Seth I had to switch off Secure boot since I need virtualbox for work, but I have still this service failing, do you want me to open an issue about it:

> Aug 13 13:10:48 kortewegdevries systemd[1]: vboxweb.service: Can't open PID file /run/vboxweb.pid > (yet?) after start: Operation not permitted
> Aug 13 13:10:48 kortewegdevries systemd[1]: vboxweb.service: Failed with result 'protocol'.

Virtualbox runs fine but the service fails, same kernel same virtualbox neither received any update since.

On Wed, Aug 19, 2020 at 01:09:02PM -0000, kortewegdevries wrote:
> Hi, Seth I had to switch off Secure boot since I need virtualbox for
> work, but I have still this service failing, do you want me to open an
> issue about it:
>
> > Aug 13 13:10:48 kortewegdevries systemd[1]: vboxweb.service: Can't open PID file /run/vboxweb.pid > (yet?) after start: Operation not permitted
> > Aug 13 13:10:48 kortewegdevries systemd[1]: vboxweb.service: Failed with result 'protocol'.
>
> Virtualbox runs fine but the service fails, same kernel same virtualbox
> neither received any update since.

Yes, I'd recommend opening a new bug against virtualbox for this issue.

@Launchpad Janitor (janitor)
how do you fix virtualbox - 6.1.12-dfsg-9 build problem with kernel 5.18 ?
dkms modules can build success with 5.8.0-18-generic kernel, but build failed with my kernel 5.18.

modpost: "__get_vm_area_caller" undefined!
modpost: "map_kernel_range" undefined!