Active11 months ago
Make sure that you have followed each of the steps correctly (especially the part where you exit your VirtualBox before entering in your code) and also make sure that your VirtualBox is on the latest version which is VirtualBox 5.1.22. Just double check that, but if the problem still persists then what you can do is check your system. I would like, if you could include this in the README: Issue with installing Oracle VM VirtualBox Extension Pack on OSX Oracle VM VirtualBox checks your permissions in /Applications and if they are too permissive, VirtualBox will throw a.
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
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.
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.
user2986683user2986683
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.```
Fixed it by:
sudo rmmod vboxpci vboxnetadp vboxnetflt vboxdrv
sudo apt-get purge virtualbox-dkms
sudo /sbin/vboxconfig
.
xtraxtra
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:
Then it worked.
Hope this helps
michaelmichael
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
6,83933 gold badges2525 silver badges2525 bronze badges
Try this one
sudo /sbin/vboxconfig
. It works for me.khaykkhayk
alright, finally i made it, tried to edit michael's answer but rejected.
posting here:
posting here:
version mismatch is caused by the old modules, to clean it up:
remove all vbox binaries and sources, then restart to install virtualbox-5.1
user2986683user2986683
How I did fix on Ubuntu 14.04 server x64:
I try to do everything above, nothing help.
![Virtualbox codes download Virtualbox codes download](/uploads/1/2/5/8/125819570/712312619.jpg)
- 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
138k1414 gold badges164164 silver badges215215 bronze badges
LonacLonac
Not the answer you're looking for? Browse other questions tagged virtualbox or ask your own question.
Active5 months ago
I was trying to run Oracle Virtualbox Manager but it is not working. I am getting the following error message:
How do I fix this issue ?
a_horse_with_no_name333k5555 gold badges515515 silver badges610610 bronze badges
beginITbeginIT11711 gold badge22 silver badges1111 bronze badges
2 Answers
I started virtual box in administrator mode, now it's able to start my VM
user3541290user3541290
The error message indicates that the image is inaccessible, this may be due to several reasons but in most cases, the image has been moved to another directory by making a cut paste from the Windows Explorer.
- go to the 'Machine Manager' and click on 'File'.
- Click on 'Media Manager'.
- In the first tab called 'Hard Drives', click on the image that is unreachable then click on the 'Release' button to remove the disk link (UUID) to the VM.
- Now click the 'Delete' button to remove the disk from the 'Virtual Media Manager'.
- Now all you have to do is add your image from the storage section and start on your virtual machine.
2,72511 gold badge66 silver badges1919 bronze badges
![Int Int](/uploads/1/2/5/8/125819570/469741993.png)