new1234.jpg

Archive

Posts Tagged ‘Power on’

[VMware] Could not start VMX: msg.vmk.status.VMK_NO_MEMORY

March 29th, 2015 4 comments

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

image

 

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:

For ESXi 5.5, see:

 

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:
TwitterLinkedIn

VMware: The operation is not allowed in the current connection state of the host

March 22nd, 2012 6 comments

Today I want to install Windows 8 in my test lab, after creating a new virtual machine and power-on the VM I received warning error message:

Failed to find a host for powering on the virtual machine. The following faults explain why the registered host is not compatible

The operation is not allowed in the current connection state of the host.

 

image

 

Weird, both ESXi 5.0 hosts are powered on, my vCenter VM is running on the same machine which I want to power on the new virtual machine.. also strange is.. there’s no CPU (0 MHz) and no Memory usage (0,00 MB) activity at this host, check the screenshot below

 

image

Double check..:

image

Jup.. there are two running servers at esx01.vmpros.lan

 

Solution:

After disconnecting the ESXi host from vCenter and reconnect the host I was able to power on virtual machines, also my CPU/Memory activity is back

 

image

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:
TwitterLinkedIn