Inaccessible VM

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
asabbah
Posts: 1
Joined: 24. Oct 2013, 20:22

Inaccessible VM

Post by asabbah »

I removed a Linux (Fedora) VM, then uninstalled Vbox, and reinstalled, and there it is again. Showing a stop sign, inaccessible, with the following error:
Runtime error opening '/Users/asabbah/VirtualBox VMs/Fedora 17/Fedora 17.vbox' for reading: -102(File not found.).
/Users/vbox/tinderbox/4.3-mac-rel/src/VBox/Main/src-server/MachineImpl.cpp[727] (nsresult Machine::registeredInit()).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

I searched for the file on the computer but it is gone, and I am unable to remove the entry from VBox, please help.
noteirak
Site Moderator
Posts: 5231
Joined: 13. Jan 2012, 11:14
Primary OS: Debian other
VBox Version: OSE Debian
Guest OSses: Debian, Win 2k8, Win 7
Contact:

Re: Inaccessible VM

Post by noteirak »

asabbah wrote:I am unable to remove the entry from VBox
Because you get an error message? If yes, which one?
Hyperbox - Virtual Infrastructure Manager - https://apps.kamax.lu/hyperbox/
Manage your VirtualBox infrastructure the free way!
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Inaccessible VM

Post by mpack »

You can't remove a VM by deleting a VM folder - which I suspect was what was done here. The problem is that the VM remains registered in VirtualBox. You should have asked VirtualBox to remove the VM.

The VM register is data. Data is not affected by reinstalling the VirtualBox software.

Have you tried right clicking the VM in the GUI and selecting "Remove"?

Other options are to edit the VirtualBox.xml manually, for which you need to understand what you're doing. Or you can delete VirtualBox.xml entirely, which will cause all VMs to be unregistered.
FrAgFo0d
Posts: 2
Joined: 30. Oct 2013, 11:05

Re: Inaccessible VM

Post by FrAgFo0d »

What if you don't have the VirtualBox.xml ?

I removed VirtualBox from my machine (all the files) and after re-installing it says:

"The selected virtual machine is inaccessible."
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Inaccessible VM

Post by mpack »

You do have a VirtualBox.xml, as VBox wouldn't run without it. As a data file, it is not removed by reinstalling the software. Look in your documents area for a .VirtualBox folder, inside which is that xml.
rpmurray
Volunteer
Posts: 918
Joined: 3. Mar 2009, 00:29
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows 7, Mac OS X (various flavors)
Location: Between Heaven and Hell

Re: Inaccessible VM

Post by rpmurray »

mpack wrote:Look in your documents area for a .VirtualBox folder, inside which is that xml.
Actually, no. On a Mac the VirtualBox.xml file will be stored on the following path:

<hard drive>/Users/<user account>/Library/VirtualBox
hibakushamoto
Posts: 10
Joined: 18. Dec 2013, 08:00

Re: Inaccessible VM

Post by hibakushamoto »

Has anyone found a solution to this?

I am running OSX Mavericks and VB 4.3.4 with a CentOS 6.5 guest.

I tried to upgrade to 4.3.4 but it broke, so I uninstalled it and started fresh and now my one guest VM says it is Inaccessible.
I do not need it and want to just delete it but I cannot. When I right click on it and use the remove option, nothing happens.

I located the VirtualBox.xml file and removed these lines but it didn't help:

Code: Select all

<MachineRegistry>
      <MachineEntry uuid="{84b00527-cff5-4c49-9151-38e7c05d85dd}" src="/users/me/VirtualBox VMs/DevBox/DevBox.vbox"/>
</MachineRegistry>
Any ideas on just getting rid of VirtualBox completely and starting fresh? I even used CleanMyMac and the guest still shows up when I reinstall VirtualBox.
hibakushamoto
Posts: 10
Joined: 18. Dec 2013, 08:00

Re: Inaccessible VM

Post by hibakushamoto »

** SOLVED **

I opened up /Users/me/VirtualBox and removed the <MachineRegistry> XML block from three files:

VirtualBox.xml
VirtualBox.xml-prev
VirtualBox-1.12-macosx.xml

I am not sure which one did it but the damn guest is gone, finally.
Post Reply