Start vm failed after update virtualbox from 5.0.24 to 5.1

Question

Start vm failed after update virtualbox from 5.0.24 to 5.1

vboxmanage startvm shows the following message:

VBoxManage: error: The virtual machine 'VM02' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

/var/log/syslog shows there's a version mismatch, but i don't know where is it:

kernel: [45470.001207] SUP_IOCTL_COOKIE: Version mismatch. Requested: 0x260000 Min: 0x260000 Current: 0x240000

headless -h shows this:

VBoxHeadless: Error -1912 in supR3HardenedMainInitRuntime!

VBoxHeadless: RTR3InitEx failed with rc=-1912

vm works fine after removing virtualbox 5.1 and reinstalled 5.0.24

Here's how I upgrade to 5.1.

sudo apt update
sudo apt autoremove virtualbox-5.0
sudo apt install virtualbox-5.1
sudo vboxmanage extpack install Oracle_VM_VirtualBox_Extension_Pack-5.1.0-108711.vbox-extpack --replace

Is there something wrong when I upgrade virtualbox?

What can I do to get it work on 5.1? OS is ubuntu 16.04 btw.

virtualbox

asked on Stack Overflow Jul 19, 2016 by

user2986683 • edited Oct 12, 2018 by

Asif J

6 Answers

Had the same problem on Debian where I accidentally installed the Debian virtualbox-dkms package along with the Oracle version of virtualbox-5.1 which naturally were different versions.

Check via dpkg -l | grep virtualbox, if you have something like the following, you have the same situation.

ii  virtualbox-5.1  5.1.8-111374~Debian~jessie amd64 Oracle VM VirtualBox
ii  virtualbox-dkms 5.1.6-dfsg-2 all           x86   virtualization solution - kernel module sources for dkms

```

Fixed it by:

sudo rmmod vboxpci vboxnetadp vboxnetflt vboxdrv
sudo apt-get purge virtualbox-dkms
sudo /sbin/vboxconfig.

answered on Stack Overflow Oct 22, 2016 by

xtra

I had a similar problem, after a while I figured out there is a problem in removing the old modules. After uninstalling, rebooting and reinstalling I ran:

sudo rm /usr/lib/modules/4.5.7-202.fc23.x86_64/extra/vbox*
sudo rmmod vboxpci
sudo rmmod vboxnetadp
sudo rmmod vboxnetflt
sudo rmmod vboxdrv
sudo vboxconfig

Then it worked.

Hope this helps

answered on Stack Overflow Jul 19, 2016 by

michael • edited Jul 20, 2016 by

user2986683

Tried all the answers above, none worked. Issue was the debian virtualbox was uninstalled properly. The following worked:

Close virtualbox
sudo apt-get remove virtualbox-5.1
sudo apt-get install virtualbox
sudo apt-get purge virtualbox virtualbox-qt virtualbox-dkms
sudo apt-get install virtualbox-5.1
sudo vboxconfig

answered on Stack Overflow Mar 14, 2017 by

frmdstryr

Try this one sudo /sbin/vboxconfig. It works for me.

answered on Stack Overflow Nov 28, 2017 by

khayk

alright, finally i made it, tried to edit michael's answer but rejected.
posting here:

ubuntu solution:

version mismatch is caused by the old modules, to clean it up:

# stop all vbox services
sudo service vboxblahblah stop
# check all vbox is not running
ps -e | grep -i vbox
# remove 5.0 or maybe 5.1
sudo apt remove virtualbox-5.0
cd /
# find all vbox files to delete
sudo find -iname "vbox" 2>/dev/null

remove all vbox binaries and sources, then restart to install virtualbox-5.1

answered on Stack Overflow Jul 21, 2016 by

user2986683

How I did fix on Ubuntu 14.04 server x64:

I try to do everything above, nothing help.

stop first all vbox services (vboxautostart, vboxbaloon vboxdrv and vboxweb)
wait for 10-15 seconds and check is there any vbox
sudo apt-get remove virtualbox-5.*
Try first with command : sudo update-grub
reboot machine and than try install virtualbox-5.*
If doesn't work than stop all vbox services, remove virtualbox-5.*
sudo apt-get autoremove (all kernel modules to last one, I had 3 versions and I do it twice apt-get autoremove)
sudo update-grub
reboot
install virtualbox-5.1 and after that it is working

answered on Stack Overflow Oct 11, 2016 by

Lonac • edited Oct 11, 2016 by

Ingo Karkat

User contributions licensed under CC BY-SA 3.0