No matching key sequence on Ubuntu 8.04

[Neon612]

I just had it open last night and everything worked fine. Then I try to open it this afternoon and bam, Error.


Could not load the settings file '/home/darin/.VirtualBox/Machines/Windows XP/Windows XP.xml'.
Element '{http://www.innotek.de/VirtualBox-settings}Machine': No match found for key-sequence ['{0f75a7b2-ddf1-498e-a1cb-e063efec2912}'] of keyref '{http://www.innotek.de/VirtualBox-settin ... ntSnapshot'.


Result Code:
VBOX_E_XML_ERROR (0x80BB000A)
Component:
VirtualBox
Interface:
IVirtualBox {339abca2-f47a-4302-87f5-7bc324e6bbde}


I've been able to pickup a bit about what the problem is, but I can't figure out how to fix it. The problem seems to be the Snapshot {0f75a7b2...} cannot be found, and after a look through the snapshot folder I can see that the file in question is NOT there. But there is a .vdi file and a .sav file. Correct me if I'm wrong, but isn't the .sav file the Snapshot? So will it work to replace the missing hex string with the .sav file?

Thank you.

[Sasquatch]

You have to check the XML file contents and compare it with the files in the snapshots folder. See if the file you see on your hard drive is noted in the XMl file or not, and if it's not, but another one is noted, you can try to replace it with the one on the hard drive. Do make a backup of the files before changing things, as you might corrupt the whole VM.

[Neon612]

Thanks for the quick reply.

I just tried replacing the first hex code with the hex code of the .sav file. Nothing happened, well, except for the same error.

Could not load the settings file '/home/darin/.VirtualBox/Machines/Windows XP/Windows XP.xml'.
Element '{http://www.innotek.de/VirtualBox-settings}Machine': No match found for key-sequence ['{3212ccea-6e34-48ff-94f0-dc36d677b1c5}'] of keyref '{http://www.innotek.de/VirtualBox-settin ... ntSnapshot'.


Result Code:
VBOX_E_XML_ERROR (0x80BB000A)
Component:
VirtualBox
Interface:
IVirtualBox {339abca2-f47a-4302-87f5-7bc324e6bbde}

Should I just delete the xml file and let VB make a new one that should, hopefully, work? Or is there something else I can do that may save the snapshot? Since, when I shut down the Virtual machine I tell it to save the current process, and I'd like to try and keep what i was working on.

[Sasquatch]

Well, we're working with Windows here, so creating a new config for it might cause strange behaviour like BSODs and reactivation. Why don't you attach the xml file here (rename it to .txt, else it won't get accepted), and hopefully someone sees the problem. In the mean time, create a new VM config (so create a second VM) and compare the base tags etc. to the other VM.

[Neon612]

Here is the xml file you asked for.