HELP:Error while opening the virtual machine:XXXXXX is not a valid virtual machine configuration file

[hahafx]

I've been using vmware player(Version 2.0.3) very happily for a long time now to run a winXP Pro,but I got the following message this day when I runing it.

Error while opening the virtual machine:

"S:\OFFICE2003\WXP\Win XP Pro.vmx" is not a valid virtual machine configuration file.

Can somebody help please !!

Thanks a lot!

Best,

Hahafx

2009.12.07

[wila]

Hi,

It looks like your .vmx file got corrupted somehow.

Good that you attached the vmware*,log files, i've reconstructed the vmx file from the vmware-0.log file using the vmxRecover.pl script.

The script to do so yourself can be found here: http://www.vi-toolkit.com/wiki/index.php/Recover_vmx_from_log_file

The result is attached.

Hope this helps,

--

Wil

_____________________________________________________

VI-Toolkit & scripts wiki at http://www.vi-toolkit.com

[continuum]

Hi Wil

I should read the full post before starting to work

Here is my reconstruction - with slightly different results following this procedure http://sanbarrow.com/vmdk/extracting-vmx-from-log.html

config.version ="8"
deploymentPlatform ="windows"
displayName ="Windows XP Professional"
ehci.pciSlotNumber ="34"
ehci.present ="TRUE"
ethernet0.addressType ="generated"
ethernet0.connectionType ="nat"
ethernet0.generatedAddress ="00:0c:29:64:68:52"
ethernet0.generatedAddressOffset ="0"
ethernet0.pciSlotNumber ="32""
ethernet0.present ="TRUE"
ethernet0.wakeOnPcktRcv ="FALSE"
extendedConfigFile ="Windows XP Professional.vmxf"
fileSearchPath ="H:\WXP;."
floppy0.present ="FALSE"
guestOS ="winxppro"
ide0:0.fileName ="Win XP Pro.vmdk"
ide0:0.present ="TRUE"
ide0:0.redo =""
ide0:1.present ="FALSE"
ide1:0.present ="FALSE"
memsize ="1028"
mks.keyboardFilter ="allow""
nvram ="Windows XP Professional.nvram"
pciBridge0.pciSlotNumber ="17"
pciBridge0.present ="TRUE"
scsi0.pciSlotNumber ="16""
scsi0.present ="TRUE"
sound.autodetect ="TRUE"
sound.fileName ="-1"
sound.pciSlotNumber ="33""
sound.present ="TRUE"
svga.autodetect ="TRUE"
tools.remindInstall ="FALSE"
tools.syncTime ="FALSE
tools.upgrade.policy ="useGlobal
usb.present ="TRUE
uuid.bios ="56 4d 66 f3 9e 38 bd cc-19 84 5e c1 e8 64 68 52"
uuid.location ="56 4d 66 f3 9e 38 bd cc-19 84 5e c1 e8 64 68 52"
virtualHW.productCompatibility ="hosted"
virtualHW.version ="6"

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[hahafx]

Dear Wil,

Thank you very very much!

I can run the virtual machine again .

Thank you !!!

Hahafx

[wila]

Hi Ulli,

Hehe, well i fall down that trap sometimes as well. I've looked at the differences between yours and mine. Out of curiosity, is there any reason why you reordered the statements? Is there any other difference I've missed in the comparing the two?

At Glad to hear the reconstructed vmx file solved your problem. Happy virtualising!

cheers,

--

Wil

_____________________________________________________

VI-Toolkit & scripts wiki at http://www.vi-toolkit.com

[continuum]

Hi Wil

I sort the orders alphabetically as this allows a quicker overview while checking for further syntax errors.

In Ultraedit there is a sort-function ...

I also deleted the encoding line as it will be recreated and I have never seen the value used here before




___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[wila]

Hi Ulli,

Ah .. didn't notice the alphabetic sorting, yes that makes sense.

I noticed that there was no exotic character currently used in the vmx config file, but leaving the encoding out (Chinese Kuozhan) may end up resulting in problems when would want to, for example, start using shared folders with a character out of the standard US character set, which is why you can better leave it in.

Internationalisation in software products is always a bit of a challenge

--

Wil

_____________________________________________________

VI-Toolkit & scripts wiki at http://www.vi-toolkit.com