So basically I had a customer hit by a known HP-AMS driver issue (KB2085618), the symptons were as follows;
- Unable to vMotion a VM to another host, gives “operation timed out error”
- If power off VM, vMotion a machine to another host, and then power on, you get the following error “Could not start VMX: msg.vmk.status.VMK_NO_MEMORY”
ESXi memory leak
This issue is caused by a memory leak in the driver which fills the SWAP memory of the ESXi host, making it unable to response to any requests at all,
For example, trying to enable SSH;
