My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
-
computermaniac
- Posts: 10
- Joined: 20. May 2016, 19:57
My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
Hi, people. I tried to ask this on Ask Ubuntu and Ubuntu Forums and nobody seems to answer and solve this problem. So, I'm going to tell here the problem.
I was trying to start up my VM, when suddenly I closed VirtualBox and opened it, it appeared this:
The selected virtual machine is inaccessible. Please inspect the error message shown below and press the Refresh button if you want to repeat the accessibility check:
Runtime error opening
'/scra/home/davidbmelo/VirtualBox/VDI/Windows XP/Windows XP.vbox' for reading: -102 (File not found.).
/build/virtualbox-FD2cpk/virtualbox-4.1.44-dfsg/src/VBox/Main/src-server/MachineImpl.cpp[708] (nsresult Machine::registeredInit()).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: VirtualBox
Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}
Can someone tell me how do I fix this problem please?
BTW, the version I'm using on VirtualBox is 4.1.44 and my Linux Guest is Ubuntu 12.04.
I was trying to start up my VM, when suddenly I closed VirtualBox and opened it, it appeared this:
The selected virtual machine is inaccessible. Please inspect the error message shown below and press the Refresh button if you want to repeat the accessibility check:
Runtime error opening
'/scra/home/davidbmelo/VirtualBox/VDI/Windows XP/Windows XP.vbox' for reading: -102 (File not found.).
/build/virtualbox-FD2cpk/virtualbox-4.1.44-dfsg/src/VBox/Main/src-server/MachineImpl.cpp[708] (nsresult Machine::registeredInit()).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: VirtualBox
Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}
Can someone tell me how do I fix this problem please?
BTW, the version I'm using on VirtualBox is 4.1.44 and my Linux Guest is Ubuntu 12.04.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
Look in the folder that has the guest and see if the *.vbox file has content. If it is 0 or missing then reneame the *.vbox-prev to *.vbox and see if that will allow the guest to start.
-
computermaniac
- Posts: 10
- Joined: 20. May 2016, 19:57
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
Perryg wrote:Look in the folder that has the guest and see if the *.vbox file has content. If it is 0 or missing then reneame the *.vbox-prev to *.vbox and see if that will allow the guest to start.
Already tried it.
Premature end of data in tag VirtualBox line 8.
Location: '/scra/home/davidbmelo/VirtualBox/VDI/Windows XP/Windows XP.vbox', line 77 (8), column 1.
/build/virtualbox-FD2cpk/virtualbox-4.1.44-dfsg/src/VBox/Main/src-server/MachineImpl.cpp[708] (nsresult Machine::registeredInit()).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: VirtualBox
Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
Well that is not the same error. Post the *.vbox-prev and *.vbox.tmp if it exists. Compress the files so they will be allowed as attachments here.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
Also post the guests log file ( as an attachment ) that has content.
-
computermaniac
- Posts: 10
- Joined: 20. May 2016, 19:57
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
Is this OK? And does *.vbox~ count as *vbox-temp?
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
Both of these files are corrupt. Look in that directory and post what is shown, take a screenshot if you need too.
-
computermaniac
- Posts: 10
- Joined: 20. May 2016, 19:57
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
OK. Here's what is written in *.vbox-prev file:Perryg wrote:Both of these files are corrupt. Look in that directory and post what is shown, take a screenshot if you need too.
Code: Select all
<?xml version="1.0"?>
<!--
** DO NOT EDIT THIS FILE.
** If you make changes to this file while any VirtualBox related application
** is running, your changes will be overwritten later, without taking effect.
** Use VBoxManage or the VirtualBox Manager GUI to make changes.
-->
<VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.12-linux">
<Machine uuid="{97ea430a-aa82-471a-8a2a-a47e06e2894d}" name="Windows XP" OSType="WindowsXP" snapshotFolder="Snapshots" lastStateChange="2016-05-15T23:03:45Z">
<MediaRegistry>
<HardDisks>
<HardDisk uuid="{869ef264-1ba0-4e89-a6eb-c87feffe5e5b}" location="/scra/home/davidbmelo/.VirtualBox/HardDisks/Windows XP.vdi" format="VDI" type="Normal">
<HardDisk uuid="{4ff73cc0-d71b-465e-ab1c-fbf642b11704}" location="/scra/home/davidbmelo/.VirtualBox/Machines/Windows_XP/Snapshots/{4ff73cc0-d71b-465e-ab1c-fbf642b11704}.vdi" format="VDI"/>
<HardDisk uuid="{11de891a-6ce0-4e7e-b5e3-d1b6cb995006}" location="Snapshots/{11de891a-6ce0-4e7e-b5e3-d1b6cb995006}.vdi" format="VDI"/>
</HardDisk>
<HardDisk uuid="{9a9d14a3-e3dd-4452-5c94-44e605144a3e}" location="/scra/home/davidbmelo/Área de Trabalho/Pasta Partilhada/nn/VDI/Windows_XP.vdi" format="VDI" type="Normal">
<HardDisk uuid="{c1122e70-e8a9-46e6-9041-d8eb15ec79f5}" location="/scra/home/davidbmelo/.VirtualBox/Machines/Windows_XP/Snapshots/{c1122e70-e8a9-46e6-9041-d8eb15ec79f5}.vdi" format="VDI"/>
<HardDisk uuid="{b0204c5a-c0da-4fc4-ba44-4f683527eacc}" location="Snapshots/{b0204c5a-c0da-4fc4-ba44-4f683527eacc}.vdi" format="VDI"/>
</HardDisk>
</HardDisks>
<DVDImages>
<Image uuid="{f8bdacc0-7052-4729-a099-2453f395b063}" location="/scra/home/davidbmelo/.VirtualBox/VBoxGuestAdditions_4.1.44.iso"/>
</DVDImages>
<FloppyImages/>
</MediaRegistry>
<ExtraData>
<ExtraDataItem name="GUI/LastCloseAction" value="powerOff"/>
<ExtraDataItem name="GUI/LastGuestSizeHint" value="1360,673"/>
<ExtraDataItem name="GUI/LastNormalWindowPosition" value="8,52,680,307,max"/>
</ExtraData>
<Hardware version="2">
<CPU count="1" hotplug="false">
<HardwareVirtEx enabled="true" exclusive="true"/>
<HardwareVirtExNestedPaging enabled="true"/>
<HardwareVirtExVPID enabled="true"/>
<PAE enabled="false"/>
<HardwareVirtExLargePages enabled="false"/>
<HardwareVirtForce enabled="false"/>
</CPU>
<Memory RAMSize="192" PageFusion="false"/>
<HID Pointing="PS2Mouse" Keyboard="PS2Keyboard"/>
<HPET enabled="false"/>
<Chipset type="PIIX3"/>
<Boot>
<Order position="1" device="Floppy"/>
<Order position="2" device="DVD"/>
<Order position="3" device="HardDisk"/>
<Order position="4" device="Network"/>
</Boot>
<Display VRAMSize="16" monitorCount="1" accelerate3D="false" accelerate2DVideo="false"/>
<RemoteDisplay enabled="false" authType="Null" authTimeout="5000"/>
<BIOS>
<ACPI enabled="true"/>
<IOAPIC enabled="false"/>
<Logo fadeIn="true" fadeOut="true" displayTime="0"/>
<BootMenu mode="MessageAndMenu"/>
<TimeOffset value="0"/>
<PXEDebug enabled="false"/>
</BIOS>
<USBController enabled="true" enabledEhci="true"/>
<Network>
<Adapter slot="0" enabled="true" MACAddress="08002709B4D5" cable="true" speed="0" type="Am79C973">
<DisabledModes/>
<NAT>
<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/>
<Alias logging="false" proxy-only="false" use-same-ports="false"/>
</NAT>
</Adapter>
<Adapter slot="1" enabled="false" MACAddress="080027E22DDE" cable="true" speed="0" type="Am79C973">
<DisabledModes>
<NAT>
<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/>
<Alias logging="false" proxy-only="false" use-same-ports="false"/>
</NAT>
</DisabledModes>
</Adapter>
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
You have already posted the *.vbox-prev. What I wanted to know is were there any other *.vbox files.
But I guess there is not. You can recover this but it is a little harder. It means removing the previous one and creating another with the same settings as before.
1) make a backup of the *.vdi file so you can not hurt it any more than it already is.
3) rename the folder that holds this guest by adding .old to the end of the folder name
4) create a new guest and when asked to create or use an existing guest select do not add a virtual hard disk now.
5) Try to use as many of the previous settings as you can remember from the step in 1a above.
6) copy the saved *.vdi file to the base folder of the newly created guest.
7) go into the settings under the storage section ( IDE for XP ) and add the disk back in.
8 ) see if it starts and operates.
But I guess there is not. You can recover this but it is a little harder. It means removing the previous one and creating another with the same settings as before.
1) make a backup of the *.vdi file so you can not hurt it any more than it already is.
- 1a) look at the settings of the guest as it is now and record that information because you will need it later.
3) rename the folder that holds this guest by adding .old to the end of the folder name
4) create a new guest and when asked to create or use an existing guest select do not add a virtual hard disk now.
5) Try to use as many of the previous settings as you can remember from the step in 1a above.
6) copy the saved *.vdi file to the base folder of the newly created guest.
7) go into the settings under the storage section ( IDE for XP ) and add the disk back in.
8 ) see if it starts and operates.
-
computermaniac
- Posts: 10
- Joined: 20. May 2016, 19:57
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
1) How do I make a backup of the *.vdi? Should I do it in a terminal?Perryg wrote:You have already posted the *.vbox-prev. What I wanted to know is were there any other *.vbox files.
But I guess there is not. You can recover this but it is a little harder. It means removing the previous one and creating another with the same settings as before.
1) make a backup of the *.vdi file so you can not hurt it any more than it already is.2) remove the guest from the media manager and select to not delete anything.
- 1a) look at the settings of the guest as it is now and record that information because you will need it later.
3) rename the folder that holds this guest by adding .old to the end of the folder name
4) create a new guest and when asked to create or use an existing guest select do not add a virtual hard disk now.
5) Try to use as many of the previous settings as you can remember from the step in 1a above.
6) copy the saved *.vdi file to the base folder of the newly created guest.
7) go into the settings under the storage section ( IDE for XP ) and add the disk back in.
8 ) see if it starts and operates.
- 1a) How do I know the settings of my guest?
4) Maybe, I know how to do it.
5) Same question as in 1a)
6) Same as 4).
7) How do I go into the settings under the storage section?
8 ) I'll check that if all the previous questions are answered.
-
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: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
1) How do I make a backup of the *.vdi
Just make a copy using whatever tool suits you best.
2) How do I know the settings of my guest?
Look at the .vbox files you posted. The files are corrupt so you can't get everything, but you can get a lot.
3) Where do I find the fold that holds this guest?
You already copied the vbox files from that folder, so you already know this.
Just make a copy using whatever tool suits you best.
2) How do I know the settings of my guest?
Look at the .vbox files you posted. The files are corrupt so you can't get everything, but you can get a lot.
3) Where do I find the fold that holds this guest?
You already copied the vbox files from that folder, so you already know this.
-
computermaniac
- Posts: 10
- Joined: 20. May 2016, 19:57
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
If I do this in a terminal, how do I do it?mpack wrote:1) How do I make a backup of the *.vdi
Just make a copy using whatever tool suits you best.
-
computermaniac
- Posts: 10
- Joined: 20. May 2016, 19:57
Re: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
What if I manually copy? Does that work?
-
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: My VM is inaccessible. Runtime error opening NS_ERROR_FAILURE (0x80004005)
By definition, anything that makes a copy works. I don't know where you got the idea that something complex was needed.
A vdi is a host file. It's a bit large, but otherwise nothing special. It can be copied like any other host file.
A vdi is a host file. It's a bit large, but otherwise nothing special. It can be copied like any other host file.