VMware

VMware ESX Server 3.0.3 Update 1 Release Notes

ESX Server 3.0.3 Update 1 | 8 March 2010 | 231127

Last Document Update: 8 March 2010

The release notes cover the following topics:

What's New in the ESX Server 3.0.3 Update 1 Release

The ESX Server 3.0.3 Update 1 release is a patch rollup release containing no new features, or enhancements. This release is provided as an ISO deliverable and through a tarball.
The ESX Server 3.0.3 Update 1 release is compatible with the ESX Server 3.0.3 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. To view release notes for prior releases, click the following links:

ESX Server Releases

  • ESX Server 3.0.3 (HTML)
  • 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

Before You Begin

See the Hardware Compatibility Lists at http://www.vmware.com/resources/compatibility before installing ESX Server 3.0.3 Update 1. The Hardware Compatibility Lists provide details on the compatibility of current and previous versions of ESX Server, VirtualCenter, and the VI Client. Verify that your servers, I/O devices, storage devices, guest operating systems, management agents, and backup software are compatible. The Hardware Compatibility Lists also address the minimum requirements and scaling limits associated with ESX Server 3.0.3 Update 1. To view a guide, click one of the following links:

  • Backup Software Compatibility Guide for ESX Server 3.0.x (PDF)
  • Guest Operating System Installation Guide (PDF)

Installation Notes

  • You should read the Installation and Upgrade Guide (PDF) for step-by-step guidance on installing and configuring ESX Server and VirtualCenter.
    Although the installations are straightforward, several subsequent configuration steps are essential. In particular, read:
    • Licensing section in the Installation and Upgrade Guide (PDF)
    • Networking section in the Server Configuration Guide (PDF)
    • Security section in the Server Configuration Guide (PDF) for firewall ports
  • If you are upgrading an existing ESX Server installation (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 Update 1, 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 to ESX Server 3.0.3 Update 1

This release supports upgrading from ESX Server 3.0.3 to ESX Server 3.0.3 Update 1. You should review the detailed upgrade instructions and guidelines provided in the Installation and Upgrade Guide (PDF).

To upgrade your ESX Server 3.0.3 host to ESX Server 3.0.3 Update 1, follow one of these supported upgrade paths:

Upgrade type ESX Server
2.5.4 and 2.5.5
ESX Server
3.0.0 and 3.0.1
ESX Server
3.0.2 and 3.0.2 Update 1
ESX Server 3.0.3
and
ESX Server 3.0.3 with any patches
Tarball No No No Yes
ISO image No No No Yes

 

Note: Users running unsupported ESX Server releases should upgrade to the nearest supported release and then upgrade to ESX Server 3.0.3 Update 1.

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

  • To upgrade an ESX Server 3.0.3 host to ESX Server 3.0.3 Update 1 by using a tarball, see the Upgrading from a Tarball section of the Installation and Upgrade Guide (PDF).
  • To upgrade an ESX Server 3.0.3 host to ESX Server 3.0.3 Update 1 by using the ESX Server 3.0.3 Update 1 ISO, see the Graphical installer from CD section or the Text-mode Installer from CD section of the Installation and Upgrade Guide (PDF).

Updated RPMs and Security Fixes

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

Top of Page

Upgrading from ESX Server 3.0.3 Update 1 to ESX Server 3.5 or ESX Server 4.0

From ESX Server 3.0.3 Update 1, you should either upgrade to ESX Server 3.5 Update 2 and later update releases, or should upgrade to ESX Server 4.0 and later update releases.

Top of Page

Compatibility of ESX Server 3.0.3 Update 1 with VMware VirtualCenter

ESX Server 3.0.3 Update 1 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 Update 1

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

To run VMware Update Manager on ESX Server 3.0.3 Update 1, 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>
New Value: <SupportedBaseHostVersion>3.0.3</SupportedBaseHostVersion>

Note:  If the value of the SupportedBaseHostVersion tag  is already set to 3.0.3 in the vci-integrity.xml file, do not change the value.

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 Update 1.

Note: You cannot use VMware Update Manager to upgrade from ESX Server 3.0.3 Update 1 to ESX Server 3.5.x. You can upgrade from ESX Server 3.0.3 Update 1 to ESX Server 3.5.x by using only the CD-ROM or tarball.  

Top of Page

Patches Contained in this Release

This release contains all bulletins that were released for the ESX Server software prior to the release date of this product. See the VMware Download Patches page or click on the name of a bulletin for more information on the individual bulletins.

ESX Server 3.0. 3 Update 1 fixes new issues (see the Resolved Issues section) and these issues are also resolved in the following individual patch bundles:

ESX Server 3.0.3 Update 1 contains the fixes from all the following patches released after ESX Server 3.0.3:

Top of Page

Resolved Issues in ESX Server 3.0.3 Update 1

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>

  • Virtual machines on NFS volumes might stop responding and display an error


    Virtual machines containing swap files on NFS volumes might stop responding and display the vmk: vcpu-0:Unable to read swapped out PPN(0x34890) from swap slot(0x106a0d1) error. This issue occurs due to invalid user privileges on NFS volumes. The issue is fixed in this release.

  • Security update to net-snmp, net-snmp-utils, and net-snmp-libs

    The service console package is updated for net-snmp, net-snmp-utils, and net-snmp-libs to version net-snmp-5.0.9-2.30E.28. This net-snmp update fixes a divide-by-zero flaw in the snmpd daemon. A remote attacker could issue a specially crafted GETBULK request that could cause the snmpd daemon to fail. This vulnerability was introduced by an incorrect fix for CVE-2008-4309.
    The Common Vulnerabilities and Exposures Project (cve.mitre.org) has assigned the name CVE-2009-1887 to this issue.

    Note: After installing the patch ESX303-200808401-SG, running the snmpbulkwalk command with the parameter -CnX results in no output, and the snmpd daemon stops. The issue is fixed in this release.

  • VMware Tools service might fail to start when upgrading VMware Tools


    Fixes an issue where the VMware Tools service might fail to start when installing or upgrading VMware Tools in a virtual machine.

  • Security update to libxml2 packages

    The updated libxml2 packages fix the following security issues in the ESX service console:

    • A stack overflow flaw was found in the way libxml processes the root XML document element definition in a DTD. A remote attacker could provide an XML file, which if opened by a local user, might cause a denial-of-service application failure. The Common Vulnerabilities and Exposures Project (cve.mitre.org) has assigned the name CVE-2009-2414 to this issue.
    • Multiple use-after-free flaws was found in the way libxml parses the Notation and Enumeration attribute types. A remote attacker could provide an XML file, which if opened by a local user, might cause a denial-of-service application failure. The Common Vulnerabilities and Exposures Project (cve.mitre.org) has assigned the name CVE-2009-2416 to this issue.

  • Security update to BIND

  • An updated BIND package fixes a security issue in the ESX service console. A flaw was found in the way BIND handles dynamic update message packets containing the ANY record type. A remote attacker could use this flaw to send a specially crafted dynamic update packet that could cause a denial-of-service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-0696 to this issue.

  • Security updates to Python package

    Service console updates are provided for the Python package, which upgrades the RPM to python-2.2.3-6.11.i386.rpm. The updated Python package fixes multiple security issues in the ESX Server service console. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2008-1679, CVE-2008-1887, CVE-2008-2315, CVE-2008-3142, CVE-2008-3143, CVE-2008-3144, CVE-2008-4864, and CVE-2008-5031 to these issues.

  • Includes Scripts RPM

    Provides all required scripts to use ESX 3.0.3 Update 1 as the baseline version.

Top of Page

Known Issues in ESX Server 3.0.3 Update 1

† denotes the issues documented in previous releases

  • 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 results in 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 continues to operate normally after No option is selected.
  • Scripted install fails while using Spanning Tree Protocol when 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