[18.10] 2x latest Kernels(4.18.0-15-generic + -16) + latest virtualbox(5.2.18-dfsg-2ubuntu18.10.1) = KO?

Support & Help Requests
#1

Hello,

A recent problem that popped up is that VirtualBox now refuses to work on my system running UM 18.10 latest.

$ uname -a
Linux T-2030 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$

I have purged virtualbox, reinstalled it and have retried relaunching yet nothing happens. Also there are no error at program launch nor any zombie PIDs.

$ ps -ef | grep -i virtualbox
t        13048 12982  0 18:06 pts/1    00:00:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn -i virtualbox
$

Just so we're clear:

$  apt list --installed | grep -i virtual

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

virtualbox-dkms/cosmic-updates,cosmic-updates,cosmic-security,cosmic-security,now 5.2.18-dfsg-2ubuntu18.10.1 all [installed,automatic]
virtualbox-guest-utils/cosmic-updates,cosmic-security,now 5.2.18-dfsg-2ubuntu18.10.1 amd64 [installed]
virtualbox-qt/cosmic-updates,cosmic-security,now 5.2.18-dfsg-2ubuntu18.10.1 amd64 [installed,automatic]
virtualbox/cosmic-updates,cosmic-security,now 5.2.18-dfsg-2ubuntu18.10.1 amd64 [installed]
$

Only thing I could find is:

$ dmesg | tail
[   62.604722] usb 2-1-port1: unable to enumerate USB device
[   92.922206] vboxdrv: loading out-of-tree module taints kernel.
[   92.922390] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[   92.930282] vboxdrv: Found 12 processor cores
[   92.952188] vboxdrv: TSC mode is Invariant, tentative frequency 3593248030 Hz
[   92.952189] vboxdrv: Successfully loaded version 5.2.18_Ubuntu (interface 0x00290001)
[   92.957093] VBoxNetFlt: Successfully started.
[   92.962016] VBoxNetAdp: Successfully started.
[   92.966798] VBoxPciLinuxInit
[   92.968336] vboxpci: IOMMU found

But before applying old fixes ( Ref.: https://stackoverflow.com/questions/24975377/kvm-module-verification-failed-signature-and-or-required-key-missing-taintin ) I wanted to first check in with the Community because this worked fine not too long ago.

Guess my next step is, again, to rollback to previous kernel.

Please advise,

#2

Here are more infos using the previous kernel:


$ uname -a
Linux T-2030 4.18.0-15-generic #16-Ubuntu SMP Thu Feb 7 10:56:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ sudo service virtualbox status
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox; generated)
   Active: failed (Result: exit-code) since Wed 2019-03-13 18:20:27 EDT; 31s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 5526 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Mar 13 18:20:27 T-2030 systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Mar 13 18:20:27 T-2030 virtualbox[5526]:  * Loading VirtualBox kernel modules...
Mar 13 18:20:27 T-2030 virtualbox[5526]:  * No suitable module for running kernel found
Mar 13 18:20:27 T-2030 virtualbox[5526]:    ...fail!
Mar 13 18:20:27 T-2030 systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Mar 13 18:20:27 T-2030 systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Mar 13 18:20:27 T-2030 systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.

$ sudo service virtualbox restart
Job for virtualbox.service failed because the control process exited with error code.
See "systemctl status virtualbox.service" and "journalctl -xe" for details.

$ journalctl -xe
Mar 13 18:20:19 T-2030 sudo[5481]:        t : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/sbin/service virtualbox status
Mar 13 18:20:19 T-2030 sudo[5481]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 18:20:19 T-2030 sudo[5481]: pam_unix(sudo:session): session closed for user root
Mar 13 18:20:26 T-2030 sudo[5497]:        t : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/sbin/service virtualbox start
Mar 13 18:20:26 T-2030 sudo[5497]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 18:20:27 T-2030 systemd[1]: Starting LSB: VirtualBox Linux kernel module...
-- Subject: Unit virtualbox.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit virtualbox.service has begun starting up.
Mar 13 18:20:27 T-2030 virtualbox[5526]:  * Loading VirtualBox kernel modules...
Mar 13 18:20:27 T-2030 virtualbox[5526]:  * No suitable module for running kernel found
Mar 13 18:20:27 T-2030 virtualbox[5526]:    ...fail!
Mar 13 18:20:27 T-2030 systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Mar 13 18:20:27 T-2030 systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Mar 13 18:20:27 T-2030 systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
-- Subject: Unit virtualbox.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit virtualbox.service has failed.
-- 
-- The result is RESULT.
Mar 13 18:20:27 T-2030 sudo[5497]: pam_unix(sudo:session): session closed for user root
Mar 13 18:20:59 T-2030 sudo[5593]:        t : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/sbin/service virtualbox status
Mar 13 18:20:59 T-2030 sudo[5593]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 18:20:59 T-2030 sudo[5593]: pam_unix(sudo:session): session closed for user root
Mar 13 18:21:01 T-2030 sm-msp-queue[5457]: unable to qualify my own domain name (T-2030) -- using short name
Mar 13 18:21:01 T-2030 CRON[5430]: pam_unix(cron:session): session closed for user smmsp
Mar 13 18:21:01 T-2030 sudo[5605]:        t : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/sbin/service virtualbox restart
Mar 13 18:21:01 T-2030 sudo[5605]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 18:21:01 T-2030 systemd[1]: Starting LSB: VirtualBox Linux kernel module...
-- Subject: Unit virtualbox.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit virtualbox.service has begun starting up.
Mar 13 18:21:01 T-2030 virtualbox[5611]:  * Loading VirtualBox kernel modules...
Mar 13 18:21:01 T-2030 snapd[1049]: udevmon.go:190: udev monitor observed remove event for unknown device "/sys/mm_struct(1219:virtualbox.service)"
Mar 13 18:21:01 T-2030 virtualbox[5611]:  * No suitable module for running kernel found
Mar 13 18:21:01 T-2030 virtualbox[5611]:    ...fail!
Mar 13 18:21:01 T-2030 systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Mar 13 18:21:01 T-2030 systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Mar 13 18:21:01 T-2030 systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
-- Subject: Unit virtualbox.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit virtualbox.service has failed.
-- 
-- The result is RESULT.
Mar 13 18:21:01 T-2030 sudo[5605]: pam_unix(sudo:session): session closed for user root
1 Like