Vm crashed - line 63 syntax error

[theflin56]

I have read some of the line 63 syntax error post, but do not see how to fix this error. This is the second time my VM has crashed with this error. The first I just simple created a new VM. I would rather recover this one if possible due to the data that is on it. Any recommendations? Thanks in advance.

Tom

[RDPetruska]

Well, it might be helpful to us if you'd actually post what is ON line 63 of your vmx file, so that somebody could recommend what to change! Even better - post your entire vmx file (it's only a couple of kb of text).

[theflin56]

Here is the vmx file, sorry for not putting that in the original post.

Thank you

[RDPetruska]

Hmm... looks like somehow the file has gotten corrupted, as it cuts off at line 63 in the middle of a line for the CD-ROM drive. I'd say you can safely delete the last 2 lines, if you weren't using that ISO image in your VM at the time. Not sure if there's any other info missing. If you look through your "vmware.log" files in the folder with that VM, the contents of the vmx file are contained within the log itself, so it CAN be recovered. Search the forum here for vmxRecover.pl to download a Perl script by Eric Tung.

[theflin56]

RDPetruska,

Thank you for your assistance. I removed the last 2 lines as you recommended. After saving the .vmx file, I was able to start the machine. I had to reload VM Tools, but it is working fine.

Thanks again for your assistance.

[CrazyVM]

you need to update your .vmx file

Go to Last line in .vmx file and remove the followings

"/Library/Application Support/VMware Fus

Save the .vmx file and power on the VM

[dniles]

My VM also showed line 63 synytax error. Can someone take a look at my file and tell me how to fix it?

[oreeh]

Delete the last line (guiExitOnC).

[dniles]

I'm speechless. Thanks so much. I thought I was going to lose everything I had on VM.

[WoodyZ]

You can do as oreeh suggested however you may also what to have a look in the vmware*.log files and make sure that you're only missing that last line.

Also you can use the vmxRecover.pl script from and the vmware*.log file from within the target Virtual Machine's Package to create a new .vmx configuration file.

Reference Thread:

[dniles]

Will do. Thanks again.

[ilr]

i'm having the same problem. The worse is that i was doing some work to this friday on vm . I'm sacred as hell of loosing this files. What should i do??

[ilr]

heres the logs

[ilr]

config.version = "8"

virtualHW.version = "6"

scsi0.present = "TRUE"

memsize = "512"

MemAllowAutoScaleDown = "FALSE"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Windows XP Professional.vmdk"

ide1:0.present = "TRUE"

ide1:0.autodetect = "TRUE"

ide1:0.deviceType = "cdrom-raw"

floppy0.fileType = "file"

floppy0.fileName = ""

floppy0.clientDevice = "FALSE"

ethernet0.present = "TRUE"

ethernet0.connectionType = "nat"

ethernet0.wakeOnPcktRcv = "FALSE"

usb.present = "TRUE"

ehci.present = "TRUE"

sound.present = "TRUE"

sound.fileName = "-1"

sound.autodetect = "TRUE"

pciBridge0.present = "TRUE"

buslogic.noDriver = "FALSE"

displayName = "Windows XP Professional"

guestOS = "winxppro"

nvram = "Windows XP Professional.nvram"

deploymentPlatform = "windows"

virtualHW.productCompatibility = "hosted"

sharedFolder0.present = "TRUE"

sharedFolder0.enabled = "TRUE"

sharedFolder0.readAccess = "TRUE"

sharedFolder0.writeAccess = "TRUE"

sharedFolder0.hostPath = "/Users/italo"

sharedFolder0.guestName = "italo On My Mac"

sharedFolder0.expiration = "never"

sharedFolder.maxNum = "1"

RemoteDisplay.vnc.port = "0"

tools.upgrade.policy = "upgradeAtPowerCycle"

powerType.powerOff = "soft"

powerType.powerOn = "soft"

powerType.suspend = "soft"

powerType.reset = "soft"

ethernet0.addressType = "generated"

uuid.location = "56 4d 97 89 a8 d5 88 cc-22 25 47 f1 a3 2c fd ea"

uuid.bios = "56 4d 97 89 a8 d5 88 cc-22 25 47 f1 a3 2c fd ea"

scsi0:0.redo = ""

checkpoint.vmState = "Windows XP Professional.vmss"

vmotion.checkpointFBSize = "16777216"

checkpointFBSize = "16777216"

pciBridge0.pciSlotNumber = "17"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "32"

sound.pciSlotNumber = "33"

ehci.pciSlotNumber = "34"

ethernet0.generatedAddress = "00:0c:29:2c:fd:ea"

ethernet0.generatedAddressOffset = "0"

ide1:0.startConnected = "TRUE"

floppy0.startConnected = "FALSE"

floppy0.present = "FALSE"

tools.syncTime = "FALSE"

ide1

[RDPetruska]

Just follow what others have posted in this thread... run the vmRecover perl script against one of the log files in your VM's folder to re-create the vmx file based on the information contained in the log file.

[WoodyZ]

You can just remove the "ide1" at the end of the file or as you can do as Robert () suggested use the vmxRecover.pl script from and the vmware*.log file from within the target Virtual Machine's Package to create a new .vmx configuration file.

Reference Thread:

[ilr]

How do i run this file?

Sorry, but i dont understand much of this stuff!

[ilr]

Thank you!!!!

I'm glad that ill be able to finish my work and get paid tsi month. lol

[RDPetruska]

Thank you!!!!

I'm glad that ill be able to finish my work and get paid tsi month. lol

Not sure if you're being sarcastic here or not, but...

If my income depended on me being able to run certain applications, etc., then I sure as heck would not be:

1. Running critical apps ONLY in a virtual environment.

2. NOT making certain that I had several good backups of my computers, virtual OR physical.

To answer your question about how you run the utility:

It is a Perl script. You need to install a Perl runtime interpreter so that you can run the script. Once you have that, if you run the script at a command prompt/terminal with no parameters, it will display a help telling you exactly what you need to type to run it.

[WoodyZ]

To answer your question about how you run the utility:

It is a Perl script. You need to install a Perl runtime interpreter so that you can run the script. Once you have that, if you run the script at a command prompt/terminal with no parameters, it will display a help telling you exactly what you need to type to run it.

This is VMware Fusion which of course runs on Mac OS X 10.4.11 or later and Perl does not need to be installed since it's already there by default in OS X.

In a Terminal (/Applications/Utilities/Terminal) type the following command and if Perl is installed (which is should be under OS X) it will report the version.

perl -v

If it doesn't it would say...

-bash perl: command not found

If you put the vmxRecover.pl script inside the Virtual Machine Package and then change to its location in a Terminal and lets say the existing .vmx file was named ".Windows XP Home.vmx" then the Terminal command would be as follows...

./vmxRecover.pl vmware.log > "Windows XP Home.vmx"

Note: Be sure to have Fusion closed when you do this.