August 31, 2009
Today at VMworld 2009, VMware anounced ‘VMware GO’. VMware Go is a free web-based service that will enable SMB customers to fly through the ESXi setup process with just a few mouse clicks. VMware GO also allows you to create and manage virtual machines and VMware GO can scan your machines for both PCI compliance and patch updates thanks to SHAVLIK TECHNOLOGIES.
More information: http://communities.vmware.com/community/vmtn/vsphere/esxi/go
Join the beta: https://go.vmware.com/beta.aspx
August 28, 2009
Are you looking for Microsoft Visio stencils for VMware vSphere? Checkout the following awesome stencils made by Maish Saidel-Keesing.
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.
August 24, 2009
VMware has released vCenter Server 4.0 Patch 1 to address an issue with VMware HA. From the VMware KB:
You experience these symptoms:
- In vCenter 4.0, VMware HA might not failover virtual machines when a host failure occurs.
- When the ESX host’s IP address in a VMware HA enabled cluster is configured with certain IP addresses, the node failure detection algorithm fails.
- You are susceptible to this issue when all of your Service Console Port(s) or Management Network IP address(s) on your ESX host fall within the following range:
3.x.x.x – 9.x.x.x
26.x.x.x – 99.x.x.x
Note: You are not affected if one of Service Console Port(s) or Management Network IP address(s) on your ESX host falls outside of this range.
More information on: http://kb.vmware.com/kb/1013013
August 20, 2009
With the release of VMware vShpere 4.0, VMware has made it possible to install ESXi 4.0 to USB storage devices directly attached to the server. To ensure VMware support you have to use a USB key that is approved by the server vendor for the particular server model on which you want to install ESXi 4.0 on a USB flash storage device.
I am currently building a VMware cluster based on ESXi 4 to host virtualized XenApp 5 servers. This cluster is based on HP BL460c G6 blades which have a nice SD Memory slot to boot from.
HP supports ESXi 4 on the following usb storage devices:
– Kingston SD Flash Memory: 2GB Elite Pro SD Card 50x
– HP v100ss 2GB USB flash drive
I am going to test a diskless ESXi 4 host based on the Kingston SD Flash Memory and will post my results on this blog.
More information: http://kb.vmware.com/kb/1010574 and HP
August 18, 2009
When scanning ESX 4 hosts with vCenter Update Manager I noticed that for one of the patches the compliance was reported as ‘conflict’. I never saw this message before so I was curious what this message means.
According to VMware this message indicates the patch conflicts with another patch in the patch depot of vCenter Update Manager. This message does not indicate a conflict with any other patches installed on the host.
More information on http://kb.vmware.com/kb/1013068
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: http://kb.vmware.com/kb/1012575