VMware

VMware ESX Server 2.5.2 Upgrade Patch 2 (for 2.5.x Systems)

Released 12/28/05

TAR File

This patch for ESX Server 2.5.x addresses the following issues:

  • This patch enables support for OEM versions of the IBM xSeries 260, 366, and 460 servers. Please note that this enabling of support does not guarantee server certification. Consult the Systems Compatibility Guide for ESX Server 2.x for information on which servers are currently certified.
  • Previous versions allowed downgrading the ESX Server installation back to builds or patches prior to the currently installed version. This version of the installer prevents downgrading, which is the more correct behavior.
  • During patch installation, the patch installer did not check to see if the patch was already installed before proceeding with installation. This version of the patch installer will not apply this patch if it detects that it is already installed.
  • Previously, changes to persistent bindings settings (settings which allow you to assign a specific target SCSI ID to a Fibre Channel device) were reset to default values after rebooting the ESX Server system. These bindings are now permanent, and survive reboots, in this patch release. After installing Upgrade Patch 2, you will need to update persistent bindings manually whenever you add a new target to the Fibre Channel SAN. See knowledge base article 1894 for more information.
  • Security fix -- Corrects a potential vulnerability in the VMware Management Interface which could allow remote code execution in the Web browser. See knowledge base article 2001.

There are separate patches for ESX Server 2.1.2 and 2.0.1 available as the VMware ESX Server 2.1.2 Upgrade Patch 6 and VMware ESX Server 2.0.1 Upgrade Patch 6.

Applicability
This update applies only to ESX Server 2.5, 2.5.1, and 2.5.2. Please make sure that one of these versions is installed before applying the patch. The installer will log the name of this patch and information on the updated components in the file /var/log/vmkernel-version.

Important Notes
After updating your system, you must update the version of VMware Tools installed in your virtual machines.

After updating your system, if you are using persistent bindings with the qla2300_604 or qla2300_607 QLogic drivers, you must manually modify the pbindings file. For details, see knowledge kase article 2005.

Installing the Update
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.

  1. Power off all virtual machines and shut down your server.
  2. Restart your system.
  3. 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.
  4. Log in as root into the ESX Server service console, in Linux mode. Make sure your path variable contains /usr/bin:/bin.
  5. Download the tar file into the temporary directory /tmp on the service console.
  6. Change directories to /tmp.
  7. Verify the integrity of the package:
    # md5sum esx-2.5.2-18819-upgrade.tar.gz

    The md5 checksum output should match the following:
    73997afacbd0bbd43ef8b384c0480816 esx-2.5.2-18819-upgrade.tar.gz

  8. Extract the compressed tar archive:
    # tar -xvzf esx-2.5.2-18819-upgrade.tar.gz
  9. Change directories to the newly created directory /tmp/esx-2.5.2-18819-upgrade:
    # cd esx-2.5.2-18819-upgrade
  10. Run the installer:
    # /usr/bin/perl ./upgrade.pl
  11. The system updates have now been installed. A reboot prompt displays:
    Reboot the server now [y/n]?
  12. 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 for this update to take effect. Update has been terminated unexpectedly." If you see this message, you must manually reboot the server to complete the driver update.

  13. At the reboot prompt, enter Y to reboot the server.