Lỗi transport vmdb error failed to connect to peer proces năm 2024

Home
About
Contact

vCenter

vMotion fails at 20% – unable to generate userworld swap file in directory ‘/vmfs/volumes/

Symptoms: Migrating any VM fails at 20% reporting the error "Unable to generate userworld swap file in directory /vmfs/volumes/" User cannot perform VMotion / svMotion of the VM. In some cases , additionally below error is also reported: transport (vmdb) error "-45": failed to connect to peer process Cause: This issue is because of stale… Continue reading vMotion fails at 20% – unable to generate userworld swap file in directory ‘/vmfs/volumes/

I often get "Cannot find a valid peer process to connect to" and sometime before : "Transport (VMDB) error -32: Pipe: Read failed" or "Transport (VMDB) error -14: Pipe connection has been broken"

I've been working for 2 years on this machine without a hitch, upgrading from WS7 to WS9 without any issue.

FYI : we have changed the domain 3 months ago, but this has never be a problem.

I've googled and search on several forum. So far I've tried to :

- restart vmware-auth service as admin

- launch vmware.exe as admin

- stop/start vmx86 service

- uninstall / reboot / install Workstation. 3 times. First using control panel's uninstaller, then doing a /clean before install and finally hunting down any file/reg entry.

- asked IT if any change in group policy have been done recently (like not allowing to run vmware.exe ?!)

- rename vmware.exe (the logs I have look similars to what is in this post : http://communities.vmware.com/thread/331099?start=0&tstart=0 ... but no luck)

- excluded vmware.exe in my the AV (Microsoft ForeFront). Unfortunalely I'm not allowed to disabled it...

- open VM using the player ==> don't work either.

This is not a corrupted file in a VM (even backup -7zipped- are not working on my laptop ... but launch on another).

Even a newly created WM (without an OS), do not boot ! :-(

*BUT TO BE NOTICED* : if a VM is created as a shared VM, I can start it as remote localy ! And this same VM, if started (thru the.vmx) is not working using Workstation GUI !?

I've attached the 2 logs. The working one (vmware.log thru remote) and the non-working (vmware-vmx-4072.log thru WS GUI).

Powering on or migrating a virtual machine fails with error: Transport (VMDB) error -45: Failed to connect to peer process.

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

Symptoms:

Powering on or migrating a virtual machine fails with error:

An error was received from the ESX host while powering on VM. Transport (VMDB) error -45: Failed to connect to peer process.

The vmx binary (in the /bin folder) which is required for a VM to power on is blocked.
You see message similar to:

2017-04-20T14:23:50.533Z cpu9:256411)WARNING: User: 4530: vmx: Error in initial cartel setup: Failed to open /bin/vmx: Operation not permitted

Environment

VMware vSphere ESXi 5.5 VMware vSphere ESXi 6.0 VMware vSphere Client 5.5 VMware vCenter Server Appliance 5.5.x VMware vCenter Server 5.5.x VMware vCenter Server Appliance 6.0.x VMware vCenter Server 6.0.x