Last week I had some issues with starting virtual machines on vSphere 5.5 hosts (enough capacity available), when I try to start up the VM I receive message:

Could not start VMX: msg.vmk.status.VMK_NO_MEMORY”

An error was received from the ESX host while powering on VM [name]
Head globalCartel-1 already at its maximum size of 7869288. Cannot expand
Could not start VMX: msg.vmk.status.VMK_NO_MEMORY

Cause

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. This issue occurs with ESXi hosts running on HP hardware with these versions of AMS:

• hp-ams 500.9.6.0-12.434156
• hp-ams-550.9.6.0-12.1198610
• hp-ams 500.10.0.0-18.434156
• hp-ams-550.10.0.0-18.1198610

Solution

This is a known issue affecting ESXi 5.x. To resolve this issue, upgrade to AMS version 10.0.1.

For ESXi 5.0 and 5.1, see:

• HP Agentless Management Service Offline Bundle for VMware ESXi 5.0 and vSphere 5.1.

For ESXi 5.5, see:

• HP Agentless Management Service Offline Bundle for VMware vSphere 5.5
• HP ESXi Offline Bundle for VMware vSphere 5.5

Note: In some cases, commands running on the ESXi host fails with cant’t fork.  In this case the virtual machines running on the ESXi host needs to be powered off and the ESXi host rebooted. To verify the installed versions of AMS, run this command:

esxcli software vib list | grep ams

To remove the package on all hosts running on these AMS versions:

1. Log in to the host using SSH. For more information, see Using ESXi Shell in ESXi 5.x and 6.0 (2004746).
2. Run this command to stop the HP service (does not persist on reboot):
   /etc/init.d/hp-ams.sh stop
3. Run this command to remove the VIB:
   esxcli software vib remove -n hp-ams
4. Reboot the host.

More information:

VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:

Duncan Epping wrote July 22nd:

I received multiple questions around this so decided to ask around internally. I managed to get ahold of the VMware Update Manager (aka VUM) Product Manager and after exchanging a couple of emails this is the outcome:

VMware vSphere Compatibility Matrixes

Table 13 on page 14 of the above linked document states that VUM doesn’t support MS SQL 2008 Standard. This is however untrue and should be considered as a document bug. It is supported and the document will be modified soon to reflect these changes.

 Oke, it’s a document bug, you can install it safely! 🙂

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me: