This patch contains the following fixes and enhancements:
Fixes an issue that will circumvent the need to wait for VMFS operations to complete on certain conditions, thereby reducing occurrence of virtual machines lockup in ESXi 4.0 hosts.
Symptom: Virtual machines might fail or temporary unresponsive network can occur during VMFS configuration changes. Other possible time-consuming VMFS locked-out operations include:
Creating a VMFS datastore
Expanding a VMFS datastore onto additional extents
Powering on a virtual machine
Acquiring a lock on a file
Creating or deleting a file
Creating a template
Deploying a virtual machine from a template
Creating a new virtual machine
Migrating a virtual machine with vMotion
Growing a file. For example, a snapshot file or a thin provisioned virtual disk.
On ESXi 4.0 hosts connected through vSphere Client and vCenter Server, the status of the System Board 2 ProcHot sensor is displayed as Unknown. In vSphere Client, the System Board 2 ProcHot sensor status is displayed under the Configuration tab. In vCenter Server, the System Board 2 ProcHot sensor status is displayed under the Hardware Status tab. This issue is seen only on ESXi hosts running on HP AMD platforms that support the Six-Core AMD Opteron processors.
After applying this patch:
On ESXi hosts connected through vSphere Client, the System Board 2 ProcHot sensor is not listed.
On ESXi hosts connected through vCenter Server, the System Board 2 ProcHot sensor does not report status and displays Current State: Unknown: OEM-Specific in the Details column.
After upgrading vCenter Server 4.0 to 4.0 Update 1, the following error message might result while reconnecting ESXi hosts to vCenter Server: Cannot install the vCenter agent service. Unknown Installer.
Symptom: vCenter Server reports the Cannot install the vCenter agent service. Unknown Installer error. After the error, the ESXi host either stays disconnected or is not displayed in vCenter Server. All attempts to add or reconnect the ESXi hosts to vCenter Server fail. The /var/log/vmware/vpx-iupgrade.log file on the ESXi 4.0 host contains the error:
Acquiring lock /tmp/bootbank.lck Copying vpxa.vgz to /bootbank/vpxa.vgz Editing /bootbank/boot.cfg to add module vpxa.vgz [90597] 2009-11-30 15:21:49: status = 0 [90597] 2009-11-30 15:21:49: exec /sbin/vmkramdisk vpxa.vgz Failed to mount archive: Out of memory
