I am having problems running VirtualBox on my Ubuntu laptop. My laptop is dual boot, and running (Windows 10 - I think, haven't used it in years), as well as Ubuntu 16.0.4 LTS.
I have secure boot enabled on the BIOS settings of my laptop.
I am aware that there are similar questions posted on here, specifically these two:
- Failed installation of Virtualbox 5.1 on Ubuntu 16.04
- VirtualBox Installation gives message “modprobe vboxdrv” failed
I have followed all of the instructions given in the answers sections for those two questions - yet, the problem remains unresolved.
Here is the console output, when I attempt to run virtualbox:
me@YOURBOX:~$ virtualbox WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (4.4.0-47-generic) or it failed to load. Please recompile the kernel module and install it by sudo /sbin/vboxconfig You will not be able to start VMs until this problem is fixed.
here is the console output when I run
/sbin/vboxconfig as suggested:
me@YOURBOX:~$ sudo /sbin/vboxconfig vboxdrv.sh: Stopping VirtualBox services. vboxdrv.sh: Building VirtualBox kernel modules. vboxdrv.sh: Starting VirtualBox services. vboxdrv.sh: Building VirtualBox kernel modules. vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why. There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root.
Here is the tail end of the output of
[ 44.319682] audit: type=1400 audit(1491313982.374:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" pid=705 comm="apparmor_parser" [ 45.041433] cgroup: new mount options do not match the existing superblock, will be ignored [ 59.682936] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 59.697820] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 59.702008] IPv6: ADDRCONF(NETDEV_UP): enp2s0f0: link is not ready [ 60.267000] IPv6: ADDRCONF(NETDEV_UP): enp2s0f0: link is not ready [ 62.473044] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 70.681706] audit_printk_skb: 60 callbacks suppressed [ 70.681709] audit: type=1400 audit(1491314008.734:32): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=2009 comm="apparmor_parser" [ 70.850936] aufs 4.x-rcN-20160111 [ 75.407218] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. [ 75.408555] Bridge firewalling registered [ 75.427172] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 75.848416] ip_tables: (C) 2000-2006 Netfilter Core Team [ 76.703232] Initializing XFRM netlink socket [ 77.060003] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready [ 80.101042] aufs au_opts_verify:1597:dockerd: dirperm1 breaks the protection by the permission bits on the lower branch [ 113.895236] wlp3s0: authenticate with 84:16:f9:77:e1:54 [ 113.910483] wlp3s0: send auth to 84:16:f9:77:e1:54 (try 1/3) [ 113.912712] wlp3s0: authenticated [ 113.915101] wlp3s0: associate with 84:16:f9:77:e1:54 (try 1/3) [ 113.919397] wlp3s0: RX AssocResp from 84:16:f9:77:e1:54 (capab=0x1411 status=0 aid=1) [ 113.919516] wlp3s0: associated [ 113.919559] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Now, I'm not going to lie - I have absolutely no idea what dmesg just spewed out - and as far as I can tell, there are no error messages in the log output - which makes the situation even more infuriating.
Has anyone ever installed VirtualBox 5.x on a laptop running Ubuntu 16.0.4 LTS - but with secure boot enabled on BIOS ? - if yes, what is the solution. ???!
Lots of people have this problem - even going a few years back. it is very strange that no one seems to have a solution for it - ???