search

neoreeps / surface-pro-3

Notes, patches, etc for Ubuntu on Surface Pro 3
75 stars 13 forks source link

Cannot start Virtualbox machines #5

Open maurizi opened 8 years ago

maurizi commented 8 years ago

I'm using Ubuntu 15.10 on a Surface Pro 3.

I can't start Virtualbox machines after switching to this kernel, 4.3.0-reeps ( everything else is working great though :smile: ).

I tried running sudo apt-get purge virtualbox-dkms; sudo apt-get install virtualbox-dkms, and got an error:

> sudo apt-get install virtualbox-dkms
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.2.0-16 linux-headers-4.2.0-16-generic linux-image-4.2.0-16-generic linux-image-extra-4.2.0-16-generic linux-signed-image-4.2.0-16-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  virtualbox-dkms
0 upgraded, 1 newly installed, 0 to remove and 37 not upgraded.
Need to get 614 kB of archives.
After this operation, 4,960 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ wily/multiverse virtualbox-dkms all 5.0.4-dfsg-2 [614 kB]
Fetched 614 kB in 0s (676 kB/s)          
Selecting previously unselected package virtualbox-dkms.
(Reading database ... 313146 files and directories currently installed.)
Preparing to unpack .../virtualbox-dkms_5.0.4-dfsg-2_all.deb ...
Unpacking virtualbox-dkms (5.0.4-dfsg-2) ...
Setting up virtualbox-dkms (5.0.4-dfsg-2) ...
Loading new virtualbox-5.0.4 DKMS files...
First Installation: checking all kernels...
Building only for 4.3.0-reeps
Building initial module for 4.3.0-reeps
ERROR (dkms apport): kernel package linux-headers-4.3.0-reeps is not supported
Error! Bad return status for module build on kernel: 4.3.0-reeps (x86_64)
Consult /var/lib/dkms/virtualbox/5.0.4/build/make.log for more information.
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.

When I run systemctl status virtualbox.service, I get:

/dotfiles [ systemctl status -l virtualbox.service                           master * ] 9:48 PM
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox)
   Active: failed (Result: exit-code) since Fri 2015-11-20 21:25:09 EST; 23min ago
     Docs: man:systemd-sysv-generator(8)

Nov 20 21:25:09 mike-Surface-Pro-3 systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Nov 20 21:25:09 mike-Surface-Pro-3 virtualbox[4422]: * Starting VirtualBox kernel modules
Nov 20 21:25:09 mike-Surface-Pro-3 virtualbox[4422]: * No suitable module for running kernel found
Nov 20 21:25:09 mike-Surface-Pro-3 virtualbox[4422]: ...fail!
Nov 20 21:25:09 mike-Surface-Pro-3 systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Nov 20 21:25:09 mike-Surface-Pro-3 systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Nov 20 21:25:09 mike-Surface-Pro-3 systemd[1]: virtualbox.service: Unit entered failed state.
Nov 20 21:25:09 mike-Surface-Pro-3 systemd[1]: virtualbox.service: Failed with result 'exit-code'.

Any idea what I can do to get Virtualbox working?

magichowl commented 8 years ago

@maurizi The changelog of vbox 5.0.6 says it supports kernel 4.3, maybe you should try the latest vbox 5.0.12. Looking forward your good news

magichowl commented 8 years ago

I've tested virtual box 5.0.10 (or 5.0.12) can run. Only 32bit Windows host can be installed. I decide to try single system Ubuntu. Shorter than long pain.