ESX Server 3.0.2, Patch ESX-1003524: Updates to VMware-esx-vmkernel, VMware-esx-vmx, and VMware-esx-apps (1003524)
ESX Server might stop responding if it ran out of heap memory for copy-on-write (COW) disk metadata. COW disks are used by several ESX Server facilities such as snapshots, VMware Consolidated Backup (VCB), and VMware Lab Manager. The COW heap might get exhausted when the total theoretical size of COW disks being managed approaches 20 terabytes. This issue has been resolved.
Windows virtual machines might not respond when a virtual machine is updated with Symantec virus definition from 213 to 220.
Virtual machines installed on Microsoft Windows 2003 Server do not respond while rebooting.
Failed to resume virtual disk scsi0:0:The disk has been modified since you took a snapshot or suspended the virtual machine. Error encountered while restarting virtual machine after taking snapshot. The virtual machine will be powered off.
Download and verify the patch bundle as follows:
3. Create a local depot directory.
# mkdir -p /var/updates
Note: VMware recommends that you use the updates directory.
4. Change your working directory to /var/updates.
# cd /var/updates
The md5 checksum output should match the following:
7. Extract the compressed tar archive:
# tar -xvzf ESX-1003524.tgz
8. Change to the newly created directory, /var/updates/ESX-1003524:
# cd ESX-1003524
After you download and extract the archive, and if you are in the directory that you previously created, use the following command to install the update:
# esxupdate update
To run esxupdate from a different directory, you must specify the bundle path in the command:
# esxupdate -r file://<directory>/ESX-1003524 update
For example, if the host is called depot:
# esxupdate -r file:///depot/var/updates/ESX-1003524 update
During the update process, logs appear on the terminal. You can specify the verbosity of esxupdate logs by using the -v option as shown below.
# esxupdate -v 10 file://<directory>/ESX-1003524 update
For more information how to use esxupdate, see the Patch Management for ESX Server 3 tech note at http://www.vmware.com/pdf/esx3_esxupdate.pdf .