Rebooting with 4.4.0-20 kernel; output from a terminal:
oem@u64:~$ sudo dpkg-reconfigure virtualbox
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.service" and "journalctl -xe" for
details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
oem@u64:~$
oem@u64:~$ systemctl status virtualbox.service
● virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2016-04-16 18:40:23 CEST; 51s
ago
Docs: man:systemd-sysv-generator(8)
Process: 2385 ExecStart=/etc/init.d/virtualbox start (code=exited,
status=1/FAILURE)
Apr 16 18:40:23 u64 systemd[1]: Stopped LSB: VirtualBox Linux kernel module.
Apr 16 18:40:23 u64 systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Apr 16 18:40:23 u64 virtualbox[2385]: * Starting VirtualBox kernel modules
Apr 16 18:40:23 u64 virtualbox[2385]: * No suitable module for running kernel
found
Apr 16 18:40:23 u64 virtualbox[2385]: ...fail!
Apr 16 18:40:23 u64 systemd[1]: virtualbox.service: Control process exited,
code=exited status=1
Apr 16 18:40:23 u64 systemd[1]: Failed to start LSB: VirtualBox Linux kernel
module.
Apr 16 18:40:23 u64 systemd[1]: virtualbox.service: Unit entered failed state.
Apr 16 18:40:23 u64 systemd[1]: virtualbox.service: Failed with result
'exit-code'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571210
Title:
virtualbox[1239]: * No suitable module for running kernel found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571210/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
