Extra content at the end of the document.
Location: '/home/mint/VirtualBox VMs/bleble/general.vbox', line 21965 (0), column 61.
/home/vbox/vbox-4.3.6/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}
What Was happend? How can i repair this?
Plis help me.
Extra content at the end of the document.
Extra content at the end of the document.
Last edited by dziobak on 7. Feb 2014, 01:10, edited 1 time in total.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Extra content at the end of the document.
It would be nice to have the precise error message, but errors of that kind usually mean that the .vbox file is corrupted. The cure is to delete it and rename the backup ".vbox-prev" file to ".vbox".
Re: Extra content at the end of the document.
"The selected virtual machine is inaccessible. Please inspect the error message shown below and press the refresh button. If You want repeat the accessebility check. "
The backup was done automaticly? When I change ".vbox-prev" file to ".vbox" i have the same problem.
When i try open .vbox manulay i have this information:
Failed to open virtual machine located in /home/mint/VirtualBox VMs/bleble/general.vbox.
Extra content at the end of the document.
Location: '/home/mint/VirtualBox VMs/bleble/general.vbox', line 21965 (0), column 61.
/home/vbox/vbox-4.3.6/src/VBox/Main/src-server/MachineImpl.cpp[472] (nsresult Machine::initFromSettings(VirtualBox*, const com::Utf8Str&, const com::Guid*)).
Detail:
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Callee:
IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
(
The backup was done automaticly? When I change ".vbox-prev" file to ".vbox" i have the same problem.
When i try open .vbox manulay i have this information:
Failed to open virtual machine located in /home/mint/VirtualBox VMs/bleble/general.vbox.
Extra content at the end of the document.
Location: '/home/mint/VirtualBox VMs/bleble/general.vbox', line 21965 (0), column 61.
/home/vbox/vbox-4.3.6/src/VBox/Main/src-server/MachineImpl.cpp[472] (nsresult Machine::initFromSettings(VirtualBox*, const com::Utf8Str&, const com::Guid*)).
Detail:
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Callee:
IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
(
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Extra content at the end of the document.
Do you have your own backup of this folder?
Zip up any of these if they are present in the folder: *.vbox, *.vbox-tmp, *.vbox-prev, and post the zip here. While you're at it, include the VBox.log file from the "Logs" subfolder.
VirtualBox should not have propagated the corruption into the backup file - it has to be able to read a file before it can write a backup of it, which AFAIK it does at the end of the session, at the same time it closes the log file. If several files in this folder are corrupted then it would require a common cause external to VirtualBox.
Zip up any of these if they are present in the folder: *.vbox, *.vbox-tmp, *.vbox-prev, and post the zip here. While you're at it, include the VBox.log file from the "Logs" subfolder.
VirtualBox should not have propagated the corruption into the backup file - it has to be able to read a file before it can write a backup of it, which AFAIK it does at the end of the session, at the same time it closes the log file. If several files in this folder are corrupted then it would require a common cause external to VirtualBox.
Re: Extra content at the end of the document.
I had the same problem on my Ubuntu Desktop VM.
Events:
1. Restarted my host Win7 machine and selected save machine state for my VM.
2. I force quit everything (dumb!)
3. Upon power up my virtual machine failed with the error message you have.
Resolution:
1. Check to see if your vbox-prev file is any good, as already suggested.
2. Failing that, edit your vbox file and see what is missing. The .vbox file is the configuration file of your VM and follows a standard format.
As the error suggests, you should just be missing some stuff at the end. Mine had this as the last lines:
Which as you can tell is a a mess. This is xml, those characters on the final lines should not be there.
3. To resolve, I looked at a known good VM I have and replaced the final lines with what was there:
Boom, fixed.
Events:
1. Restarted my host Win7 machine and selected save machine state for my VM.
2. I force quit everything (dumb!)
3. Upon power up my virtual machine failed with the error message you have.
Resolution:
1. Check to see if your vbox-prev file is any good, as already suggested.
2. Failing that, edit your vbox file and see what is missing. The .vbox file is the configuration file of your VM and follows a standard format.
As the error suggests, you should just be missing some stuff at the end. Mine had this as the last lines:
Code: Select all
</AttachedDevice>
</StorageController>
</StorageControllers>
</Machine>
</ê¥+(Àº
/ õ!
3. To resolve, I looked at a known good VM I have and replaced the final lines with what was there:
Code: Select all
</AttachedDevice>
</StorageController>
</StorageControllers>
</Machine>
</VirtualBox>
Boom, fixed.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Extra content at the end of the document.
Well explained, thanks for contributing.