ESX Server 2.5.2 Release Notes

What's in the Release Notes

The release notes cover the following topics:

• What's New
• Resolved Issues
• Prior Release Notes for ESX Server 2.5 and 2.5.1
• Before You Begin
• Known Issues
• Installation Notes for This Release
• Security Alerts for This Release

What's New

• (Update: 10/17/05) Support for the dual-core Intel Xeon processor, codenamed "Paxville".
  
For details on the support of servers based on this processor, see the Systems Compatibility Guide for ESX Server 2.x
• Support for new servers from HP, IBM, and Dell, including servers using AMD dual-core Opteron processors such as the HP ProLiant DL585.
  
For details on the new servers supported by ESX Server 2.5.2, see the Systems Compatibility Guide for ESX Server 2.x
• Expanded support for a wide range of hardware and software.
  ESX Server 2.5.2 supports new storage arrays, guest operating systems, backup software, and management software.
• If you are managing ESX Server with VMware VirtualCenter, you must use VirtualCenter 1.3, available now!

Resolved Issues

VMware 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, and 2.5.2 is available at www.vmware.com/pdf/esx2x_fixed_bugs_list.pdf.

Release Notes for ESX Server 2.5 and 2.5.1

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 Begin

Please refer to the following before you install or upgrade ESX Server:

• Configuring Your System to Install Boot-From-SAN
• Configuring System Partitions for Boot-From-SAN (KB 1506)
• Disk Controllers Default to Shared Mode on Boot From SAN (KB 1635)
• Installing the VMware Virtual SMP Product
• Installing on Systems Using an IBM Remote Supervisor Adapter II Card or on a System with Baseboard Management Controller (KB 1636)
• Upgrading a Previous ESX Server Release to ESX Server 2.5
• Upgrading from a Tar Archive

Known Issues

Check 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.2, search for the keyword "esx252".

www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=xxxx

Compatibility with VMware VirtualCenter

VirtualCenter 1.3 supports ESX Server 2.5.2. However, ESX Server 2.5.2 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.2.

Please refer to KB 1107 for VMware product security alerts.

Installation

• Installing Linux 64-bit Guest Operating System Fails (KB 1637)
• Installing VMware Tools in Unsupported Linux Distributions (KB 1625)
• Installation Fails During Service Console Installation on Disks that Are Greater Than or Equal to 1 Tb (KB 1639)
• Use the "Custom" Installation Option if using Non-US Keyboards (KB 1640)
• Booting into Linux with Hyper-Threading Enabled (KB 1641)
• "Unresolved Symbols" Error When Upgrading From ESX Server 2.0 to ESX Server 2.x (KB 1642)
• Installing ESX Server 2.5.2 and HP Insight Manager Agents (KB 1810)
• Boot Option Update for Dual-Core AMD Opteron Systems (KB 1852)
• Scripted Install Hangs when VMFS Partitions Are not Contiguously Listed in the Kickstart file (ks.cfg) (KB 1851)

Configuration

• vmsnap_all Does not Allow Spaces in Configuration File Paths (KB 1608)
• Unsupported Features in the ESX Server 2.5.1 Version of the adp94xx Driver (KB 1607)
• Emulex Driver Is Not Supported with Agents in Shared Mode (KB 1606)
• IBM eServer xSeries 366 and Dell Power Edge 6850 Server Cannot Boot into the Linux Kernel (KB 1605)
• ESX Server Graphical Installation is not Displayed Through DELL DRAC Remote Console (KB 1600)
• Adaptec RAID Card in Dell PowerEdge 2650 is not Shown in Dell OpenManage Web Interface (KB 1599)
• The snmpwalk Tool Displays Incorrect Product Version and Build Number (KB 1598)
• Effective BusLogic Qdepth is Limited to 1 on Windows 2000, Update 3, or XP (KB 1614)
• Detecting LUNs on IBM DS4500 Storage Arrays (KB 1846)
• For Multihost Clustering Using Clustered Virtual Disks, the LUN No Longer Requires a Single Path (KB 1827)
• Upgrade Virtual Hardware Appears on Hardware Tab When I Create a Virtual Machine Using Raw Disk or Raw Disk Mapping (KB 1816)
• Virtual Compatibility for Clustered Non-Pass-Through Raw Device Mapping in Multihost Clustering Is Not Supported (KB 1821)
• Adding a Virtual Disk on an Auxiliary Virtual SCSI Controller to a Virtual Machine Moves Other Devices to New PCI Slots (KB 1513)
• VMotion Uses One Port on Virtual Switch, Leaving 31 for Virtual Machines (KB 1825)
• VMware Management Interface Not Able to Manage a Partition Once it is Changed by fdisk (KB 1850)
• Cable Pulls Changed Original Paths, Causing Persistent Binding Issue with Raw Device Mapping (KB 1824)
• After Refreshing, VirtualCenter Reports Only the Memory Allocated to the Service Console and One CPU (KB 1823)
• Must use Physical Compatibility Mode for Shared Disks when using Microsoft Clustering Service with Raw Device Mappings (KB 1822)
• NICs of VMotion Switch Cannot Be Part of Virtual Switch Configuration (KB 1493)
• Default Maximum Size of a File Allowed by VMFS is 144GB, Not 456GB (KB 1847)
• ESX Server 2.5.2 with Microsoft Exchange Server in a Clustered Configuration not Recommended with Emulex HBAs (KB 1858)
• VirtualCenter 1.3 Reports the Wrong Number of CPUs in Dual-Core Host (KB 1872)

Guest Operating System

You can find the latest version of the Guest Operating System Installation Guide by following these links: HTML | PDF | Japanese PDF.

• Red Hat Linux 2.1 WS Guest Operating System Fails to Install with BusLogic Virtual Adapter (KB 1644)
• The Virtual Machine Occasionally Hangs While Running RHEL 3.0 Update 3 or Update 4 (KB 1675)
• Time Can Be Set to Synchronize Between Guest Operating System and Console Once Every Minute, Not Second (KB 1832)
• ESX Server Virtual Machines Running Windows NT 4.0 Guest Operating System Using the vmxnet Virtual NIC lose Network Connectivity After a Short Period (KB 1854)

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.

• Failovers with MSCS Can Take an Excessive Amount of Time (KB 1597)
• The vmsnap and vmres Scripts Do Not Work with Raw Disk Mapping (KB 1681)
• IO Meter Gives an Error Performance Counter Percentage That Is Less Than Zero (KB 1604)
• Unintended IBM FAStT LUNs Causes vmkernel Load Time to Increase Significantly (KB 1596)
• Clustering a Physical Machine with a Virtual Machine (KB 1634)
• vmsnap_all Does Not Create a /var/log/backup.log File (KB 1603)

Installation Notes for This Release

Configuring Your System to Install Boot-From-SAN
For general instructions on configuring ESX Server for boot-from-SAN operation, see the ESX Server SAN Configuration Guide.

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
If you have purchased the VMware Virtual SMP product, then you can create Symmetric Multiprocessing (SMP) virtual machines, with single or dual virtual CPUs. You install the Virtual SMP product during your ESX Server installation by inserting its serial number during the licensing step of your ESX Server installation.

Upgrading a Previous ESX Server Release to ESX Server 2.5.2
ESX Server 2.5.2 supports upgrading from the following previous releases:

• ESX Server 2.5.1 (and with patches)
• ESX Server 2.5 (and with patches)
• ESX Server 2.1.2 (and with patches)
• ESX Server 2.1.1
• ESX Server 2.1
• ESX Server 2.0 Security Update
• ESX Server 2.0.1 (and with patches)
• ESX Server 2.0.1 Security Update

Upgrading from a Tar Archive
If you are using the downloaded tar archive, note the filename of the download file and make appropriate substitutions in the file and directory names shown below.

Note: Using the tar archive, upgrading directly from releases prior to ESX Server 2.0 is not supported.

1. Shutdown or suspend all virtual machinese and boot into Linux.
   /sbin/lilo -R linux
   /sbin/reboot
2. Log on as root.
3. Make a directory named download (or use another name of your choice.) This directory must be accessible to the service console on the server you want to upgrade.
4. Save the file esx-2.5.2-16390-upgrade.tar.gz to this directory.
5. Change to the download directory.
6. Extract the contents of the file.
   tar zxf esx-2.5.2-16390-upgrade.tar.gz
7. Change to the directory esx-2.5.2-16390-upgrade.
8. Run the upgrade script.
   ./upgrade.pl
9. You see various messages about the upgrade process.
10. When prompted, reboot the system. When the system reboots, you are finished upgrading VMware ESX Server.