VMware ESX Server 2.5.4 Upgrade Patch 3 (for 2.5.4 Systems Only)
This patch addresses the following issues:
- This patch includes an improved watchdog handler to detect and recover network transmit hang that can cause loss of network connectivity. Events detected and recovered are now reported to the system log file.
- This patch corrects an issue which can cause a service console crash when running with Dell OpenManage 5 and a QLogic Fiber Channel controller.
Please refer to KB 1107 for VMware product security alerts. This patch addresses the following security issues:
- A possible security issue with the configuration program vmware-config which could set incorrect permissions and umask on SSL key files. Local users may be able to obtain access to the SSL key files. The Common Vulnerabilities and Exposures project (cve.mitre.org) assigned the name CVE-2006-3589 to this issue.
Note: The affected files include /usr/bin/vmware-config.pl and /usr/bin/vmware-config-mui.pl.
- A possible security issue with the OpenSSL toolkit and the authentication of SSL certificates. Clients using OpenSSL and connecting to a malicious server can be caused to crash. The patch also addresses an issue when using RSA keys with an exponent of 3 that allows the forging of PKCS #1 v1.5 signatures and prevents OpenSSL from properly verifying X.509 and other certificates. The Common Vulnerabilities and Exposures project (cve.mitre.org) assigned the names
and CVE-2006-4343 to these issues.
- A possible security issue with virtual disk (.vmdk or .dsk) files that are newly created, but contain blocks from recently deleted virtual disk files. Information belonging to the previously deleted virtual disk files could be revealed in newly created virtual disk files.
VMware recommends the following workaround: When creating new virtual machines on an ESX Server that may contain sensitive data, use vmkfstools with the -W option. This initializes the virtual disk with zeros.
This patch is an ESX Server 2.5.4 patch.
Please make sure that ESX Server 2.5.4 build 32233 or later is installed before applying the patch. Run vmware -v to display version and build information for your system.
Note: For IBM X460 server, please follow the instructions in KB 8949128 to boot the server into maintenance mode before applying the patch.
Installing the Update
Note: VMware recommends backing up your ESX Server installation before installing this patch. Also, a minimum of 350 MB of temporary free space on "/" filesystem is required for installing this patch.
This update requires you to boot your server into Linux mode to perform the upgrade. When you are prompted to
reboot at the end of the upgrade, the installer will restart your system to run ESX Server.
- Power off all virtual machines.
- Restart your system.
- At the LILO Boot Menu, select the option appropriate for your system.
- For a boot-from-SAN installation, select esx-san-safe.
- For all other installations, select linux-up.
- Log in as root into the ESX Server service console, in Linux mode.
- Download the tar file into the temporary directory under /root on your ESX Server service console.
- Change your working directory to that directory.
- Verify the integrity of the package:
# md5sum esx-2.5.4-36502-upgrade.tar.gz
The md5 checksum output should match the following:
- Extract the compressed tar archive:
# tar -xvzf esx-2.5.4-36502-upgrade.tar.gz
- Change to the newly created directory:
# cd esx-2.5.4-36502-upgrade
- Run the installer:
- The system updates have now been installed. A reboot prompt displays:
Reboot the server now [y/n]?
This update will not be complete until you reboot the ESX Server.
If you enter N, to indicate that you will not reboot at this time,
ESX Server displays the warning message "Please reboot the server manually. Your virtual machines
will not run properly until this is done." If you see this message, you must manually reboot the server
to complete the driver update.
- At the reboot prompt, enter Y to reboot the server.