VB broken after upgrade to Ubuntu 16.04

[amcnaughton]

VirtualBox stopped working after I upgraded to Ubuntu 16.04. To try and fix the problem I purged VB and reinstalled virtualbox-5.0_5.0.18-106667~Ubuntu~xenial_amd64.deb

Here's what happens now:

allan@allan-XPS-13:~$ VBoxManage --version
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.4.0-21-generic) or it failed to
load. Please recompile the kernel module and install it by

sudo /sbin/rcvboxdrv setup

You will not be able to start VMs until this problem is fixed.
5.0.18r106667
allan@allan-XPS-13:~$ sudo /sbin/rcvboxdrv setup
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMS ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
allan@allan-XPS-13:~$

Here's the last line from dmesg:

[ 50.386030] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)

Any help is much appreciated!

Allan

[Perryg]

Assuming you used the Ubuntu software center to install I suspect you have a missing dependency.

Use dpkg to install and it should report any missing dependencies and then use apt-get install -f to install them.

[amcnaughton]

Here's the result of dpkg. Any suggestions as it still fails?

allan@allan-XPS-13:~/Downloads$ sudo dpkg -i virtualbox-5.0_5.0.18-106667-Ubuntu-xenial_amd64.deb
(Reading database ... 230545 files and directories currently installed.)
Preparing to unpack virtualbox-5.0_5.0.18-106667-Ubuntu-xenial_amd64.deb ...
Unpacking virtualbox-5.0 (5.0.18-106667~Ubuntu~xenial) over (5.0.18-106667~Ubuntu~xenial) ...
Setting up virtualbox-5.0 (5.0.18-106667~Ubuntu~xenial) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMS ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Processing triggers for systemd (229-4ubuntu4) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160415-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for gnome-menus (3.13.3-6ubuntu3) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
Processing triggers for mime-support (3.59ubuntu1) ..
.
allan@allan-XPS-13:~/Downloads$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
kbuild libgsoap8 libvncserver1 module-assistant virtualbox-source
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

[Perryg]

(modprobe vboxdrv failed. Please use 'dmesg' to find out why)

It would help if when these prompts happen you do what they say and then provide the information.

You may also want to try to purge the installed version of VirtualBox and then use dpkg again to install it. That would remove all previous packages and configs that could be causing this.

[amcnaughton]

I needed to install libvpx2_1.4.0-4_amd64.deb

Problem solved.