Server Consolidation Ratio

August 27, 2009

As a virtualization consultant I am always interested in performance figures of VMware implementations. Especially the achieved server consolidation ratio is an important figure in combination with the used hardware for the VMware implementation.

To get more inside this subject I would like to gather information on your VMware implementation and the achieved server consolidation ratio. I will publish this information on my Consolidation Chart  which is available for everybody. This way, you can compare your consolidation ratio to that of others!

When there is enough information I will publish the figures in a consolidation rate whitepaper.

I am asking the following information from you:

Number of hosts: provide the number of used hosts
Number of VM’s: provide the number of vm’s running
VMware version: ESX 3, ESX 3.5, ESX 4, ESXi 3, ESXi 3.5, ESXi 4
VMware HA: y/n (are you using VMware HA)
Tolerated host failures: (if you are  using VMware HA)
Used server brand: provide the used server brand
Used server type: provide the used server type
Number of CPU’s in host: provide the number of CPU´s per host
Type of CPU in host: provide the CPU type used
Number of RAM in host: provide the number of configured RAM
Used storage type: DAS, iSCSI, FC, NFS
Used storage: provide the brand and type of your storage
Satisfaction level: provide your satisfaction level of your VMware implementation in a rate of 1-5, 1=bad and 5=excellent
Remark: Any remark you would like to leave

You can provide your information as a comment to this post. I will process the comments to the consolidation chart.

I am looking forward to your information! The more information we gather the more value the consolidation chart has!

The Consolidation Chart is available here.

ESXi CIM Agent bug

August 7, 2009

The CIM agent allows ESX to monitor the hardware status of the physical server and provide this hardware status information back to the administrator either through vCenter Hardware status or Health Status views.

Unfortunately there is a problem in the CIM agent in combination with the OEM providers and some IHV information that is reported whether the Hardware exists or not on the host. This problem can result in intermittent lockups of the ESX host.

The problem can be detected by the following warning messages in de vmkernel log of ESXi 3.5 update 4 or ESXi 4 hosts.

StorelibManager::createDefaultSelfCheckSettings – failed to get TopLevelSystem Jul 29 19:53:57 vmkernel: 0:06:03:34.837 cpu2:5535)WARNING: UserThread: 402: Peer table full for sfcbd
Jul 29 19:53:57 vmkernel: 0:06:03:34.837 cpu2:5535)WARNING: World: vm99478: 1111: init fn user failed with: Out of resources!

VMware recommends to disable the CIM agent until this problem is resolved. If this service is disabled or otherwise not available, no updated hardware status information is received until it is available again.

More information on: