VMFAQ.com - FAQing about virtualization since 2008
Search:     Advanced search
Browse by category:
Contact Us

vmx connection handshake failed for mks of vmfs

Add comment
Views: 6848
Votes: 6
Comments: 0
Posted: 01 Jul, 2009
by: Troen L.
Updated: 01 Jul, 2009
by: Troen L.

This error message indicates that your VM didn't start properly and was powered off. 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.

If you look in the log file of the VM you will see a message similar to this one:

Jul 01 12:21:30.093: vcpu-0| MonitorInitReserveMem64: vmm64OverheadPages=5156
Jul 01 12:21:30.095: vcpu-0| Could not reserve memory for vmm64. Are you sure your VM specifies a 64 bit guest OS type?

In the above case, changing the VM type to a 64 bit OS fixes the error.

Others in this Category
document Which hardware can I install ESX on?
document My VirtualCenter database is huge and slow, can I purge it?
document Need to mount a snapshotted LUN or a LUN that was suddenly lost
document ESX 3.5u4: List of supported guest operating systems
document I'm getting a black console screen from my guest
document How to update the uEFI BIOS from the Service Console of ESX4
document I have 64bit CPU but I can't boot/install 64bit guests?
document "This installation package is not supported by this processor type." when installing vCenter 4.1
document Is there a GUI for Storage VMotion?
document Upgrading VMware Tools fails on Windows Server 2008 with the message "Error 1316. A network error occured while attempting to read from the file C:\Windows\Installer\VMware Tools.msi"
» More articles



RSS