1

Hi recently installed a fresh copy of Ubuntu Server 17.04 and virtualbox on it and then ran the do-release-upgrade command to upgrade to 17.10.

I now end up getting the following error, is it because of the kernel version or something else? At this point of time virtualbox's website suggested the latest download being available for Ubutu 17.04 :(

-- Unit virtualbox.service has begun starting up.
Oct 28 14:55:31 ares virtualbox[902]:  * Loading VirtualBox kernel modules...
Oct 28 14:55:31 ares virtualbox[902]:  * No suitable module for running kernel found
Oct 28 14:55:31 ares virtualbox[902]:    ...fail!
Oct 28 14:55:31 ares systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Oct 28 14:55:31 ares 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 failed.

apt list virtualbox gives the following output:

Listing... Done
virtualbox/artful,now 5.1.30-dfsg-1 amd64 [installed]

reinstalled vbox still get the following (when installing):

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 Sat 2017-10-28 16:25:50 CEST; 5ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 4586 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)
      CPU: 26ms

Oct 28 16:25:50 ares systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Oct 28 16:25:50 ares virtualbox[4586]:  * Loading VirtualBox kernel modules...
Oct 28 16:25:50 ares virtualbox[4586]:  * No suitable module for running kernel found
Oct 28 16:25:50 ares virtualbox[4586]:    ...fail!
Oct 28 16:25:50 ares systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Oct 28 16:25:50 ares systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Oct 28 16:25:50 ares systemd[1]: virtualbox.service: Unit entered failed state.
Oct 28 16:25:50 ares systemd[1]: virtualbox.service: Failed with result 'exit-code'.
  • I see virtualbox/artful 5.1.30-dfsg-1 on apt search so how did you get that version? – George Udosen Oct 28 '17 at 13:20
  • If I recollect correctly, I had installed virtualbox on 17.04 and then ran the release-upgrade. I'll edit/update the question to reflect the same – Kunal Oct 28 '17 at 13:49
  • @George I would assume via download from virtualbox.org – Charles Green Oct 28 '17 at 13:51
  • @Kunal Can you append your question with the output of apt list virtualbox – Charles Green Oct 28 '17 at 13:53
  • @CharlesGreen done – Kunal Oct 28 '17 at 13:59
0

It seems that for some reason during the upgrade from 17.04 to 17.10 the kernel got switched from 4.13.0-16-generic to 4.13.0-16-lowlatency. It could be due to the fact that I ran the upgrade over ssh client instead of on the system itself. I did not investigate further as to why this happened. Since this was a new machine, I wiped it clean and installed 17.04 and upgraded to 17.10 on the terminal itself.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.