Hello. I have the same problem on the 17.04, 16.10 and 16.04.2 LTS too.
I use the Ubuntu among with a Windows 10 in UEFI! When I install the virtualbox
it always ask a question about to disable the secure boot, if I have selected
the yes or no answer, the results were always the same:
[Here you can see the 17.04 output]
...
Setting up gcc-6 (6.3.0-12ubuntu2) ...
Setting up libqt5gui5:amd64 (5.7.1+dfsg-2ubuntu4~1) ...
Setting up qt5-gtk-platformtheme:amd64 (5.7.1+dfsg-2ubuntu4~1) ...
Setting up libqt5x11extras5:amd64 (5.7.1~20161021-2build1~1) ...
Setting up libqt5widgets5:amd64 (5.7.1+dfsg-2ubuntu4~1) ...
Setting up gcc (4:6.3.0-2ubuntu1) ...
Setting up libqt5printsupport5:amd64 (5.7.1+dfsg-2ubuntu4~1) ...
Setting up libqt5opengl5:amd64 (5.7.1+dfsg-2ubuntu4~1) ...
Setting up dkms (2.3-3) ...
Setting up libqt5svg5:amd64 (5.7.1~20161021-2build1~3) ...
Setting up virtualbox-dkms (5.1.18-dfsg-1build1) ...
Loading new virtualbox-5.1.18 DKMS files...
Building for 4.10.0-19-generic
Building initial module for 4.10.0-19-generic
Done.
vboxdrv:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.10.0-19-generic/updates/dkms/
vboxnetadp.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.10.0-19-generic/updates/dkms/
vboxnetflt.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.10.0-19-generic/updates/dkms/
vboxpci.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.10.0-19-generic/updates/dkms/
depmod...
DKMS: install completed.
Setting up virtualbox (5.1.18-dfsg-1build1) ...
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.
● virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2017-04-10 12:59:32 CEST; 9ms
ago
Docs: man:systemd-sysv-generator(8)
Process: 9566 ExecStart=/etc/init.d/virtualbox start (code=exited,
status=1/FAILURE)
ápr 10 12:59:32 AMD-Work-PC systemd[1]: Starting LSB: VirtualBox Linux kern…...
ápr 10 12:59:32 AMD-Work-PC virtualbox[9566]: * Loading VirtualBox kernel …...
ápr 10 12:59:32 AMD-Work-PC virtualbox[9566]: * modprobe vboxdrv failed. P…why
ápr 10 12:59:32 AMD-Work-PC virtualbox[9566]: ...fail!
ápr 10 12:59:32 AMD-Work-PC systemd[1]: virtualbox.service: Control process…s=1
ápr 10 12:59:32 AMD-Work-PC systemd[1]: Failed to start LSB: VirtualBox Lin…le.
ápr 10 12:59:32 AMD-Work-PC systemd[1]: virtualbox.service: Unit entered fa…te.
ápr 10 12:59:32 AMD-Work-PC systemd[1]: virtualbox.service: Failed with res…e'.
Hint: Some lines were ellipsized, use -l to show in full.
Setting up virtualbox-qt (5.1.18-dfsg-1build1) ...
Processing triggers for libc-bin (2.24-9ubuntu2) ...
Processing triggers for shim-signed (1.28+0.9+1474479173.6c180c6-1ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (232-21ubuntu2) ...
By the way the most interesting thing that on 16.04.2 I did not see this
problem if I used only the Ubuntu OS on my PC (without UEFI and Windows
10)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639310
Title:
Failed to start LSB: VirtualBox Linux Kernel Module
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1639310/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
