June 14, 2010
VMware has released the next major update on VMware ESX 4.0 with the release of VMware ESX 4.0 Update 2.
The following information provides highlights of some of the enhancements available in this release of VMware ESX:
- Enablement of Fault Tolerance Functionality for Intel Xeon 56xx Series processors— vSphere 4.0 Update 1 supports the Intel Xeon 56xx Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel Xeon 56xx Series processors.
- Enablement of Fault Tolerance Functionality for Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors— vSphere 4.0 Update 1 supports the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors.
- Enablement of IOMMU Functionality for AMD Opteron 61xx and 41xx Series processors— vSphere 4.0 Update 1 supports the AMD Opteron 61xx and 41xx Series processors without input/output memory management unit (IOMMU). vSphere 4.0 Update 2 enables IOMMU functionality for the AMD Opteron 61xx and 41xx Series processors.
- Enhancement of the esxtop/resxtop utility— vSphere 4.0 Update 2 includes an enhancement of the performance monitoring utilities, esxtop and resxtop. The esxtop/resxtop utilities now provide visibility into the performance of NFS datastores in that they display the following statistics for NFS datastores: Reads/s, writes/s, MBreads/s, MBwrtn/s, cmds/s, GAVG/s(guest latency).
- Additional Guest Operating System Support— ESX/ESXi 4.0 Update 2 adds support for Ubuntu 10.04. For a complete list of supported guest operating systems with this release, see the VMware Compatibility Guide.
Resolved Issues – In addition, this release delivers a number of bug fixes that have been documented in the Resolved Issues section.
The full release notes forVMware ESX 4.0 Update 2 can be read here.
VMware ESX 4.0 Update 2 can be downloaded here.
March 10, 2010
Sometimes after renaming your vCenter server or performing an upgrade of vCenter the vCenter Management Webservices monitoring can get correpted. The most visible symptoms of this problem is within the vCenter Service Status of the Administration section of the VI client:
vCenter Management Webservices shows an Alert with a message of
“Unable to retrieve health data from https://servername.mydomain.local:8443/vws/Query/Health“
This error can be corrected with the following procedure:
- On the vCenter server go to Start -> All programs -> ADAM -> ADAM ADSI Edit
- Right click on the ADAM ADSI edit and select connect to
- Ensure the following is selected under connection settings:
Connection name: VC
Server name: localhost
Distinguished name is selected and name is dc=virtualcenter, dc=vmware, dc=int
Click OK to connect
- You need to delete :CN=<VCGUID>,OU=ComponentSpecs, OU=Health, dc=virtualcenter,dc=vmware,dc=int
- After deleting this container you will need to restart the vCenter service and the webaccess.
A new container will be created and the error mentioned above will be corrected.
You will also notice that the storage management service monitor does not show up anymore. Don’t worry. After a couple of minutes the monitor will return.
October 21, 2009
VMware vCenter CapacityIQ has been released by VMware. vCenter CapacityIQ is vCenter plugin for proactively monitor the capacity of your VMware Infrastructure. vCenter CapacityIQ monitors cpu, memory and disk I/O usage and predicts future demands for resources.
vCenter CapacityIQ allows you to show impacts in capacity as well as forecasted capacity based on changes you predict will happen to the environment.
From the VMware site:
‘VMware vCenter CapacityIQ is a value-add component of the vCenter family of management solutions, providing capacity management capabilities for virtualized datacenter or desktop environments. CapacityIQ integrates seamlessly with VMware vCenter Server, ensuring that your virtualized infrastructure capacity is always predictable and efficiently used.
- Eliminate waste by identifying any unused or over-allocated capacity
- Reduce operational overhead by automating routine capacity monitoring and management tasks
- Minimize business risk of outages or failures resulting from capacity bottlenecks and shortfalls
More information can be found on: http://www.vmware.com/products/vcenter-capacityiq/
September 4, 2009
One of the new features of vSphere is the ability to grow a volume/extent. This way you don’t have to add additional extends/lun’s to grow a datastore.
However trying to a grow a volume with vCenter on a ESXi 4 host didn’t work for me. If I clicked on the "Increase" button, a pop-up for Increase DataStore Capacity came up, but it was blank.
vCenter reports 110 GB on the device and 100 GB capacity on the extent. So vCenter did recognize the increase of the lun, but I wasn’t able to use the ability to grow an extent.
After some research I found out that the ability to grow a volume/extent does work on new created datastores on vSphere.
However under some circumstances a datastore upgraded from ESX 3.5 cannot be not be grown from the vSphere client through vCenter. But when you connect directly to the ESX host it can be upgraded! vCenter now presents the datastore as expandable.
Not possible when done via vCenter. How strange?
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 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
Host Profiles is a really useful new feature of vCenter. However in some situations they could be more intelligent. For example when you define in the host profile to add an additional nic to vswitch0 to make the management network redundant, this results in deleting vswitch0 en recreating vswitch0 when you apply the host profile.
During the execution of this tasks the configurations ends with a communication error between vCenter and the ESX host because the management network is not available anymore (due to deleting vswitch0).
Also when a host profile with a configuration that enables VMotion on a selected vmknic is applied to an ESX host, the selected vmknic might not get enabled for VMotion on the ESX host. If the ESX host is checked for host profile compliance, the compliance status might be displayed as Non-compliant.
More information in the following VMware KB: