VMware Cloud Community
gpeppa
Contributor
Contributor

VMX connection handshake failed for mks of /vmfs/volumes/4bad.../MyTest/MyTest.vmx

Can someone help me please?

When powering on a Windows 2008 R2 64 bits VM and opening up a console I get the error "VMX connection handshake failed for mks of /vmfs/volumes/4bad.../MyTest/MyTest.vmx" The VM then turns off.

I get the same error even after create an another VM a moVe the vmdk file into the new VM that i create, I also do the same in a diferent datstore with the same results.

Any ideas?

Reply
0 Kudos
6 Replies
Troy_Clavell
Immortal
Immortal

maybe this will help?

http://kb.vmware.com/kb/1002001

Reply
0 Kudos
gpeppa
Contributor
Contributor

I use a template to deploy the virtual machine. Now i use a template of Windows 2003 R2 32 bits with the sames results I am so confuse, it can be a storage problem? becuase I use a differents templates in the same datastore and i have the same errors.

These templates I have been using in another environment and I have not had any problems before.

I think that maybe using the comand to restart the services can be useful

Reply
0 Kudos
athlon_crazy
Virtuoso
Virtuoso

If your case like mine "before this it's working but occasionally it's not" just restart this service :

/etc/init.d/vmware-vmkauthd restart

or

service vmware-vmkauthd restart






vcbMC-1.0.6 Beta

vcbMC-1.0.7 Lite

http://www.no-x.org

http://www.no-x.org
taou
Enthusiast
Enthusiast

you have to check first your storage or sam storage and verify the connectivity beteween esx and storage. in most of time, you will have this issue if there is a problem in connection if we restart the service it will help you to identify the problem. if the problem persiste you have to restart and check the activity on the shared storage and on esx server. waiting for yr replay. TAOU.

Reply
0 Kudos
gpeppa
Contributor
Contributor

Thank you very much, after restarting this service and do some tests, apparently it had corrected the problem, I restartes this service to the other host in the cluster.

Reply
0 Kudos
ab_lal
Enthusiast
Enthusiast

I got the same error however we edited the VM Settings and changed the VM type to a 64 bit OS fixes the error. It was wrongly set to 32 bit.

This typically happens if your VM is trying to start in 64 bit mode, but it has been configured as a 32 bit VM or if you're booting from a corrupt .iso file.

Reply
0 Kudos