Page 1 of 1
3.1.2 Bug
Posted: 15. Jan 2010, 19:14
by AndrewMc
I recently installed the latest update. The first time I installed and tried to reopen it said the program (VirtualBox) is corrupted, so I reinstalled. After doing so I can now no longer access my WinXP VM . The VirtualBox platform says that "the virtual machine is inaccessible" and gives the following message:
Start tag expected, '<' not found.
Location: '/Users/andrewmcswain/Library/VirtualBox/Machines/Quest/Quest.xml', line 1 (0), column 1.
/Users/vbox/tinderbox/3.1-mac-rel/src/VBox/Main/MachineImpl.cpp[5821] (nsresult Machine::loadSettings(bool)).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {2158464a-f706-414b-a8c4-fb589dfc6b62}
Is my VM fried? Can I fix this by reverting back to the old version? I use this to work, so as of right now I cannot. Please help.
Thanks,
Andrew
Re: 3.1.2 Bug
Posted: 15. Jan 2010, 20:34
by rpmurray
Your VM is not fried. It looks like the XML file that contains your VM settings has been mangled. Any way you could post the Quest.xml file so we could take a look at it?
Re: 3.1.2 Bug
Posted: 15. Jan 2010, 22:49
by AndrewMc
What program can i use to open it and post the material?
Re: 3.1.2 Bug
Posted: 16. Jan 2010, 02:44
by rpmurray
The XML file is just a text file, so any text editor, including TextEdit in the Applications folder, can open it.
When you paste it into the reply, place CODE tags around it, so it looks like so:
Re: 3.1.2 Bug
Posted: 17. Jan 2010, 01:28
by AndrewMc
I've already tried to open the .xml with TextEdit and Open Office as a regular text file. Text Edit tells me "the file could not be opened. the format is incorrect." Open Office gives me a 15 lines of nonsensensical character combinations.
Re: 3.1.2 Bug
Posted: 17. Jan 2010, 19:51
by rpmurray
I don't have that problem when I open the .xml file for my VM. Are you sure you tried opening the .xml and not the .vdi?
For example, the .xml for my Win 7 VM looks like so:
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<!-- Sun VirtualBox Machine Configuration -->
<VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.7-macosx">
<Machine uuid="{5d0b43fb-6f43-428f-9891-317a7f53a511}" name="Win 7" OSType="Windows7" lastStateChange="2010-01-12T19:48:47Z">
<ExtraData>
<ExtraDataItem name="GUI/SaveMountedAtRuntime" value="yes"/>
<ExtraDataItem name="GUI/LastWindowPostion" value="102,44,1400,1072"/>
<ExtraDataItem name="GUI/Fullscreen" value="off"/>
<ExtraDataItem name="GUI/Seamless" value="off"/>
<ExtraDataItem name="GUI/AutoresizeGuest" value="on"/>
</ExtraData>
<Hardware>
<CPU count="1">
<HardwareVirtEx enabled="false"/>
</CPU>
<Memory RAMSize="1024"/>
<Boot>
<Order position="1" device="Floppy"/>
<Order position="2" device="DVD"/>
<Order position="3" device="HardDisk"/>
</Boot>
<Display VRAMSize="32" monitorCount="1" accelerate3D="false"/>
<RemoteDisplay enabled="false" port="3389" authType="Null"/>
<BIOS>
<ACPI enabled="true"/>
<IOAPIC enabled="true"/>
<Logo fadeIn="true" fadeOut="true" displayTime="0"/>
<BootMenu mode="MessageAndMenu"/>
<TimeOffset value="0"/>
<PXEDebug enabled="false"/>
</BIOS>
<DVDDrive passthrough="false">
<Image uuid="{6f1484fd-b6ca-45ed-b7ea-4bea9bf2ad57}"/>
</DVDDrive>
<FloppyDrive enabled="true"/>
<USBController enabled="true" enabledEhci="true"/>
<Network>
<Adapter slot="0" enabled="true" MACAddress="08002723FDB3" cable="true" speed="0" type="82545EM">
<NAT/>
</Adapter>
<Adapter slot="1" enabled="true" MACAddress="0800273DF498" cable="true" speed="0" type="82545EM">
<NAT/>
</Adapter>
<Adapter slot="2" enabled="false" MACAddress="0800272D0272" cable="true" speed="0" type="82540EM"/>
<Adapter slot="3" enabled="false" MACAddress="08002781212F" cable="true" speed="0" type="82540EM"/>
<Adapter slot="4" enabled="false" MACAddress="080027774534" cable="true" speed="0" type="82540EM"/>
<Adapter slot="5" enabled="false" MACAddress="080027F7E0F3" cable="true" speed="0" type="82540EM"/>
<Adapter slot="6" enabled="false" MACAddress="080027B598E5" cable="true" speed="0" type="82540EM"/>
<Adapter slot="7" enabled="false" MACAddress="08002738A0BA" cable="true" speed="0" type="82540EM"/>
</Network>
<UART>
<Port slot="0" enabled="false" IOBase="0x3f8" IRQ="4" hostMode="Disconnected"/>
<Port slot="1" enabled="false" IOBase="0x3f8" IRQ="4" hostMode="Disconnected"/>
</UART>
<LPT>
<Port slot="0" enabled="false" IOBase="0x378" IRQ="4"/>
<Port slot="1" enabled="false" IOBase="0x378" IRQ="4"/>
</LPT>
<AudioAdapter controller="AC97" driver="CoreAudio" enabled="true"/>
<SharedFolders/>
<Clipboard mode="Bidirectional"/>
<Guest memoryBalloonSize="0" statisticsUpdateInterval="0"/>
<GuestProperties>
<GuestProperty name="/VirtualBox/GuestInfo/OS/Product" value="Windows 7" timestamp="1263324678671096000" flags=""/>
<GuestProperty name="/VirtualBox/GuestInfo/OS/Release" value="6.1.7600" timestamp="1263324678675272000" flags=""/>
<GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxControl.exe" value="2.2.4r47978" timestamp="1263324678784953000" flags=""/>
<GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxHook.dll" value="2.2.4r47978" timestamp="1263324678792094000" flags=""/>
<GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxDisp.dll" value="2.2.4r47978" timestamp="1263324678796966000" flags=""/>
<GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxMRXNP.dll" value="2.2.4r47978" timestamp="1263324678807207000" flags=""/>
<GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxService.exe" value="2.2.4r47978" timestamp="1263324678861274000" flags=""/>
<GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxTray.exe" value="2.2.4r47978" timestamp="1263324678870281000" flags=""/>
<GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxGuest.sys" value="2.2.4r47978" timestamp="1263324678875834000" flags=""/>
<GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxMouse.sys" value="2.2.4r47978" timestamp="1263324678879003000" flags=""/>
<GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxSF.sys" value="2.2.4r47978" timestamp="1263324678883459000" flags=""/>
<GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxVideo.sys" value="2.2.4r47978" timestamp="1263324678891618000" flags=""/>
<GuestProperty name="/VirtualBox/GuestInfo/OS/LoggedInUsers" value="0" timestamp="1263325724831850000" flags=""/>
<GuestProperty name="/VirtualBox/GuestInfo/OS/NoLoggedInUsers" value="true" timestamp="1263325724878016000" flags=""/>
<GuestProperty name="/VirtualBox/HostInfo/GUI/LanguageID" value="C" timestamp="1263324253401303000" flags=""/>
<GuestProperty name="/VirtualBox/GuestInfo/Net/Count" value="0" timestamp="1263325725156017000" flags=""/>
</GuestProperties>
</Hardware>
<StorageControllers>
<StorageController name="IDE" type="PIIX4" PortCount="2"/>
<StorageController name="SATA" type="AHCI" PortCount="1" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
<AttachedDevice type="HardDisk" port="0" device="0">
<Image uuid="{2ae31d69-4c56-4a76-a2fd-dd8ff52b76f2}"/>
</AttachedDevice>
</StorageController>
</StorageControllers>
</Machine>
</VirtualBox>
My guess is that the error you originally got indicates that one or more of the lines that make up this file are missing or mangled.
You could try creating a new VM (with a different name), with the EXACT SAME SETTINGS (this is important) as the one you're trying to get working, and then in the Storage Settings, attach the Quest.vdi to the IDE or SATA controller (depending on your settings).
But before doing any of that I would backup the entire VirtualBox folder in the Library folder that contains your VirtualBox setup, settings and hard disks, just in case things go wrong.
Re: 3.1.2 Bug
Posted: 19. Jan 2010, 21:16
by AndrewMc
Ok, I got the code. Let me know if you see anything strange.
Code: Select all
<?xml version="1.0"?>
<VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.7-macosx">
<Global>
<ExtraData>
<ExtraDataItem name="GUI/LastVMSelected" value="38eeefd0-bdfe-406b-aae2-b6ad13ff4c5a"/>
<ExtraDataItem name="GUI/LastWindowPostion" value="735,140,770,550"/>
<ExtraDataItem name="GUI/RegistrationData" value="triesLeft=0"/>
<ExtraDataItem name="GUI/SUNOnlineData" value="triesLeft=0"/>
<ExtraDataItem name="GUI/SuppressMessages" value=",confirmInputCapture,remindAboutAutoCapture"/>
<ExtraDataItem name="GUI/UpdateCheckCount" value="127"/>
<ExtraDataItem name="GUI/UpdateDate" value="1 d, 2010-01-20, stable"/>
</ExtraData>
<MachineRegistry>
<MachineEntry uuid="{cb1c04cd-e2ae-4025-95d8-0ace069e81c4}" src="Machines/Win98/Win98.xml"/>
<MachineEntry uuid="{38eeefd0-bdfe-406b-aae2-b6ad13ff4c5a}" src="Machines/Quest/Quest.xml"/>
</MachineRegistry>
<MediaRegistry>
<HardDisks>
<HardDisk uuid="{c25d68a8-3c75-4265-aac1-5623c0aea8f2}" location="VDI/Win98.vdi" format="VDI" type="Normal"/>
<HardDisk uuid="{b8ea352d-7c03-44c3-90f0-c1d38f4d2ab4}" location="VDI/Win98.2.vdi" format="VDI" type="Normal"/>
<HardDisk uuid="{1f4601f4-a10c-4bb4-a39e-f99a8faa6dbf}" location="HardDisks/Quest.vdi" format="VDI" type="Normal"/>
</HardDisks>
<DVDImages>
<Image uuid="{3e9bd5b5-f5ca-4a63-a0b9-d8839629997e}" location="/Users/andrewmcswain/Documents/Azureus Downloads/Windows.XP.Pro.Performance.Edition.March.2009-TJ/xppe.iso"/>
</DVDImages>
<FloppyImages/>
</MediaRegistry>
<NetserviceRegistry>
<DHCPServers>
<DHCPServer networkName="HostInterfaceNetworking-vboxnet0" IPAddress="192.168.56.2" networkMask="255.255.255.0" lowerIP="192.168.56.3" upperIP="192.168.56.255" enabled="1"/>
</DHCPServers>
</NetserviceRegistry>
<SystemProperties defaultMachineFolder="Machines" defaultHardDiskFolder="HardDisks" defaultHardDiskFormat="VDI" remoteDisplayAuthLibrary="VRDPAuth" webServiceAuthLibrary="VRDPAuth" LogHistoryCount="3"/>
<USBDeviceFilters/>
</Global>
</VirtualBox>
Re: 3.1.2 Bug
Posted: 20. Jan 2010, 00:44
by rpmurray
The file you posted is the VirtualBox.xml file. It's not going to show us what we need.
The file that is causing the problem is the Quest.xml file. You should find it in the Machine subfolder in the same place you found the VirtualBox.xml file. There will be two folders inside the Machine folder, one will be called Win98 and the other Quest. Within the Quest folder will be the Quest.xml file.
The Quest.xml file will contain all the settings for your VM. If that file has been corrupted, then that would explain the error you're getting. Because you updated, there might also be a file that may look like:
Quest.xml.1.3-macosx.bak
That would be a backup that was created when you updated to the new version of VB and would contain your original settings. You could make a copy of it and rename it to Quest.xml and replace the damaged Quest.xml file. Then startup VB and see if it will allow you to start your VM.
But, you'll want to make a backup of the VirtualBox folder in the Library folder, so that on the off chance doing the above makes things worse, you could always restore to where you are now.
Re: 3.1.2 Bug
Posted: 20. Jan 2010, 03:05
by AndrewMc
Ya ok. I see why I couldn suddenly open an *xml file with TextEdit. The Quest.xml still isn't opening with textedit. I'll do what you said and replace the .xml with the backup after also backing up the current Quest.xml.
However, this doesn't help you much with understanding what went wrong. And I also have concerns about using an old version of the .xml . Won't I have to revert to the older version of VB in order to use the backup?
Thanks,
Andrew
Re: 3.1.2 Bug
Posted: 20. Jan 2010, 05:00
by rpmurray
My best guess is that sometime during the update something went wrong and mangled the Quest.xml file. Maybe a stray cosmic ray, an Act of God, gremlins, or Just One of Those Things. Who knows? All we really know is it's toast now.
I've never done this before, which is why I'm saying you should back up the whole VirtualBox folder, and not just the Quest.xml. That way if it doesn't work you can just restore the folder, with no harm done, otherwise you might hose the whole thing and be up the creek without a backup. The closest I've seen to what's causing your error was when another user lost some lines within the xml file and just had to do a simple cut and paste to replace them, but in that case they didn't lose the whole file.
I'm making the assumption that VirtualBox will re-update the file and then open your VM. As far as I've been able to tell from a cursory examination of the xml files on my own Mac, the developers don't seem to modify the file all that much, if at all, between updates. The big question is if anything happened to the Quest.vdi file during your update attempt. Assuming that it's still OK, it should just work once you power it on.
Re: 3.1.2 Bug
Posted: 20. Jan 2010, 20:42
by AndrewMc
I did as you said: I backed up the entire folder and replaced Quest.xml with my file Quest.xml.1-6.bak, and it worked [So Far]. I have successfully booted my VM and everything seems to be functioning. Thanks a ton!
Andrew