VMware Communities: Message List - "Failed to connect to peer process"

Re: "Failed to connect to peer process"

vlakjetser — Fri, 17 Apr 2009 12:40:44 GMT

Great, this resolved the problem! Many thanks!

Re: "Failed to connect to peer process"

VivAna — Mon, 09 Feb 2009 21:55:18 GMT

Hello

I have solved this issue this way.

create a new machine.

just enter credentials without installation

open the paket and locate the *.vmx file

open your *.vmx file and take a look at the Hardwareversion third line (remember the number)

take a look at the same place in your own vm-session-file

replace the number in the *.vmx file withe that one generated in the first test file.

That resolved my problem

greetings

Re: "Failed to connect to peer process"

keitHkjtlHutchison — Sat, 07 Feb 2009 19:26:34 GMT

After backing up to a new machine I got the same error,

after reading of the above posts all I did was run from a terminal session

sudo /Library/Application Support/VMware Fusion/boot.sh --restart

problem solved

Many thanks

Keith

Re: "Failed to connect to peer process"

CMoote2 — Thu, 06 Nov 2008 13:21:42 GMT

Multiple VMware Fusion Versions are Installed

It is possible you may have 2 copies of VMware Fusion installed. I was trying to launch a newly created VM and running into the same problems as you all have been experiencing. I had 1.1.3 installed and then installed the 2.x upgrade for free and didn't realize that the old app launcher for 1.x was referenced by my doc and where I'd saved a copy under Utilities.

If you've installed 2.x as well check under the menu bar VMware Fusion > About VMware Fusion. If it shows any older version you'll need to close that app instance and find the newly installed app.

Another quick tell for version is by the Library's GUI. The the new one for 2.x has the VMs listed down the left side with a preview pane on the right. The OLD 1.x interface just has a window with list of VMs.

Once I started using the correct launcher everything is running fine.

Alternate Permission Repair (built-in OS & no need to boot from Mac Install DVD)

If you are unsure about permission on your disk you can even run the repair with out rebooting from the Mac OS. Simply launch the Disk Utility, select the HDD that you wish to check, ensure the "First Aid" tab is selected (Tab bar reads the following selectors: First Aid | Erase | RAID | Restore) and then click the button "verify disk permission" . Once that is finished you can choose the "Repair Disk Permissions" button if there were any issues found that might be the problem. (Note: you do not have to verify first and can skip straight to the repair as the button is not Grayed out.)

I hope either of these help. Good luck.

Re: "Failed to connect to peer process"

mcr2582 — Fri, 31 Oct 2008 15:05:04 GMT

All that was needed was to run the comand that was posted by MadarMS. I didn't reinstall anything...just add to add backslashes to the command.

sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restart

I got the log info below, then quit and reloaded VMware and it worked fine.

VMware Fusion 94249: Shutting down VMware Fusion:
No matching processes were found
No matching processes were found
No matching processes were found
No matching processes were found
kextunload: unload id com.vmware.kext.vmcrosstalk failed (result code 0xe00002c2)
kextunload: unload id com.vmware.kext.vmmon failed (result code 0xe00002c2)
kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmmon.kext failed
kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmci.kext failed
kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmioplug.kext failed
kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmnet.kext failed

VMware Fusion 94249: Starting VMware Fusion:
kextload: /Library/Application Support/VMware Fusion/kexts/vmmon.kext loaded successfully
kextload: /Library/Application Support/VMware Fusion/kexts/vmci.kext loaded successfully
kextload: /Library/Application Support/VMware Fusion/kexts/vmioplug.kext loaded successfully
kextload: /Library/Application Support/VMware Fusion/kexts/vmnet.kext loaded successfully
Internet Software Consortium DHCP Server 2.0
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

Configured subnet: 172.16.108.0
Setting vmnet-dhcp IP address: 172.16.108.254
Opened:
Recving on VNet/vmnet8/172.16.108.0
Sending on VNet/vmnet8/172.16.108.0
Internet Software Consortium DHCP Server 2.0
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

Configured subnet: 192.168.7.0
Setting vmnet-dhcp IP address: 192.168.7.254
Opened:
Recving on VNet/vmnet1/192.168.7.0
Sending on VNet/vmnet1/192.168.7.0

Re: "Failed to connect to peer process"

banderson_6@yahoo.com — Fri, 24 Oct 2008 15:05:24 GMT

All, I recently came accross the same issue and I ran this script that resolved it. I hope this helps.

http://communities.vmware.com/docs/DOC-8013

Re: "Failed to connect to peer process"

rjgentile — Tue, 27 May 2008 11:40:33 GMT

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.

Re: "Failed to connect to peer process"

WoodyZ — Wed, 30 Apr 2008 19:13:28 GMT

Creating a new Virtual Machine using the New Virtual Machine Assistant and pointing it to use an existing virtual hard disk (.vmdk) is not the same thing that you suggested in your first post in this thread and I fail to see that you just don't get it! (Maybe English isn't your first language and that would explain it.) Not only that one can use the New Virtual Machine Assistant and point it to use an existing virtual hard disk (.vmdk) without deleting the additional files in a different Virtual Machine Bundle Package and if the virtual disk is not corrupt it would also work. How you solved your issue has nothing to do with the problem that you posted your first reply to as that person had already stated "Restarting the boot- shell skript helped." which mean their issue was resolved.

Either way the suggestion you made in that first post is erroneous and has the potential to cause someone additional problems that they don't need any why you just don't get that is flabbergasting.

Re: "Failed to connect to peer process"

alexylee — Wed, 30 Apr 2008 18:25:31 GMT

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)

Re: "Failed to connect to peer process"

WoodyZ — Wed, 30 Apr 2008 18:10:28 GMT

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

Yes the .vmx files contains the Virtual Machine's settings. So what's your point? I fail to see any!

Re: "Failed to connect to peer process"

alexylee — Wed, 30 Apr 2008 17:54:11 GMT

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"

Re: "Failed to connect to peer process"

WoodyZ — Wed, 30 Apr 2008 17:07:41 GMT

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.

Re: "Failed to connect to peer process"

etung — Wed, 30 Apr 2008 17:41:16 GMT

Woody's right. Most files other than the .vmdk can be regenerated (such as the .nvram, .vmsd, . vmss, .log, etc.), but the conspicuous and important file that can't be is the .vmx file. You could create a new one by creating a new virtual machine and pointing it at the .vmdk file, but this isn't the same as automatically regenerating it. Maybe something strange is going on in your setup or I overlooked something in the code, but for anyone else reading this thread, please don't blindly delete files from the virtual machine bundle.

Re: "Failed to connect to peer process"

WoodyZ — Wed, 30 Apr 2008 15:39:10 GMT

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!

Re: "Failed to connect to peer process"

alexylee — Wed, 30 Apr 2008 16:04:49 GMT

Let me explain what is going on about my virtual machine. My virtual harddisk lies in the file "Windows XP Professional.vmwarevm" (say: Windows XP Professional icon) where the virtual harddrive (Windows XP Professional.vmdk lies). In my case I upgraded the new version of VMware Fusion while the virtual machine is still as suspend. So this make VMware Fusion didn't work anymore. As I uninstalled and reinstalled sever times as failure. Then I find this trick to remove the other files in this virtual machine.

I regenerated a new Windows machine and lied the machine in other folder (say: Windows XP Pro). Start the program and the system rebuilds it's necessary files in this "Windos XP Pro" icon (if you open the Package Contents). Done, just as good as before. What I removed now are in the new place.

Re: "Failed to connect to peer process"

alexylee — Wed, 30 Apr 2008 15:14:06 GMT

Believe me if you remove all the files but *.vmdk. The guest OS runs as well as the same. I've made a backup of these removed files first and now the new virtual machine has only one file, that is *.vmdk. In my case, I've Windows XP Professional as guest OS.

Re: "Failed to connect to peer process"

WoodyZ — Wed, 30 Apr 2008 14:06:34 GMT

alexylee wrote: And one more thing. If you keep the guest OS in suspend, this will also cause the problem.

To solve the problem, try to find the virtual machine harddisk icon. Right click on the icon and open 'Show Package Contents', delete all files except *.vmdk file. Then restart VMware Fusion. The program will rebuild the guest OS system. Now it should run correct.

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!

Re: "Failed to connect to peer process"

alexylee — Wed, 30 Apr 2008 11:44:06 GMT

And one more thing. If you keep the guest OS in suspend, this will also cause the problem.

Re: "Failed to connect to peer process"

siluro — Thu, 24 Apr 2008 12:46:24 GMT

Now it works! Thanks a lot..

Restarting the boot- shell skript helped.

Re: "Failed to connect to peer process"

MandarMS — Thu, 24 Apr 2008 11:54:28 GMT

Try Reinstalling Vmware Fusion

1) To uninstall following are the steps
a) Uninstall VMware Fusion (/Library/Application Support/VMware Fusion/Uninstall VMware Fusion)
b) Delete the following folder: /Library/Application Support/VMware Fusion
c) Delete following file: ~/Library/Preferences/com.vmware.fusion.plist
d) Delete the following folder: ~/Library/Preferences/VMware Fusion
2) Restart you system

If you have already Reinstalled Try restarting Boot.sh in Mac OS Terminal using following command

sudo /Library/Application Support/VMware Fusion/boot.sh --restart

Re: "Failed to connect to peer process"

siluro — Thu, 24 Apr 2008 11:46:04 GMT

I have the same Problem since the Update to 1.1.2...

Is there a posibility to restart the peer Process?

Re: "Failed to connect to peer process"

hdbaumeister — Mon, 21 Apr 2008 11:58:21 GMT

I had exactly the same issue after upgrading my 10.4.12 OS to Leopard.

A deinstall of VMWare and a subsequent reinstall (in both cases 1.1.1) fixed my problems!

No need to uninstall / redo anything to do with Leopard!

Re: "Failed to connect to peer process"

lawremp — Tue, 04 Mar 2008 06:30:28 GMT

Try deleting the contents of Library/Application Support/VMware Fusion/kexts then reinstall. That should do it.

Re: "Failed to connect to peer process"

mecase — Thu, 14 Feb 2008 22:05:49 GMT

Hi,

The first time I ran it on Leopard, VMWare Fusion failed the same way. After reading this discussion page I downloaded the latest VMWare Fusion (1.1.1 (72241)) and installed it. I have no idea if it overwrote the original but I assume so. The same serial number was shown to me after the install. It all works fine now.

Mike

Re: "Failed to connect to peer process"

tdefriez — Thu, 17 Jan 2008 13:53:14 GMT

Seems repairing the permission totally messes up a pile of permissions in the OS - so the only solution seems to be to re-install OS. I found some many wrong permissions that it was easier to just re-install - reminds me of a Windows issue back in WIndows 98. Still yet to check Apple site for this issue.

Re: "Failed to connect to peer process"

climber_rich — Thu, 17 Jan 2008 04:27:22 GMT

Seems like a lot of work to get fusion running....I'm hoping that there is a simpler solution.

Re: "Failed to connect to peer process"

tdefriez — Thu, 17 Jan 2008 04:11:23 GMT

Here's how I recovered it

Took Leopald install disk
Re-booted
Selected Archive and install (no choice due to pervious 10.5.1 update)
Re-booted
Check VMWare, it now runs using original virtual disk
Had error about preferences file ignored
Updated to 10.5.1
Now fixing preference

Seems an issue with TechTools Pro as several other programs would not run before I re-installed, they also now run

I wondered why using Disk Utilities failed in Leopald, Apple need to fix this - now to check Apple site for this issue.

Re: "Failed to connect to peer process"

climber_rich — Thu, 17 Jan 2008 03:44:03 GMT

Specifically, I am running a Macbook Pro Intel Core 2 duo that was upgraded to Leopard. Everyone was running fine and then one day I ran fusion and I got the failed to connect to peer process error. I am not running boot camp, but running windows xp in fusion. I then tried uninstalling and reinstalling according to the instructions posted in this forum, but I still can't run windows xp. I then tried uninstalling fusion, booting from a techtools protogo usb drive (leopard version), repairing permissions, reinstalling fusion, but I still get the error.

I really don't want to delete my windows installation and reinstall windows. Any help is greatly appreciated.

Re: "Failed to connect to peer process"

tdefriez — Thu, 17 Jan 2008 02:46:45 GMT

Can you be more specific? Did repair permissions cause the issue? Did you re-install both VMWare Fusion and Virtual Machine or which?

Re: "Failed to connect to peer process"

climber_rich — Wed, 16 Jan 2008 15:45:07 GMT

I didn't do that so I'm not sure why my Macbook Pro doesn't run fusion. I'm still searching for a solution.

Re: "Failed to connect to peer process"

grahamfw — Wed, 16 Jan 2008 13:21:24 GMT

I figured out what it was that caused my problem. Perhaps we are in the same boat.

I netbooted to a 10.4.x netboot set and repaired permissions. This effectually hosed the permissions therein, so no matter of uninstalling and reinstalling would fix this. I eventually had to do an archive and reinstall and all was well.

Re: "Failed to connect to peer process"

climber_rich — Tue, 15 Jan 2008 23:17:56 GMT

I'm still having the problem.

Anyone have any other suggestions?

Re: "Failed to connect to peer process"

climber_rich — Tue, 15 Jan 2008 22:44:23 GMT

Okay. I'm having the same problem. I followed MandarMS's instructions, but I still get the same error message. It appears that the problem is in my Virtual Machine, not the program.

I think that if I delete the Windows Machine and Create a new one, it should solve the problem.

Re: "Failed to connect to peer process"

MandarMS — Tue, 15 Jan 2008 12:16:45 GMT

not sure that you have deleted the following files after uninstallation of VMware Fusion

1) To uninstall following are the steps
a) Uninstall VMware Fusion (/Library/Application Support/VMware Fusion/Uninstall VMware Fusion)
b) Delete the following folder: /Library/Application Support/VMware Fusion
c) Delete following file: ~/Library/Preferences/com.vmware.fusion.plist
d) Delete the following folder: ~/Library/Preferences/VMware Fusion
2) Restart you system

"Failed to connect to peer process"

grahamfw — Mon, 14 Jan 2008 18:09:32 GMT

I've already seen the thread regarding this topic, but that does not work to fix my problem. I've:

1.) Completely uninstalled, rebooted, reinstalled from CD with 1.0 (with network cable disconnected, etc.) with no luck
2.) Completely uninstalled, rebooted, attempted to install from the newly downloaded Fusion 1.1 Build 62573, with no luck.

Nothing has worked and I'll be D@MNED if I have to purchase support to resolve this. It had been working flawlessly before.

I've also repaired permissions from the Leopard Disk that came with my computer. I'm also running the latest Leopard version 10.5.1.

Any suggestions? Thanks in advance.