Geek Answers Handbook

Start vm failed after updating virtual box from 5.0.24 to 5.1

vboxmanage startvm shows the following message:

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

/ var / log / syslog shows version mismatch, but I don’t know where it is:

Nucleus

: [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 virtual box 5.1 and reinstalling 5.0.24

here as 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 update the virtual box?

What can I do to make it work on 5.1? OS - ubuntu 16.04 btw

+6
source share
6 answers

ok, finally i did it, tried to change Michael's answer, but rejected.
accommodation here:

Ubuntu solution:

Version mismatch caused by old modules to clear it:

 # 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 source and sources, then reboot to install virtualbox-5.1

0
source

It had the same problem in Debian, where I accidentally installed the Debian virtualbox-dkms package along with Oracle virtualbox-5.1 , which naturally were different versions.

Check via dpkg -l | grep virtualbox 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:

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

I had a similar problem, after a while I realized that there is a problem with removing 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 he worked.

Hope this helps

+6
source

I tried all the answers above, no one worked. The problem was that the debian virtual box was deleted correctly. It worked:

  • Close virtual block
  • 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
+1
source

How I fixed the Ubuntu 14.04 x64 server:

I try to do everything above, nothing helps.

  • stop all vbox services first (vboxautostart, vboxbaloon vboxdrv and vboxweb)
  • wait 10-15 seconds and check for any vbox
  • sudo apt-get remove virtualbox-5.*
  • Try first with the command: sudo update-grub
  • restart your computer and try installing virtualbox-5.*
  • If this does not work, than stop all vbox services, remove virtualbox-5.*
  • sudo apt-get autoremove (all kernel modules for the latter, I had 3 versions, and I do it twice apt-get autoremove)
  • sudo update-grub
  • reboot
  • install virtualbox-5.1 and after that it works
0
source

Try this sudo /sbin/vboxconfig . This works for me.

0
source

More articles:


All Articles