VMware Cloud Community
VMTNtt
Enthusiast
Enthusiast
Jump to solution

upgrade esxi from 6.0 to 6.5,VM can't power on

Hi,

I was used VCSA6.5's update manager upupgrade esxi from 6.0 to 6.5 succeessful, but all VM did't power on,the error as follow:

Failed to power on virtual machine 2k3dc01. Transport (VMDB) error -45: Failed to connect to peer pr...


the tasks information:

Power On VM

Key                       haTask-72-vim.VirtualMachine.powerOn-164272284

Description            Power On this virtual machine

Virtual machine       2k3dc01

State                     Failed - Transport (VMDB) error -45: Failed to connect to peer process.

Errors

        • Transport (VMDB) error -45: Failed to connect to peer process.

Could anyone help me?


1 Solution

Accepted Solutions
VMTNtt
Enthusiast
Enthusiast
Jump to solution

Hi,

Thank you very much for your information。

I was install unlocker too


pastedImage_0.png

so i unstall the unlocker and reboot esxi

pastedImage_2.png

aha,the all vm can power on successful.

View solution in original post

14 Replies
esxi_homelab_go
Contributor
Contributor
Jump to solution

I am experiencing the same issue, cannot start VMs using the web client or vSphere client.

Reply
0 Kudos
rdmendo
Contributor
Contributor
Jump to solution

same here Smiley Sad

esxi_homelab_go
Contributor
Contributor
Jump to solution

Found another thread on a similar issue, I don't understand the solution though.

Cannot run VMs after update and reboot, having message "Transport (VMDB) error -45: Failed to connec...

Reply
0 Kudos
rdmendo
Contributor
Contributor
Jump to solution

I don't think it's related, I've tried to do a fresh install, got the same issue.

I've check the /var/log/vmkernel.log, every time I tried to start a VM I have :

WARNING: User: 4530: vmx: Error in initial cartel setup: Failed to open /bin/vmx: Operation not permitted

Config: 706: "SIOControlFlag2" = 0, Old Value: 1, (Status: 0x0)

SunRPC: 1116: Destroying world 0x10baf

Reply
0 Kudos
esxi_homelab_go
Contributor
Contributor
Jump to solution

Similar error here in the log

WARNING: User: 4530: vmx: Error in initial cartel setup: Failed to open /bin/vmx: Operation not permitted

The object in question is a link to another location:

lrwxrwxrwx    1 root     root            13 Nov 26 20:37 /bin/vmx -> /unlocker/vmx

and the target location is as follows:

-r-sr-xr-x    1 root     root      26558456 Nov 26 20:37 /unlocker/vmx

I'm wondering if this has anything to do with the tool that I tried using to enable OS X support on non-Apple hardware.

Reply
0 Kudos
esxi_homelab_go
Contributor
Contributor
Jump to solution

UPDATE: Ran the uninstaller bundled with the Unlocker208, and I can start VMs again.

VMTNtt
Enthusiast
Enthusiast
Jump to solution

Thanks your information.

I could't see the path or file  "esx-xlibs\VMware_bootbank_esx-xlibs_5.5.0-0.0.1331820.vib" in VMware-ESXi-6.5.0-4564106-depot.zip\vib20,i thank the 5.5 and 6.5 architecture is not the same。

Reply
0 Kudos
VMTNtt
Enthusiast
Enthusiast
Jump to solution

Hi,

Thank you very much for your information。

I was install unlocker too


pastedImage_0.png

so i unstall the unlocker and reboot esxi

pastedImage_2.png

aha,the all vm can power on successful.

ksc
VMware Employee
VMware Employee
Jump to solution

vSphere 6.5 has implemented a security sandbox for VMs. One of the aspects of the sandbox is disallowing any executables that are not part of the base system VIB.

A ... modified ... /bin/vmx is pretty obviously going to fail the sandbox check, for reasons that I expect are unsurprising.

Reply
0 Kudos
Marko1982
Contributor
Contributor
Jump to solution

Thank you 1000X

I've read 1000 logs and forums...

Cheers

Reply
0 Kudos
rom3010
Enthusiast
Enthusiast
Jump to solution

Thanks! Smiley Happy

Reply
0 Kudos
glamb
Contributor
Contributor
Jump to solution

Thanks.

The trouble is finding the uninstaller. I had to do a 'find' to find the uninstaller:

[root@Lesxi:~] find . -name esxi-uninstall.sh

  ./vmfs/volumes/56677bb8-b0c74e3c-39db-00e04c680166/tools/unlocker/unlocker208/esxi-uninstall.sh

[root@Lesxi:~] ./vmfs/volumes/56677bb8-b0c74e3c-39db-00e04c680166/tools/unlocker/unlocker208/esxi-uninstall.sh

Reply
0 Kudos
glamb
Contributor
Contributor
Jump to solution

I just realised I NEED the unlocker to run my Mac OS vm's!!

So how do I run the unlocker and get the VMs to power on?

Reply
0 Kudos
sumitsjpr
Contributor
Contributor
Jump to solution

I am having the same issue.

Reply
0 Kudos