Now it works! Thanks a lot..

Restarting the boot- shell skript helped.

If you delete everything but the .vmkd file then not only will Fusion not recognize it as a Virtual Machine, Fusion will also not automatically rebuild the files you put in the trash! One would have to manually recreate the Virtual Machine and point it to an existing virtual hard drive if one was to follow your advise!

DO NOT Delete everything but the .vmdk file unless you understand what you're doing and what you will have to do to recover!

Okay if I do as you suggest, "Right click on the icon and open 'Show Package Contents', delete all files except *.vmdk file. Then restart VMware Fusion."...

1. The entry for Windows XP Professional was removed from the Virtual Machine Library window

2. When I doubled-clicked the Windows XP Professional Bundle Package Fusion gave me the following error message, "The document “Windows XP Professional” could not be opened."

3. There was no "The program will rebuild the guest OS system. Now it should run correct." action happening!

4. You do not know what you're talking about!

5. If you delete everything but the .vmdk file then not only will Fusion not recognize it as a Virtual Machine, Fusion will also not automatically rebuild the files you put in the trash! One would have to manually recreate the Virtual Machine and point it to an existing virtual hard drive if one was to follow your advise!

Don't take this the wrong way as I mean nothing personal by it... Your first post in this thread is dangerous in that not only is it totally absolutely incorrect it also is not the solution to fixing a Virtual Machine that was suspended during an upgrade. If you had deleted the .vmss file that would probably have fixed your problem and you would not have to have installed/unistalled/reinstalled the number of times you did.

Your explanation in your third post in this thread is not the same thing as you stated in your first post in this thread and the reason I'm being so adamant is the information you posted first is just plain wrong and can cause someone more problems then they had to begin with.

I'm just making sure that if someone that doesn't know any better then you comes along and tries to follow what you suggested as they will certainly have more issues to deal with if they do delete everything in the Virtual Machine's Bundle Package other then the virtual hard drive (.vmdk) file(s).

Bottom line is what you first posted is wrong and what you first and last said are not the same thing! Had you posted to this forum with your problem first I'm sure one of us would have told you to delete the .vmss file and you then should have then been able to start the once suspended Virtual Machine without any other issue and I for one would have suggested that before telling you to uninstall/reinstall first.

Anyway my advise to anyone reading this thread is please do not delete all files other then the .vmdk file from a Virtual Machines Bundle Package in an attempt to correct a "Failed to connect to peer process error". as it IS NOT to correct or proper solution to this issue.

If you have a suspended Virtual Machine that is having issues that cannot resolve on it own then delete the .vmss file first. Note: Deleting this file is like pulling the plug from the wall on a physical system and anything that was not saved to disk prior to suspending will be lost.

Below is the text of *.vmx. It looks like a setting script.

---

config.version = "8"
virtualHW.version = "6"
scsi0.present = "TRUE"
memsize = "512"
MemAllowAutoScaleDown = "FALSE"
ide0:0.present = "TRUE"
ide0:0.fileName = "/Users/alex/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmdk"
ide1:0.present = "TRUE"
ide1:0.autodetect = "TRUE"
ide1:0.deviceType = "cdrom-raw"
floppy0.present = "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"
isolation.tools.hgfs.disable = "FALSE"
displayName = "Windows XP Pro"
guestOS = "winxppro"
nvram = "Windows XP Pro.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "hosted"
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 c6 3a 9c bf ef 1f-4a 8d 7d a4 e2 76 c4 30"
uuid.bios = "56 4d c6 3a 9c bf ef 1f-4a 8d 7d a4 e2 76 c4 30"
ide0:0.redo = ""
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:76:c4:30"
ethernet0.generatedAddressOffset = "0"
tools.syncTime = "FALSE"

ide1:0.startConnected = "TRUE"

chipset.useAcpiBattery = "TRUE"
chipset.useApmBattery = "TRUE"

extendedConfigFile = "Windows XP Pro.vmxf"

Well, in my way I've let my dead Virtual Machine relive. If you think this is a wrong way please ignore my suggestion.

(MacBook, Leopard 10.5.2)

Try restarting the mac after migrating from one mac to a new one. I used migration assistant which moved everything flawlessly. Without restarting the mac, I received this error. After a restart, no problem.