ESX Server Documentation Features | Technical Resources | Knowledge Base | Discussion Forums ESX Server 2.5.3 Release Notes
Check back frequently for additions
and updates to these release notes. Version 2.5.3 | 4/13/06 | Build 22981 Last Document Update: 4/20/06
What's in the Release NotesThe release notes cover the following topics:
What's New
Resolved IssuesVMware typically publishes lists of issues resolved with each product at or around the time of the specific product release. A list of issues resolved in ESX Server 2.5, 2.5.1, 2.5.2, and 2.5.3 is available at www.vmware.com/pdf/esx2x_fixed_bugs_list.pdf. Release Notes for ESX Server 2.5, 2.5.1, and 2.5.2The ESX Server 2.5.2 Release Notes are available at www.vmware.com/support/esx25/doc/releasenotes_esx252.html. The ESX Server 2.5.1 Release Notes are available at www.vmware.com/support/esx25/doc/releasenotes_esx25.html. The ESX Server 2.5 Release Notes are available at www.vmware.com/support/esx25/doc/releasenotes_esx250.html. Before You BeginPlease refer to the following before you install or upgrade ESX Server:
Known IssuesCheck the VMware Knowledge Base for updates to the issues described in this document. To review all Knowledge Base articles related to ESX Server 2.5.3, search for the keyword "esx253". For any known issue that has a Knowledge Base article link, please use this path to access the article. Change the Knowledge Base number in the URL.http://kb.vmware.com/kb/xxxx Compatibility with VMware VirtualCenter VirtualCenter 1.3 supports ESX Server 2.5.3. However, ESX Server 2.5.3 is not supported by previous VirtualCenter releases. Security Alerts for This Release As of this writing, no security alerts have been identified specifically for ESX Server 2.5.3. Please refer to KB 1107 for VMware product security alerts. Installation
Configuration
Guest Operating System You can find the latest version of the Guest Operating System Installation Guide by following these links: HTML | PDF | Japanese PDF.
Operation Note: Due to ongoing certification, please check the SAN Compatibility Guide for ESX Server 2.x to see if your array is listed before upgrading.
Installation Notes for This Release
Configuring Your System to Install Boot-From-SAN
For hardware compatibility with ESX Server, see the Compatibility Guides available at www.vmware.com/support/resources/esx_resources.html. Note: If you are using a preboot execution environment (PXE), a boot-from-SAN operation will fail and is not supported for this version of ESX Server. Only a local disk PXE installation is supported.
Installing the VMware Virtual SMP Product
Upgrading a Previous ESX Server Release to ESX Server 2.5.3 ESX Server 2.5.3 supports upgrading from the following previous releases:
Note: Using the tar archive, upgrading directly from releases prior to ESX Server 2.0.1 is not supported. To upgrade from ESX Server 1.5 or ESX Server 2.0.0 to ESX 2.5.3, upgrade first to ESX Server 2.0.1 with Upgrade Patch 6. Note: During an upgrade from a previous ESX Server release to ESX Server 2.5.3, this upgrade installer reinstalls all default ESX Server RPMs. If you have modified any of the default ESX Server RPMs, these modifications will be overwritten during the upgrade. To upgrade from previous versions of ESX Server to ESX Server 2.5.3, use the installation CD-ROM. This is the CD you received from VMware or the CD you created from the ISO image file you downloaded from the VMware site. For upgrade instructions, see "Upgrading from a Previous Release of ESX Server" in the ESX Server Installation Guide, available from www.vmware.com/support/pubs/esx_pubs.html .
Upgrading from a Tar Archive
Note: Using the tar archive, upgrading directly from releases prior to ESX Server 2.0.1 is not supported.
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. After the installation, a file named "perllocal.pod" is created in the / directory. The perllocal.pod file is an unnecessary file created as a byproduct of the installation process. It can be safely deleted. |
|