VMware

VMware ESX Server 3.0.3 Release Notes

ESX Server Version 3.0.3 | 8 August 2008 | Build 104629

Last Document Update: 26 August 2008

Check frequently for additions and updates to these release notes.

 

The release notes cover the following topics:

What's New in the ESX Server 3.0.3 Release

This release of VMware ESX Server 3.0.3 offers the following improvements:

Processors

Newly supported processors are:

  • Quad-Core AMD Opteron 8300 series and 2300 series processor families (collectively code-named Barcelona)
  • Dual-core Intel Xeon 5200 series processors (code-named Wolfdale)

Drivers

Upgraded drivers are:

  • igb driver version 1.0.0
  • Broadcom 5722 tg3 driver version upgraded from 3.43.to 3.58b
  • Emulex lpfc driver version upgraded to 7.3.2_vmw10

Guest Operating Systems

Newly supported guest operating systems are:

  • Microsoft Windows Server 2003 R2 Data Center Edition
  • Red Hat Enterprise Linux 5.1

Enhanced Patch and Upgrade Management

Significant improvements to the following patch management utilities:

  • esxupdate Utility - Support for super-bundle and rollup features in esxupdate.
  • Support for VMware Update Manager.

Service Console

Update for service console from RHEL3 U8 to RHEL3 U9.

Management Agents

Support for new versions of Management Agents:

  • HP Insight Manager 8.1
  • Dell OpenManage Server Administrator 5.4
  • IBM Director 5.20 Update 1

Backup Software

Support for additional backup software from third-party vendors:

  • EMC Networker Version 7.4 SP1
  • IBM Tivoli Storage Manager Version 5.5

Quality Improvements

A significant number of issues have been fixed. Some of these issues have been described in Resolved Issues in this Release.

Top of Page

Prior Releases of VMware Infrastructure 3.0

Features and known issues from prior releases of VMware Infrastructure 3.0, which include ESX Server 3.0.x and VirtualCenter 2.0.x releases, are described in the release notes for each release.

ESX Server Releases

  • ESX Server 3.0.2 (HTML)
  • ESX Server 3.0.1 (HTML)
  • ESX Server 3.0 (HTML)

VirtualCenter Releases

  • VirtualCenter 2.0.2 (HTML)
  • VirtualCenter 2.0.1 (HTML)
  • VirtualCenter 2.0 (HTML)

Top of Page

Installation Notes

  • See the ESX Server Compatibility Guides before installing this software. Verify that your servers, I/O devices, storage devices, guest operating systems, management agents, and backup software are compatible. These guides also address the minimum requirements and scaling limits associated with this release. To view a guide, click one of the following links:
    • Systems Compatibility Guide for ESX Server 3.0.x (PDF)
    • I/O Compatibility Guide for ESX Server 3.0.x (PDF)
    • Storage Compatibility Guide for ESX Server 3.0.x (PDF)
    • Backup Software Compatibility Guide for ESX Server 3.0.x (PDF)
    • Guest Operating System Installation Guide (PDF)
  • VMware strongly recommends that you read the Installation and Upgrade Guide (PDF) for step-by-step guidance on installing and configuring ESX Server and VirtualCenter.
  • Although the installations are straight forward, several subsequent configuration steps are essential. In particular, read:

    • "Licensing" in the Installation and Upgrade Guide (PDF)
    • "Networking" in the Server Configuration Guide (PDF)
    • "Security" in the Server Configuration Guide (PDF) for firewall ports
  • If you are upgrading an existing ESX Server (and VirtualCenter environment), read the "Upgrading" chapters of the Installation and Upgrade Guide (PDF).
  • To use the esxupdate utility to apply software updates on ESX Server 3.0.3, read the ESX Server 3 Patch Management Guide (PDF).
  • To learn about VMware Infrastructure compatibility, read the VMware Infrastructure Compatibility Matrixes (PDF).

Top of Page

Upgrading or Migrating to ESX Server 3.0.3

This release supports upgrading from ESX Server 2.x to VMware Infrastructure 3.0, which includes ESX Server 3.0.x and VirtualCenter 2.x. VMware highly recommends that you review the detailed upgrade instructions and guidelines provided in the Installation and Upgrade Guide (PDF).

Note: Migration upgrade with VMotion supports upgrades only from specific versions of ESX Server 2.x software. Please refer to KB 8479101 for more information.

To upgrade your ESX Server 2.x or 3.0.x host to ESX Server 3.0.3, follow one of these supported upgrade paths:

Upgrade type

ESX Server

2.1.2 and 2.1.3

ESX Server

2.5.4 and 2.5.5

ESX Server

3.0.0

ESX Server

3.0.1

ESX Server

3.0.2 and 3.0.2U1

Tarball Yes Yes Yes Yes Yes
ISO image Yes Yes Yes Yes Yes

 

Note: VMware recommends customers running unsupported ESX Server releases to upgrade to the nearest supported release and then upgrade to ESX Server 3.0.3.

For more information on installation and upgrade methods, see the Installation and Upgrade Guide (PDF).

Upgrade an ESX Server 2.x host to ESX Server software version 3.0.3 using a tarball:

  1. From http://www.vmware.com/download/vi/, click the Download button. The Download page for VMware ESX Server 3 appears.
  2. Log in to the Download site. The license agreement page appears.
  3. Click Yes to accept the terms of the license agreement. The Download page appears.
  4. Download the tarball named esx-upgrade-from-esx2-3.0.3-104629.tar.gz.
  5. Verify the md5sum by executing the following command:

    # md5sum esx-upgrade-from-esx2-3.0.3-104629.tar.gz

    The md5 checksum output should match the following:

    # 0ad8fa4707915139d8b2343afebeb92b esx-upgrade-from-esx2-3.0.3-104629.tar.gz

  6. Follow the instructions in the section "Upgrading from a Tarball" of the Installation and Upgrade Guide (PDF).

Upgrade an ESX Server 3.0.x host to ESX Server software version 3.0.3 using esxupdate:

  1. From http://www.vmware.com/download/vi/, click the Download button. The Download page for VMware ESX Server 3 appears.
  2. Log in to the Download site. The license agreement page appears.
  3. Click Yes to accept the terms of the license agreement. The Download page appears.
  4. Download the tarball named esx-upgrade-from-esx3-3.0.3-104629.tar.gz from http://www.vmware.com/download/vi/.
  5. Verify the md5sum by executing the following command:

    # md5sum esx-upgrade-from-esx3-3.0.3-104629.tar.gz

    The md5 checksum output should match the following:

    # ff7f3dc12d34b474b231212bdf314113 esx-upgrade-from-esx3-3.0.3-104629.tar.gz

  6. Follow the instructions in the section "Upgrading Using esxupdate" of the Installation and Upgrade Guide (PDF).

Upgrade any ESX Server 2.x or 3.0.x host using the ESX Server 3.0.3 ISO:

  1. From http://www.vmware.com/download/vi/, click the Download button. The Download page for VMware ESX Server 3 appears.
  2. Log in to the Download site. The license agreement page appears.
  3. Click Yes to accept the terms of the license agreement. The Download page appears.
  4. Download the ISO image named esx-3.0.3-104629.iso from http://www.vmware.com/download/vi/.
  5. Verify the md5sum by executing the following command:

    # md5sum esx-3.0.3-104629.iso

    The md5 checksum output should match the following:

    # c2cda9242c6981c7eba1004e8fc5626d esx-3.0.3-104629.iso

  6. Follow the instructions in the section "Graphical installer from CD," or the section, "Text-mode Installer from CD" of the Installation and Upgrade Guide (PDF).

Updated RPMs and Security Fixes

For a list of RPMs updated in this release, see the Updated RPMs and Security Fixes (PDF).

Top of Page

Upgrading or Migrating from ESX Server 3.0.3 to ESX Server 3.5

VMware recommends that you upgrade from ESX Server 3.0.3 to ESX Server 3.5 Update 2 or a later update release. Upgrading from ESX Server 3.0.3 to either ESX Server 3.5 GA or ESX Server 3.5 Update 1 results in a loss of functionality since the service console kernel and some of the drivers in ESX Server 3.5 GA and Update 1 are of lower versions than ESX Server 3.0.3.

Top of Page

Compatibility of ESX Server 3.0.3 with VMware VirtualCenter

ESX Server 3.0.3 is compatible with VMware VirtualCenter 2.0.2 and VMware VirtualCenter 2.5.

Top of Page

Configuring VMware Update Manager on ESX Server 3.0.3

Patches for ESX Server 3.0.3 can be managed by VMware VirtualCenter 2.5 Update 2 and VMware Update Manager Update 2 or later.

To run VMware Update Manager on ESX Server 3.0.3, change the default value of the SupportedBaseHostVersion tag in the vci-integrity.xml file in the Update Manager installation directory

Default Value: <SupportedBaseHostVersion>3.1.0</SupportedBaseHostVersion> to

New Value: <SupportedBaseHostVersion>3.0.3</SupportedBaseHostVersion>

After changing the default value, restart Update Manager service in Microsoft Windows Start / Stop services panel. Update Manager can now be run on ESX Server 3.0.3.

Note: VMware Update Manager does not support upgrades from ESX Server 3.0.3 to ESX Server 3.5.x. You can upgrade from ESX Server 3.0.3 to ESX Server 3.5.x by using CDROM, esxupdate, and tarball.

Top of Page

Known Issues in ESX Server 3.0.3 Release

  • Error Messages Displayed for Non-Critical Missing Packages
    Even though VMware-esx-debug-tools.rpm and vmware-hwdata-legacy.rpm are not required for ESX Server 3.0.3, Missing packages: VMware-esx-debug-tools-3.0.0-34330 vmware-hwdata-legacy-1.00-6vmw messages continue to be displayed. These messages can be ignored.
  • Resetting a Virtual Machine Generates an Unknown MKS Event Error
    Sometimes, resetting a virtual machine displays the error message Error connecting:Unknown MKS event Do you want to try again? 0) Yes (1) No.
    Workaround: Click No to continue booting to the virtual machine. Virtual machine will continue to operate normally after No option is selected.
  • Scripted Install Fails While Using Spanning Tree Protocol and Portfast Option is Disabled
    While performing a scripted install using a kickstart file from a network location, the installer might time out waiting for a DHCP request if the network switch is configured with a large STP forwarding delay.
  • Unable to Install VMware Tools on Solaris 10 U4 with ESX Server 3.0.3
    On ESX Server 3.0.3, installation of VMware tools on Solaris10-U4 guest operating system might fail with the error message Unable to copy the source file /usr/lib/vmware-tools/configurator/XOrg/7.1/vmware_drv.so to the destination file /usr/X11/lib/modules/drivers/vmware_drv.so. Execution aborted.

Top of Page

Resolved Issues in ESX Server 3.0.3 Release

For any resolved issue that has a Knowledge Base article link, use the following path to access the article:

http://kb.vmware.com/kb/<knowledge_base_article_number>

This release includes fixes for the following issues:

Upgrade and Installation Issues

  • ESX Server Installation on a Server Installed with a Matrox MGA 200 Chipset Generates Error
    Installing ESX Server 3.0.2 on a machine with a Matrox MGA 200 chipset (for example, RX300 S3) generates the following error message:
    Running the Vmware Server 3 installer
    Probing for video card: VESA driver (generic) Probing for monitor type:
    CPD-200EST Probing for mouse type: Generic - 3 Button Mouse (PS/2) Attempting to start native X server Waiting for X server to start... log located in /tmp/x.log 1...2...3...4...5.... X server started successfully
    mini-wm: Fatal IO error 2 (Connection reset by peer) on X server :1.0. However, the setup continues in text mode.
    This issue has been resolved in ESX Server 3.0.3.
  • Enable UTF8 Support in esxupdate
    In the prior releases, if any non-ASCII characters are present in the descriptor.xml file, esxupdate tries to convert these characters to ASCII before printing, and raises an exception. This issue is fixed in ESX Server 3.0.3 by changing textual information from the descriptor.xml to be encoded as a UTF-8 byte stream before being printed to the display.
  • Removes tzdata-update-1.1-1vmw.rpm from ESX Server 3.0.3
    Upgrading from ESX Server 3.0.1 or ESX Server 3.0.2 to ESX Server 3.0.3 removes the tzdata-update*.rpm from ESX Server 3.0.3, and retains only the tzdata*.rpm. Daylight-saving time (DST) files do not get altered.
  • Kickstart Installation Fails on Any Other Port Other Than Port 80
    Kickstart installation fails when retrieving a kickstart file via HTTP using a port other than port 80. This release allows kickstart installation to use a HTTP port other than port 80.
  • esxupdate Removes RPM Software Packages No Longer Required by Upgraded ESX Server Host
    If an ESX Server host is upgraded to ESX Server 3.0.3, esxupdate removes the RPM software packages that are not required or that are obsolete and replaced by newer RPM packages in the upgraded ESX Server host.
  • Non-root User Account Option
    The ESX Server 3.0.3 installer now provides an option to add a non-root user account.
  • Installation of ESX Server 3.0.x by Using Kickstart File in Interactive Mode Fails
    This release fixes an issue with the installation of ESX Server 3.0.3 using kickstart file in interactive mode.
  • Naming Convention Changed for 3.0.3 RPMs
    This release introduces a new naming convention for ESX Server 3.0.3 RPMs. All installed RPMs will have a 303 prefix for unique identification and easy upgrade.
  • Incorrect US Time Zone Choices
    US time zone choices are corrected in the installer's UTC Offset selection method.
  • ESX Server Installation Fails on an IBM Blade Server with a cKVM Card
    This release fixes an issue where an ESX Server installation in text or graphical mode fails on an IBM Blade Server system installed with a cKVM (Concurrent Keyboard, Video and Mouse) card.

Networking Issues

  • ESX Server SNMP Agent Reports Incorrect sysObjectId
    This release fixes an issue where ESX Server SNMP Agent reports incorrect sysObjectId.
  • ESX Server Stops Responding and Displays a Purple Screen
    This release fixes an issue where ESX Server stops responding, and displays a purple screen with the error message Failed to ack TLB invalidate.
  • Limit Maximum Number of vswifs to 16
    Starting with this release, the maximum number of virtual switches created by esxcfg-vswif command is restricted to 16.
  • VMkernel Gateway Is Not Set if Service Console Network Uses DHCP and ESX Server Is Rebooted
    This release fixes an issue where the VMkernel gateway is not set if the service console network uses DHCP and ESX Server is rebooted.
  • tg3 Driver Might Cause ESX Server to Stop Responding Under Heavy Network Traffic
    tg3 driver installed on an ESX Server might cause the ESX Server to stop responding. Failed to ack TLB invalidate error messages are generated in the backtrace/messages on the service console. tg3 driver v3.58b released with ESX Server 3.0.3 fixes this issue.
  • Improper State of Uplink Displayed When Beaconing Is Enabled
    For each timer run, beacon selects the uplink to check the status in a round-robin method. This might lead to a state where an uplink is marked as down though the uplink is functioning correctly. This issue is resolved by checking the state of all the uplinks instead of a round-robin method.

Virtual Machine Management Issues

  • Links in Help Page of VMware Tools Displays an Error Message
    This release fixes an issue where some of the hyperlinks in the Help page of VMware Tools display the error message An error occurred while loading file:/usr/lib/vmware-tools/hlp/<xxx>.htm. The file or folder /usr/lib/vmware-tools/hlp/<xxx>.htm does not exist.
  • Images and Navigation Buttons in VMware Tools Are Not Displayed Properly
    This release fixes an issue where images and navigation buttons in the VMware Tools Help for Windows virtual machines are not displayed properly.

  • Expanded Volume Size Not Detected on ESX Server Hosts Accessing Same LUNs
    This release fixes an issue when expanding a LUN through the VMware Infrastructure Client. The expanded volume size (vdf -h) is not detected on other ESX Server hosts accessing the same LUN even after a rescan.
  • NetworkManager in Ubuntu Guest Operating System Reports No Network Connection
    Installing VMware Tools in an Ubuntu guest operating system causes the vmxnet drivers to be installed, but NetworkManager reports no network connection in spite of network connectivity. This issue is resolved by vmxnet driver reporting the correct link state.
  • Complete Path for *.properties Files Updated in the Output of vm-support Command
    The output from vm-support command in ESX Server 3.0.3 contains the complete path of *.properties files of Apache Tomcat server.

Storage Issues

  • Corrupted Snapshot Delta Disk of a Virtual Machine Might Prevent ESX Server from Responding
    This release fixes an issue where ESX Server might stop responding when accessing a corrupted snapshot delta file of a virtual machine.
  • Upgrade emulex Driver in ESX Server 3.0.3 to 7.3.2_vmw10 Version
    This release upgrades emulex driver in ESX Server 3.0.3 to 7.3.2_vmw10 version.
  • List EMC-Symmetrix Gatekeeper LUNs and Their Console Operating System Names in Output of esxcfg-vmhbadevs Command
    Starting with this release, the esxcfg-vmhbadevs command has been fixed to display the gatekeeper LUNs with their console operating names.
  • Logical Volume Manager Allows Same Extent to Be Added Twice to a Volume
    This release fixes an issue where one ESX Server host can add the same extent twice to a volume created by another ESX Server host.
  • esxtop Utility Provides Additional Storage Utilization Statistics In Storage Device Panel
    Starting with this release, the esxtop utility displays statistics on the total number of SCSI conflicts, number of conflicts per second, and duration per successful reservation in the Storage Device panel in a manner similar to the following:
    10:37:02am up 2:02, 50 worlds; CPU load average: 0.07, 0.01,
    0.01
    SCSI stats: 0 conflicts, 0.00 conflicts/sec,284.33 usec/cmd

    ADAPTR CID TID LID WID NCHNS NTGTS NLUNS NVMS AQLEN LQLEN WQLEN
    vmhba0 -   -   -   -   1     1     1     9    128   0     0
  • iSCSI Software Controls Multipath Failover
    This fix enables iSCSI software to control multipath failover with LUN reset or target reset through the advance configuration options Disk.UseLunReset and Disk.UseDeviceReset.
  • Complete Usage of VMFS Volume Causes Delay in File System Operations
    This release fixes an issue where if a VMFS volume is full, it causes a delay in file system operations.
  • Upgrade emulex Driver in ESX Server 3.0.3 to 7.3.2_vmw10 Version
    This release upgrades emulex driver in ESX Server 3.0.3 to 7.3.2_vmw10 version. The new version incorporates critical bug fixes to the emulex driver.
  • Virtual Machines Can Recognize Changes Made to RDM LUN Size
    Starting with this release, any modifications made in the RDM LUN size on the storage is recognized by the virtual machines using the LUN as RDM.
  • Make Software iSCSI Adapter Queue Depth and LUN Queue Depth Configurable
    This change makes the software iscsi adapter queue depth and lun queue depth as module parameters that can be configured at module load time.

    The configurable parameters are:

    1. iscsi_max_lun_queue - accepts values in the range 1-255 with a default value of 32.
    2. iscsi_max_adapter_queue - accepts values in the range 128-8192 with a default value of 4096.

Service Console Issues

  • File Systems Mounted on LUN Become Read-Only When TestUnitReady Command Fails
    This release fixes an issue where file systems mounted on a LUN becomes read-only when a TestUnitReady command fails.
  • .config File Missing in Service Console
    Previously, the ESX service console kernel-source package omitted the .config file that sets which Linux kernel options are to be enabled. The kernel-source package now provides a .config file, which enables OEM Management Agent packages such as Dell OpenManage, HP Insight Manager, and IBM Director to build kernel modules.
  • Service Console Oops Error with KVM Switches
    This release resolves a service console Oops error that occurs with various KVM (Keyboard Video Mouse) switches, particularly on blade server systems.
  • Error Message Generated in esxcfg-firewall Log
    This release fixes an issue where error messages are generated in the esxcfg-firewall log during ESX Server 3.0.2 installation.
  • Traceback Occurs When Setting krb5 Options with esxcfg-auth Command
    This release resolves the issue of traceback occurrence when krb5 options are set with the esxcfg-auth command.
  • Guest Operating System Stops Responding Due to Race Condition in Vmxnet
    This release fixes an issue where a race condition can occur in the vmxnet driver when its interrupt vector is shared with an LSI Logic adapter, which causes Windows guest operating systems to become non-responsive.
  • Virtual Machine Might Stop Responding for Few Minutes When Removing Snapshot
    Virtual machine might stop responding with an message User logged event: Remote console on <generic_virtual_machine_name> disconnected for few minutes when a secondary snapshot file is deleted during the copying of large files. This fix resolves this issue.

Security Issues

  • OpenSSL Binaries Replaced
    This fix updates the third party OpenSSL binaries packaged in the VMware-esx-uwlibs RPM to RHEL 3 OpenSSL version 0.9.7.a.33.24. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2007-3108, and CVE-2007-5135 to the security issues fixed in RHEL 3 OpenSSL version 0.9.7.a.33.24.
  • samba Security Update
    This fix upgrades samba package versions to samba-3.0.9-1.3E.15vmw.i386.rpm , samba-client-3.0.9-1.3E.15vmw.i386.rpm , and samba-common-3.0.9-1.3E.15vmw.i386.rpm. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-1105 to the security issue fixed in this update.

Miscellaneous Issues

  • VmPerl Perl Libraries Installation Fails on HP ProLiant Platform
    Installing ESX Server 3.0.x on HP ProLiant Platform prevents VmPerl Perl libraries not to be installed. This issue is resolved by synchronizing the machine time with the makefile time for installing the VmPerl Perl libraries. The makefile time is found in the /tmp/api-config0/control-only/make.log file.
  • ESX Server 3.0.3 Displays a SysAlert Warning Message on Stepping B0, B1, B2, and BA of Quad-Core AMD Opteron 8300 Series and 2300 Series Processor Families
    A SysAlert warning message cpu not supported message is displayed on stepping B0, B1, B2, and BA of Quad-Core AMD Opteron 8300 series and 2300 series processor families on ESX Server 3.0.3. ESX Server 3.0.3 supports only systems on B3 stepping processors of AMD Opteron 8300 series and 2300 series processor families.

Top of Page