ADVERTISE HERE

vSphere: vCenter shows VMName (Invalid)

Title: vSphere: vCenter shows VMName (Invalid)
Author(s): (ICT-Freak.nl) Arne Fokkema
Target Audience: Technical - Intermediate
Current Revision:
First Published: 30 August 2010
Products: VMware vSphere
UID: XD10323
Posted Mon, 30/08/2010 - 07:21 by xtravirt

The VM was still fully operational but vCenter didn’t recognized the VM’s anymore?

Punchy Text: 

The VM was still fully operational but vCenter didn’t recognized the VM’s anymore?

By Arne Fokkema - ICT-Freak.nl

VMware

After some issues with a NFS share I noticed that a couple of VM’s changed to Invalid. The VM was still fully operational but vCenter didn’t recognized the VM’s anymore.

vSphere Client

I found the following knowledge base article: http://kb.vmware.com/kb/1015778 which describes the following symptoms:

  • Virtual machines display as invalid in vCenter Server
  • The command service mgmt-vmware restart fails to stop the management agent

The command vmware-cmd -l returns the error:

PANIC: SyncWaitQ: The system limit on the total number of open files has been reached

  • The command ps -auxwww shows a large amount of SSHD processes running

In my case the solution was to restart the management agent on the host where the VM’s where running on.

Spotlight:

Posted Fri, 11/09/2009 - 17:40 by xtravirt

VMware Documentation Downloader v11.08.30

Updated for vSphere 5 - A free tool for those on the move who need information FAST

vSphere 5 License Entitlement Changes

See what has changed in the license entitlement in vSphere 5?

Thin Client vs Zero Client

The differences between Thin and Zero desktop clients for VDI

Technology Exchange:

Posted Fri, 11/09/2009 - 17:42 by xtravirt