virtual machine inaccessible

[ASoubra]

Hi Guys,

My VirtualBox was working fine until recently when I started getting the error message below. I've attached the windows XP 2.xml file.

Please advise!

Kind Regards,

Adam

Premature end of data in tag VirtualBox line 2.
Location: '/Users/bnbn6k/Library/VirtualBox/Machines/WIndows XP 2/WIndows XP 2.xml', line 198 (2), column 29.
/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}

[rpmurray]

Did you recently update VB to a newer version?

It looks like a good chunk of the bottom of the file is missing. When you go to the folder where you found the Windows XP 2.xml, do you see another file that might look like:

Windows XP 2.xml.1.3-macosx.bak

Maybe not exactly the same as above (it might have something other than the 1.3), but with the the .bak extension? That would be a backup of the previous version of the xml file that VB creates when you update. You could try renaming it to Windows XP 2.xml and replacing the original Windows XP 2.xml file. VB should see it and update it again when you power on the VM, hopefully correctly this time.

I'd make a complete backup of the VirtualBox folder before doing that, just in case it doesn't work and you need to restore.

[ASoubra]

Hey thanks for the quick reply!

I couldn't find a .bak file.

Is there anything else i can try?

Also do you know what the "windows key" is on a mac keyboard?

Thanks,

Adam

[ASoubra]

I fixed the problem by replacing the corrupt windows XP 2.xml file with another .xml file form a new install. Now windows is asking to be re-activated... Any ideas why?

Cheers

[rpmurray]

It's because you replaced the .xml with one from a new install. The .xml file contains the settings for your windows VM (which contains data about the hardware it is emulating). If Windows sees any differences in what it thinks is the hardware then it will assume you've installed on different hardware and require re-activation. The .bak file would have contained your original settings, so you wouldn't have gotten this message. You might be able to get around it if you made the settings in VB the same as when you originally created the VM called Windows XP 2.

If you mean the "windows key" on the keyboard with the Windows logo, it's probably whichever Command key (the one with the cloverleaf symbol on it) you're not using as the Host key. If you mean the windows activation key, it will be the same as the one you used when you originally installed Windows XP.

[MarkCranness]

The value likely triggering reactivation is the virtual network card MAC. Try using the same value as the old VM had:

Code: Select all

0800273293D3

... Settings>Network>Adapter 1>Advanced>MAC Address.
But it might be too late, unless you have a backup of the machine VDI or a snapshot to Restore to.