Symptoms:
If tasks or operations such as vMotion, clone or create VM are performed within the environment, a particular VM with no association to the task will report the guest OS as hung with vmware.log messages such as below:
Note: This could be a particularly odd behavior, hard to identify and diagnose.
The virtual machine memory limit is set to "0" in the vSphere Client, meaning the virtual machine would not get any memory.
To to start verifying this behavior, check the vmware.log of the virtual machines with problems and look up for a similar message:
Or check the virtual machine configuration in the vSphere Client, under the Memory configuration, confirm that the Limit is set to "0"