VMware

VMware Infrastructure 3 Release Notes

Note: An issue has been discovered by many VMware customers and partners with ESX Update 2 (build number 103908) and ESXi 3.5 Update 2 (build number 103909) where Virtual Machines fail to power on or VMotion successfully. This problem began to occur on August 12, 2008 for customers that had upgraded to ESX 3.5 Update 2. The problem is caused by a beta release product expiration that was mistakenly left enabled for the release build. New installations of build number 110268 of ESX Server 3.5 Update 2 will not experience this issue. For more information, see KB 1006716.

 

VMware ESX Server 3.5 Update 2 | 13 AUG 2008 | Build 110268

VMware Infrastructure Management Installer | 25 JUL 2008 | Build 104263 (English Only Build)
VirtualCenter 2.5 Server Update 2 | 25 JUL 2008 | Build 104215
Virtual Infrastructure Client | 25 JUL 2008 | Build 104215

VMware Infrastructure Management Installer | 25 JUL 2008 | Build 104265
VirtualCenter Server 2.5 Update 2 | 25 July 2008 | Build 104217
Virtual Infrastructure Client | 25 July 2008 | Build 104249

See Selecting the Appropriate VMware Infrastructure Management Installer Build for information.

Last Document Update: 26 AUG 2008

Check frequently for additions and updates to these release notes.

 

These release notes include the following topics:

Note: In many public documents, VMware ESX Server 3.5 is now known as VMware ESX 3.5 and VMware ESX Server 3i version 3.5 as VMware ESXi 3.5. These release notes continue to use the previous convention to match the product interfaces and documentation. A future release will update the product names.

What's New

Note: Only fixes relating to the beta release product expiration problem described above have been made in build 110268. No other changes are included in this build compared to previous builds of Update 2.

The following information provides highlights of some of the enhancements available in this release of VMware Infrastructure 3:

Not all combinations of VirtualCenter and ESX Server versions are supported and not all of these highlighted features are available unless you are using VirtualCenter 2.5 Update 2 with ESX Server 3.5 Update 2. See the ESX Server, VirtualCenter, and Virtual Infrastructure Client Compatibility Matrixes for more information on compatibility.

Features

  • Windows Server 2008 support – Windows Server 2008 (Standard, Enterprise, and Datacenter editions) is supported as a guest operating system.  With VMware memory overcommit technology and the reliability of ESX Server, you can maximize virtual machine density with this new guest operating system to achieve the highest ROI. Guest operating system customizations and Microsoft Cluster Server (MSCS) are not supported with Windows Server 2008.
  • Enhanced VMotion Compatibility – Simplifies VMotion compatibility issues across CPU generations. Enhanced VMotion compatibility (EVC) automatically configure server CPUs with Intel FlexMigration or AMD-V Extended Migration technologies to be compatible with older servers. After EVC is enabled for a cluster in the VirtualCenter inventory, all hosts in that cluster are configured to ensure CPU compatibility for VMotion. VirtualCenter does not permit the addition of hosts that cannot be automatically configured to be compatible with those already in the EVC cluster.
  • Storage VMotion – Storage VMotion from an FC/iSCSI datastore to another FC/iSCSI datastore.  This support is also extended on ESX Server/ESX Server 3i 3.5 Update 1.
  • VSS quiescing support – When creating quiesced snapshot of Windows Server 2003 guests, both filesystem and application quiescing are supported. With Windows Server 2008 guests, only filesystem quiescing is supported. For more information, see the Virtual Machine Backup Guide and the VMware Consolidated Backup 1.5 Release Notes.
  • Hot Virtual Extend Support – The ability to extend a virtual disk while virtual machines are running is provided. Hot extend is supported for vmfs flat virtual disks that do no have snapshots opened in persistent mode.
  • 192 vCPUs per Host – VMware now supports increasing the maximum number of vCPUs per host to 192 given that the maximum number of Virtual Machines per host is no more than 170 and that no more than three virtual floppy devices or virtual CDROM devices are configured on the host at any given time. This support is also extended on ESX Server 3.5 Update 1.

Hardware Enablement and Management:

  • 8Gb Fiber Channel HBAs – Support is available for 8Gb fiber channel HBAs. See the I/O Compatibility Guide for ESX Server 3.5 and ESX Server 3i for details.
  • SAS arrays – More SAS array configurations are now supported.  See the Storage/SAN Compatibility Guide for ESX Server 3.5 and ESX Server 3i for details.
  • 10 GbE iSCSI Initiator – iSCSI over a 10GbE interface is supported. This support is extended on ESX Server 3.5 Update 1, ESX Server version 3.5 Update 1 Embedded and ESX Server version 3.5 Update 1 Installable.
  • 10 GbE NFS Support – NFS over a 10GbE interface is supported.
  • IBM System x3950 M2 – x3950 M2 in a 4-chassis configuration is supported, complete with hardware management capabilities through multinode Intelligent Platform Management Interface (IPMI) driver and provider. Systems with up to 32 cores are fully supported.  Systems with more than 32 cores are supported experimentally.
  • IPMI OEM Extension Support – Execution of IPMI OEM extension commands is supported.
  • System Health Monitoring Through CIM Providers - More Common Information Model (CIM) providers are added for enhanced hardware monitoring, including storage management providers provided by QLogic and Emulex.  LSI MegaRAID providers are also included and are supported experimentally.
  • CIM SMASH/Server Management API The VMware CIM SMASH/Server Management API provides an interface for developers building CIM-compliant applications to monitor and manage the health of systems.  CIM SMASH is now a fully supported interface on ESX Server 3.5 and VMware ESX Server 3i.
  • Display of System Health Information – More system health information is displayed in the VI Client for both ESX Server 3.5 and VMware ESX Server 3i.
  • Remote CLI – Remote Command Line Interface (CLI), which was previously supported only on ESX Server 3i, is now supported on both Update 2 for ESX Server 3i version 3.5 and Update 2 for ESX Server 3 version 3.5. For more information on Remote CLI, see the Remote Command-Line Interface Installation and Reference Guide for more information.

Management Agents Support

  • HP Management Agents – HP Insight Management Agents provide server management capabilities for ESX Server hosts installed on supported server platforms.  A new 8.1 version is now supported.

Guest Operating System Support

  • Solaris10 U5 - Both the 32-bit and 64-bit versions are supported.
  • SUSE Linux Enterprise Server 10 SP2 - Both the 32-bit and 64-bit versions are supported. The 32-bit version supports the VMware Virtual Machine Interface (VMI) and so is performance-optimized for VMware environments.
  • Ubuntu 8.04 - Both the 32-bit and 64-bit versions are supported. The 32-bit version supports the VMware Virtual Machine Interface (VMI) and so is performance-optimized for VMware environments.

Service Console, Driver, and Library Updates

  • Service Console Operating System Update - The ESX Server Console operating system has been updated to RHEL 3.0 U9.  See the document Updated RPMs and Security Fixes for detailed information.
  • Driver Updates - The tg3 driver has been updated to version 3.81c.  The megaraid_sas driver has been updated to version 00.00.03.19.
  • Library Update - StoreLib has been updated to version 2.51.

VMware High Availability (HA)

VirtualCenter 2.5 update 2 adds full support for monitoring individual virtual machine failures based on VMware tools heartbeats. This release also extends support for clusters containing mixed combinations of ESX and ESX Server 3i hosts, and minimizes previous configuration dependencies on DNS.

VirtualCenter Alarms

VirtualCenter 2.5 Update 2 extends support for alarms on the overall health of the server by monitoring the health of each of the individual system components, such as memory and power supplies. You can now configure alarms to trigger when host health degrades.

Guided Consolidation Enhancements

Guided Consolidation now provides administrators with the ability to filter the list of discovered systems by computer name, IP address, domain name or analyzing status. Administrators can also choose to explicitly add physical hosts for analysis, without waiting for systems to be autodiscovered by the Consolidation wizard. Systems can be manually added for analysis by specifying either a hostname or IP address. Multiple hostnames or IP addresses, separated by comma or semi-colon delimiters, can also be specified for analysis. Systems can also be manually added for analysis by specifying an IP address range or by importing a file containing a list of hostnames or IP addresses that need to be analyzed for consolidation. Guided Consolidation also allows administrators to override the provided recommendations and manually start the conversion wizard.

Live Cloning of Virtual Machines

With VirtualCenter 2.5 Update 2, you can create a clone of a powered-on virtual machine without any downtime to the running virtual machine. Therefore, administrators are no longer required to power off a virtual machine to create a clone of it.

Windows Single Sign-on Support

You can now automatically authenticate to VirtualCenter using your current Windows domain login credentials on the local workstation, if the credentials are valid on the VirtualCenter server. This capability also supports logging in to Windows using Certificates and Smartcards. Windows single sign-on support can be used with the VI Client or the VI Remote CLI to make sure that scripts written using the VI Toolkits can take advantage of the Windows credentials of your current session to automatically connect to VirtualCenter. To enable single sign-on support, see KB 1006611.

Plug-In Updates

This release of the VMware Infrastructure 3 software suite also includes the following:

Top of Page

Prior Releases of VMware Infrastructure 3

Features and known issues from prior releases of VMware Infrastructure 3, which include ESX Server 3.x and VirtualCenter 2.x releases, are described in the release notes for each release. To view release notes for prior releases of VMware Infrastructure 3 components, click one of the following links:

ESX Server Releases

VirtualCenter Releases

Top of Page

Before You Begin

Note: If you are installing this release from anything other than physical DVD media, see the knowledge base article Filenames over 64 characters in ESX Server ISO image may get truncated during content extraction (KB 1005283) for important information on a known installation issue.

ESX Server, VirtualCenter, and Virtual Infrastructure Client Compatibility

The ESX Server, VirtualCenter, and Virtual Infrastructure Client Compatibility Matrixes guide provides details on the compatibility of current and previous versions of VMware Infrastructure 3 components, including ESX Server, VirtualCenter, and the VI Client.

Installation Notes for This Release

See the ESX Server Compatibility Guides before installing this software. You must verify that your server, I/O, storage, guest operating system, management agent, and backup software needs are compatible. These guides also address 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.5 and ESX Server 3i (PDF)
  •  I/O Compatibility Guide for ESX Server 3.5 and ESX Server 3i (PDF)
  • Storage/SAN Compatibility Guide for ESX Server 3.5 and ESX Server 3i (PDF)
  • Backup Software Compatibility Guide for ESX Server 3.5 and ESX Server 3i (PDF)

Read the Installation Guide 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 the following:

Installing using the VMware Infrastructure Management Installer and Physical Media

New: For this release, the VMware Infrastructure Management Installer requires a DVD drive when you use physical media to install VMware Infrastructure software.

Selecting the Appropriate VMware Infrastructure Management Installer Build

There are two builds of VMware Infrastructure Management Installer available for download. Select one of the following options :

Virtual Infrastructure Client Installer Changes

The VI Client standalone installer (available from ESX Web Access) allows installation of the VMware Infrastructure Update service, which is used for updating and patching ESX Server 3i hosts. The standalone VI Client Installer  is now modified to allow optional installation of the VMware Infrastructure Update service so as to reduce unnecessary proliferation of this tool. Note that the VirtualCenter Unified Installer  (available as part of the VC 2.5 Update 2 download) now installs VMware Infrastructure Update service when you choose the VI Client installation option.

Upgrading or Migrating to VirtualCenter 2.5 Update 2

This release also supports upgrading from VirtualCenter 1.4.1, VirtualCenter 2.0.2 (including Update 1, Update 2, and Update 3), VirtualCenter 2.5, or VirtualCenter 2.5 Update 1 to VirtualCenter 2.5 Update 2. Review the detailed upgrade and migration instructions and guidelines that are provided in the Upgrade Guide.

Note: Previous versions of VMware Update Manager are not compatible with VirtualCenter 2.5 Update 2 and must be upgraded to VMware Update Manager 1.0 Update 2 during the installation process.

Upgrading or Migrating to ESX Server 3.5 Update 2

This release of ESX Server 3.5 Update 2 allows upgrades only from previously supported versions. The ESX Server 3.5 Update 2 Installer prompts you to perform an upgrade only when a previously supported version of ESX Server is found. See the Installation Guide for installation requirements and the Upgrade Guide for the Upgrade Support Compatibility Matrix.

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

Upgrade type ESX Server 2.5.4
and 2.5.51
ESX Server 3.0.1 2 ESX Server 3.0.22 ESX Server 3.5 ESX Server 3.5 Update 1
Tarball Yes Yes3 Yes4 Yes Yes
ISO image Yes Yes Yes Yes Yes
  1. For ESX Server 2.5.1, ESX Server 2.5.2, and ESX Server 2.5.3, upgrade first to ESX Server 2.5.4 and then upgrade to ESX Server 3.5 Update 2. Or upgrade to ESX Server 3.5 and then upgrade to ESX Server 3.5 Update 2.
  2. For ESX Server 3.0.0, upgrade first to ESX Server 3.0.1 or higher and then upgrade to ESX Server 3.5 Update 2 using an ISO image. Or upgrade to ESX Server 3.5 and then upgrade to ESX Server 3.5 Update 2.
  3. For ESX Server 3.0.1 Patch ESX-1003519 (See KB 1003519) must be applied first before performing an upgrade using the tarball.
  4. For ESX Server 3.0.2 Patch ESX-1003525 (See KB 1003525) must be applied first before performing an upgrade using the tarball.

For more information on more information on installation and upgrade methods, see the Upgrade Guide.

Updated RPMs and Security Fixes

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

Top of Page

Patches Contained in this Release

This release contains all patches for the ESX Server software that were released prior to the release date of this product. See the ESX Server 3.5 Patches download page or click on the name of a patch for more information on the individual patches.

ESX Server 3.5 Update 2 contains the following patches:

Previously Released Patches

New Patches in Update 2 (13 AUG 2008 | Build 110268 )

Top of Page

Known Issues

This section contains known issues for this release in the following subject areas:

New Issues with ESX Server 3.5 Update 2, Build 110268

The following issues unique to the replacement build of ESX Server 3.5 Update 2 (Build 110268) have been found:

Backup

  • Consolidate Helper Snapshots Might Not Be Removed Automatically
    In the ESX Server 3.5 Update 2 release, Consolidate Helper snapshots are created iteratively to minimize the amount of time a virtual machine is inactive during snapshot creation. As a result, the Consolidate Helper snapshots are now called Consolidate Helper-XXX and not just Consolidate Helper. When you use VMware Consolidated Backup 1.1 with ESX Server 3.5 Update 2, if vcbMounter encounters a failure during a snapshot delete operation, this temporary snapshot might be left behind. The vbCleanup.bat command does not delete this Consolidate Helper-XXX snapshot. You must manually delete it using VI Client. This issue does not exist in VMware Consolidated Backup 1.5.

CIM and API

  • Firewall on ESX Server 3.5 interferes with CIM indication support

    Outgoing HTTP connections are blocked by the firewall on ESX Server 3.5. This prevents indications from reaching the indication consumer.

    Resolution: In the Service Console, open an outgoing port for connections to the indication consumer, using the following command:
    esxcfg-firewall -o <port-number>,tcp,out,http

    To close a port for http in the firewall:
    esxcfg-firewall -c <port-number>,tcp,out,http

  • Some CIM classes do not work properly on IBM Multinode systems
    The following anomalies are seen. For the following classes, the EnumerateInstance operation returns one instance fewer than the Enumerate InstanceNames operation:

    • CIM_AssociatedSensor
    • CIM_MemberOfCollection
    For the following classes, the GetInstance operation fails for some instances. However, the EnumerateInstances operation succeeds.
    • CIM_HostedService
    • CIM_Sensor
    • CIM_SystemDevice
    • CIM_Slot
    • CIM_ElementConformsToProfile
    For the following classes, the EnumerateInstances and EnumerateInstanceNames operations fail to return any results:
    • CIM_OwningCollectionElement
    • CIM_RedundancySet
  • Operation RequestStateChange(RestoreDefaultThresholds) results in error
    In the ESX Server 3.5 release, the operation RequestStateChange(RestoreDefaultThresholds) results in the following error message for some sensors:
    CIM_ERR_FAILED: index out of bounds

    In spite of the error message, the CIMOM does restore the thresholds.

  • VI Client displays incorrect name for power supply redundancy sensor on HP servers
    When you connect to an ESX Server installation on an HP server system using VI Client, the VI Client incorrectly displays the power supply redundancy sensor on the server as a physical power supply source. For example, for an HP server with redundancy sensor that has two physical power supplies, the VI Client displays the redundancy sensor as Power Supplies for Power Supply 3.

  • Executing a CallMethod query on a CIM_RecordLog instance might fail
    In ESX Server 3.5 Update 2, executing a CallMethod query (cm) on a CIM_RecordLog instance might not succeed at all times. You can, however, clear system event log through a remote management console or interface.
  • Mandatory property MaxReadable,NominalReading,NormalMax,NormalMin and PollingInterval in class CIM_NumericSensor shows in-correct values
    The instances of CIM_NumericSensor have this set of properties: MaxReadable,NominalReading,NormalMax,NormalMin. When the actual sensor does not support values of these properties, they are displayed as 0, in CIM responses; instead of unspecified.
  • Changes to the sensor threshold are not reflected immediately
    If you change the sensor threshold through CIM, enumeration of the sensor might not return the new property values immediately. The changes take effect about a minute later.
  • On some Dell MLK hardware, the NumberOfBlocks property for OMC_Memory instance has a value of 0. This issue is under investigation.
  • On HP 380 G5 machines running ESX Server 3.5 Update 2 the IPMI board's IP address is not returned in response to CIM_IPProtocolEndpoint queries.
  • In the ESX Server 3.5 release, invoking the operation Reset() on numeric power supply sensors results in the following error message:
    CIM_ERR_FAILED: index out of bounds
    As a workaround, you can use the RequestStateChange(Reset) operation.
  • InvokeMethod(RequestStateChange) for either Sensor and SEL fails when you use the WS-Man protocol.
  • The ModifyInstance() call to change sensor threshold fails when you use the WS-Man protocol.
  • An ESX Server 3.5 host that has been upgraded to ESX Server 3.5 Update 2 does not report CIM_AssociatedSensor instances correctly. The EnumerateInstance() and Association() queries for CIM_AssociatedSensor do not return any instances. As a workaround, do a clean installation of ESX Server 3.5 Update 2, or do a clean installation of ESX Server 3.5 U1 and then upgrade to ESX Server 3.5 Update 2.
  • Indications do not work on ESX Server 3.5 Update 2 when you use the WS-Man protocol.
  • On IBM athena hardware, some OMC_DiscreteSensor instances are found to have incorrect device IDs (with -1 as the last segment of the device ID).
  • On servers with ESX Server 3.5 Update 2 installed, SLP reports "service:wbem" available on http port 5888. However, the default firewall settings prevent access to port 5888. To access the port, unblock the port in the firewall configuration.
  • On some servers, incorrect PECI temperature sensor readings might be reported. Incorrect values are shown in the VI Client and in the NominalReading property of CIM_Sensor instances for CPU PECI tic for Processor sensors.
  • On ESX Server 3.5 Update 2, instances of VMware_Account (a subclass of CIM_Account) show a SystemName property with a value of "0". The SystemName property should contain the BIOS UUID of the server.
  • The InvokeMethod(RequestPowerStateChange) fails when you use the WS-Man protocol.
  • The chassis intrusion indication is not available for IBM Athena servers.

Guest Operating Systems

VMware High Availability (HA)

  • NEW: HA network compliance check
    During the configuration of HA in VirtualCenter 2.5 Update 2, the Task & Events tabs might display the following error message and recommendation:

    HA agent on <esxhostname> in cluster <clustername> in <datacenter> has an error Incompatible HA Network:
    Consider using the Advanced Cluster Settings das.allowNetwork to control network usage.


    Starting with Virtual Center 2.5 Update 2, HA has an enhanced network compliance check to increase cluster reliability. This enhanced network compliance check helps to ensure correct cluster-wide heartbeat network paths. See KB 1006606 for details.
  • VI Client Might Show the Host as Not Responding During HA-DRS Cluster Operations
    During HA-DRS cluster operations like adding or removing a host from a DRS cluster or applying DRS recommendations, VI Client might show the host as "Not responding", even when the host IP can be reached.
    Workaround
    Disconnect the host from the HA-DRS cluster and reconnect it. This refreshes the system and VI Client reflects the configuration changes that you have made. If the VI Client again shows the host as Not Responding, disconnect the host from the HA-DRS cluster, remove the host, and add the host back to the same cluster.
  • Virtual Machine Migrations Are Not Recommended When the ESX Server Host Is Entering the Maintenance or Standby Mode
    No virtual machine migrations will be recommended (or performed, in fully automated mode) off of a host entering maintenance or standby mode, if the VMware HA failover level would be violated after the host enters the requested mode. This restriction applies whether strict HA admission control is enabled or not.
  • VMware HA Health Monitoring Does Not Show Rebooting in the Console After a Host Failover
    After a host failure, the VMware console displays an empty window when the Health Monitoring is enabled for an HA cluster. The console does not display the virtual machines rebooting.

    Workaround
    You must open a new console to see the virtual machines restarting after the failover.

Internationalization

All fields in the VI Client and the VI WebAccess support non-ASCII character input, except for the following limitations:

Non-ASCII Character Entry Limitations

  • Specifying a non-ASCII value as an input string is not supported by the remote command line interface (RCLI).
  • The name of the computer on which Virtual Infrastructure 3 or any of its components are installed must not contain non-ASCII characters.
  • The name of the computer or virtual machine where VirtualCenter Server is installed must not have a non-ASCII computer name or the installation of VirtualCenter Server will fail.
  • Use the default installation path names specified in the installer for all the components. Do not change the install path, because the installer does not support installation path names containing non-ASCII characters and extended-ASCII characters.
  • Datastore names, Virtual Network names, and Image file names (CD, DVD, and floppy drive) are restricted to ASCII characters only.
  • Message of the Day must use only ASCII characters.
  • Logging in to the VirtualCenter server is supported for user names with ASCII characters only (login account name on Windows).
  • Image customization might fail if non-ASCII characters are used.
  • Custom attribute names and values must use only ASCII characters.
  • To conform to the general Internet practice and protocols, the following cannot contain non-ASCII characters: host names, workgroup names, domain names, URLs, email addresses, SMTP server names, and SNMP community string.
  • Guest operating system customizations using ASCII encoding are supported but customizations using UTF-8 encoded native characters of Japanese, Chinese, or German have limited support. For customizations with non-ASCII owner, organization, username, or password, VirtualCenter and the sysprep tool must be hosted in the same locale as that of the Guest OS. This includes the scenario to use UTF-8 encoded answer file.

Non-ASCII Character Display Limitations

  • When managing a VirtualCenter Server with the VI Client running on different languages of Windows, you might see some characters displayed incorrectly because of the difference in language-specific support on Windows.
  • If an error message includes log locations or user names containing non-ASCII characters, it will not display correctly in the localized environment.
  • When you use the Import Wizard of VMware Converter, the date and time format is sometimes inconsistent with the current locale.
  • Unicode characters are displayed as '???' under the Status column and the Task Details of the Task View tab in the Japanese locale.
  • The Commands section on the Summary tab is not displayed properly.

Guided Consolidation Limitations

The Guided Consolidation tab is available only in the en_US locale.

Translation Issues

The following are known issues with translation in this release:

  • The Upgrade wizard is not translated.
  • Some messages originating from the ESX Server host are not translated.
  • Some localized interface layouts are not yet completed.

Other Internationalization Issues

The following additional issues have been identified:

  • Values used in the Run a Script action for an alarm might not display properly after restarting VirtualCenter server if the Virtual Infrastructure Client host OS language and VirtualCenter Server/Database host OS languages are different.
  • In the Simplified Chinese version of VI Web Access, the Cancel button does not have the correct text and the text on the button is displayed incorrectly.
  • NEW: Connecting to an ESX Server 3.5 Update 2 host through VirtualCenter will not upgrade a localized VI Client
    If you connect to an ESX Server 3.5 Update 2 host through VirtualCenter, the localized VI client in use will not be upgraded to the Update 2 version.
  • The VI Client Might Override the Language Preference Setting
    The VI Client Might Override the Language Preference Setting and display some messages in a language other than its primary language. It might display messages that are dynamically generated by the server (VirtualCenter Server and ESX Server) in the primary language set on the server. This issue does not occur if all the software is running in the language that corresponds to the locale of the operating system.
  • Wrong Text Appears on the Reinstall Wizard of the German VI Client
    The reinstall wizard displays wrong text in the German VI Client.
    The reinstall wizard shows the following text
    Der Installations-Assistent ermöglicht Ihnen, Virtual Infrastructure Client 2.5 zu reparieren oder zu entfernen., instead of The installation wizard will allow you to remove Virtual Infrastructure Client 2.5.
  • Links Containing Machine-Generated Virtual Machine Names Do Not Work

    When you use WebAccess to browse the datastore by clicking a link containing machine-generated virtual machine name (typically starting with a plus sign and ending with slash, for example +5paw55qE5qih5p2,/), the Web browser displays a blank page or returns a page not found error. You can, however, access such virtual machines using the VI Client.

Migration with VMotion

Miscellaneous

Networking

Server Configuration

Storage

Upgrade and Installation

VirtualCenter Upgrade and Installation

Virtual Machine Management

  • User with 'Create' Privileges Cannot Create Virtual Machines(KB 1004417)
  • Cloned Virtual Machines do not Contain DNS Suffix (KB 1004299)
  • Deploying Virtual Machine From a Template Fails With No Permission Error (KB 1004295)
  • Cloned Virtual Machines See the .vmdk File of the Source Virtual Machine (KB 1004176)
  • VMware Tools Custom Script Not Executed for Suspend or Shut Down Events (KB 1004390)
  • Virtual Machines Might Not Power on After a Failover When the Host Is Isolated
    Virtual machines might not start after a failover when a host is isolated and the isolation response is set to Guest Shutdown which is the default configuration for a cluster. This might occur on clusters with fewer than five nodes and can happen on virtual machines that take more time to complete the guest shutdown.
    Workaround
    Set the Isolation Response to either Leave powered on or Power off for clusters which have fewer than five nodes.
    To set the Isolation Response for a virtual machine, select the cluster, click the Edit Settings link, and select Virtual Machine Options under VMware HA. From the Isolation Response pop-up menu, select either Leave powered on or Power off options for the specific virtual machine.
  • I/O Might Stall on Virtual Machines During Firmware Upgrade
    When Virtual machines are running on a shared LUN that has heavy I/O workload, and if the firmware is upgraded using the storage management utility or if the storage controller is restarted, I/O might stall on any of the virtual machines.
    Messages similar to the following might appear in the vmkernel.log file:
    1:01:05:07.275 cpu2:1039)WARNING: FS3: 4785: Reservation error: Not supported
    SCSI: 4506: Cannot find a path to device vmhba1:0:125 in a good state. Trying path vmhba1:0:125.
    1:01:05:10.262 cpu3:1039)ALERT: SCSI: 4506: Cannot find a path to device vmhba1:0:125 in a good state. Trying path vmhba1:0:125.
    1:01:05:40.748 cpu1:1083)<6>mptbase: ioc0: LogInfo(0x30030108): Originator={IOP}, Code={Invalid Page}, SubCode(0x0108)
    1:01:05:40.930 cpu0:1024)Log: 472: Setting loglevel (via VSI) for module 'SCSI' to 5

VirtualCenter, VI Client, and Web Access Issues


Top of Page

Resolved Issues

This release includes fixes in the following subject areas:

Backup

  • Virtual Disks Size Can Be Changed While the Virtual Machine Is Powered On
    On powered on virtual machines that are running on ESX Server 3.5 Update 2, the size of the virtual disks can be changed by using the Provision Size control that is available when editing the virtual disk settings of virtual machines.
  • VMware Consolidated Backup Fails to Perform Backup of Non-Windows and Non-Linux Virtual Machine Disks
    VMware Consolidated Backup might fail to perform backup of non-Windows and non-Linux virtual machine disks with error messages similar to the following:
    [2008-02-06 12:28:07.234 'vcbMounter' 3076457280 error] Error: Other error encountered: Snapshot creation failed: Custom pre-freeze script failed.
    [2008-02-06 12:28:07.234 'vcbMounter' 3076457280 error] An error occurred, cleaning up...
    [2008-02-06 12:28:07.356 'SOAP' 3076457280 trivia] Sending soap request to
    [TCP:cs-tse-h20:443]: logout

    Starting with the ESX Server 3.5 Update 2 release, VMware Consolidated Backup performs backup of non-Windows and non-Linux virtual machine disks successfully, without taking their quiescent snapshot.
  • VirtualCenter Server Fails When Multiple VCB Proxy Servers Perform Simultaneous Backups
    When an SDK application performs a VM lookup by starting the search by index API, and the SQL Server gets into a deadlock during lookup, the VirtualCenter Server fails. For example, this occurs is when multiple VCB proxy servers are connected to the VirtualCenter Server and if the SQL Server gets into a deadlock during backup, the VirtualCenter Server fails with error statements similar to the following in the log file:
    [2008-04-03 00:06:29.636 'App' 4700 info] [VpxLRO] -- BEGIN task-internal-43561 -- -- vim.SearchIndex.findByIp -- 2C3A8FF6-30F9-4E68-9ACF-2A6EFBCE9609
    [2008-04-03 00:06:32.605 'App' 4700 error] [Vdb::IsRecoverableErrorCode] Unable to recover from 40001:1205
    [2008-04-03 00:06:32.605 'App' 4700 error] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Check database connectivity before restarting. Error: Error[VdbODBCError] (-1) "ODBC error: (40001) - [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction." is returned when executing SQL statement "SELECT id FROM vpx_vm WHERE uuid_bios = ? AND is_template = 0"
    [2008-05-23 08:15:35.252 'App' 44264 verbose] Backtrace:
    [2008-05-23 08:15:35.252 'App' 44264 info] Forcing shutdown of VMware VirtualCenter now
  • vcbSnapAll Fails to Display a Relevant Error Message When Incorrect Login Credentials Are Provided for the ESX Server Host
    An irrelevant message similar to the following when incorrect login credentials are provided for the ESX Server host:
    Could not retrieve a list of virtual machines to back up with the search criteria (name:<VMname>)
    Starting with this release, a suitable message similar to the following is displayed:
    Other error encountered: Host address lookup for server <name> failed: Unknown host Could not retrieve a list of virtual machines to back up.
  • VCB Fails to Back Up Virtual Machines When a User Account Is Not Assigned the Disk Lease Privilege on the Root of the Object Tree
    This release resolves an issue where backups in SAN mode fail when the VirtualMachine.Config.DiskLease privilege is assigned only to the virtual machines that are backed up using VMware Consolidated Backup (but not to the root of the object tree in VirtualCenter).

CIM and API

  • HTTP 1.1 Chunking Fails
    This release resolves an issue in the previous implementation of the Small Footprint CIM Broker (SFCB) would fail if a client tried sending a chunked message. The SFCB was sending an acknowledgment to the wrong socket when HTTP 1.1 chunking was being used. This caused a failure in the transfer, since the sending client never received the proper acknowledgment.
  • System Health Information Is Now Monitored for Each Node of a multinode System
    The Intelligent Platform Management Interface (IPMI) based system health monitoring system now reports individual health information for each node of a multinode clustered system. Health information is displayed in the VI Client and can also be monitored by third party CIM-based management consoles.
  • VI Client Displays the Manufacturer and Model Name of the Server In the Health Status Tree
    The CIM window in the VI Client displays the manufacturer and model name of the server in the health status tree, in addition to the other hardware related information.
  • Web Services Description Language (WSDL) and API Reference Documentation Incorrectly Specify Properties of Type MethodFault[]
    This release resolves an issue where the web services description language (WSDL) and API reference documentation refers to the type of certain properties as MethodFault[], instead of LocalizedMethodFault[]. As a result, WSDL based clients are unable to de-serialize responses from the server that contain properties of type MethodFault[]. The fix updates the WSDL and API reference documentation for faults to specify LocalizedMethodFault[] rather than MethodFault[].
  • Adds vmkgdb And vmkdump_extract to DDK devtools.
    This release provides vmkgdb and vmkdump_extract tools that work with UserWorld coredumps to extract and analyze core dumps.
  • Custom Virtual Disk Name Displayed in the VI Client
    This release incorporates custom virtual disk names into the name of the storage displayed under Configuration > Health Monitoring in the VI Client.
  • This release resolves an issue where CIM queries for VMware_LatchedHealthState and VMware_RollupHealthState did not work in the Release Candidate build of ESX Server 3.5 Update 2.

Guest Operating Systems

  • NEW: PXE installation of guest operating system fails
    This release resolves an issue in the previous release where PXE installation failed for guest operating systems with the vmxnet or Enhanced vmxnet drivers. Starting with this release, PXE GOS installation works as expected for the e1000, flexible, and Enhanced vmxnet drivers.

VMware High Availability (HA)

  • Using VMware HA in conjunction with VMware ESX Server 3i hosts has the following restrictions, swap space must be enabled on individual ESX Server 3i hosts, and only homogeneous (non-mixed) clusters are supported at this time.
  • ESX Server 3i Hosts Without Swap Enabled Cannot be Added to an HA Cluster (KB 1004177)
  • Limited configurations are supported for VMware HA and ESX Server 3i hosts (KB 1004656)
  • DNS Resolution Is No Longer a Requirement to Enable VMware High Availability on ESX Server Hosts
    Previously, enabling VMware High Availability required DNS resolution of all ESX Server hosts in a High Availability cluster. This was done using configuring DNS records or by adding all of the host names and IP addresses to the /etc/hosts file on each server.
    Starting with the ESX Server 3.5 Update 2 release, DNS resolution or /etc/hosts file entries are no longer required to configure High Availability. The host name and IP address information are now provided by the managing VirtualCenter Server.
    Note: For ESX Server 3i systems, define a host name on the ESX Server 3i host by performing the following steps in the ESX Server 3i console user interface:
    1. Press F2 to Customize System.
    2. Choose Configure Management Network.
    3. Choose DNS configuration.
    4. Select the Use the following DNS Server addresses and hostname radio button.
    5. Replace localhost host name with a unique valid name.

Internationalization

  • VirtualCenter Server Service Now Allows For Non-ASCII Characters in DRS Rule Names and Advanced Options Settings
    In the previous release, VirtualCenter would fail to start if DRS rule names or advanced options settings contained non-ASCII characters. This is fixed in this release.
  • Text Truncated on the Network Access Page of the Add Network Wizard While Using Japanese VI Client
    Details of Networks (IP address) displayed on the Network Access page are truncated while accessing VirtualCenter using the Japanese VI Client.
    The Network Access window appears in the Add Network wizard when you select Add Networking from the Networking option under the Configuration tab.
    Workaround
    You can view the network information (IP address) in the Network Adapters page. Select Configuration>Networking>Properties>Network Adapters to display the Networks.

Migration with VMotion

  • The Power On Task Scheduled on Virtual Machines Fail After Migration (KB 1004091)
  • Storage VMotion on Virtual Machine with I/O Intensive Workload May Result Incorrectly in a Timeout Error (KB 1003276)
  • Virtual machine CPU usage spikes and remains abnormally high after VMotion in a VMware DRS enabled cluster (KB 1003638)
  • Virtual Machines with Large Memory Size Fails to Migrate when Migrate.MemChksum is Enabled
    Migrating virtual machines fails when one of the following occurs:
    • You enable Migrate.MemChksum (value is set to 1) on both source and destination ESX hosts.
    • The virtual machine has a memory size of more than 4GB.
  • The migration times out and the following error appears in the vmware.log file:
    MigrateStatusFailure: Failed waiting for data. Error bad0007. Bad parameter>
    and the VI Client reports the following error: A general system error occurred: Failed waiting for data. Error bad0007. Bad parameter.
    Workaround
    Configure the value of the following variables in the source and the destination ESX hosts. The variables are available under Configuration > Advanced Settings > Migrate:
    • Migrate.PageInTimeoutResetOnProgress: Set the value to 1.
    • Migrate.PageInProgress: Set the value to 30, if you get an error even after configuring the Migrate.PageInTimeoutResetOnProgress variable.

Miscellaneous

  • Guided Consolidation Feature Fails to Consolidate the Datacenter When Non-ASCII Characters are Used In Machine Names, Workgroup Names, or Windows Domain Names
    When non-ASCII characters are used in machine names, workgroup names, or Windows domain name, and if the Guided Consolidation feature is used, the VirtualCenter Server fails to consolidate the datacenter. An error message similar to the following appears:
    VirtualCenter must gather more information to enumerate the domains and workgroups in the enterprise. This may take several minutes. Try again later.
    Workaround: Starting with the Virtual Center 2.5 Update 2 release, to analyze a machine with non-ASCII characters in its name or its workgroup's name, manually add the machine's IP address in the Guided Consolidation wizard.
    For releases prior to VirtualCenter Server 2.5 Update 2, rename machine names, workgroup names, and Windows domain names to use only ASCII characters. In addition, remove machine names, workgroup names, and Windows domain names that have non-ASCII characters from the data collector’s Microsoft Access database, by performing the following steps:
    1. To prevent the VirtualCenter Server from locking up the Microsoft Access database of the data collector, and to prevent the VirtualCenter Server from attempting to start the VMware Capacity Planner service, stop the VMware VirtualCenter Server Windows service.
    2. To prevent the data collector from attempting to modify the Microsoft Access database, stop the VMware Capacity Planner Service Windows service.
    3. Open the embedded data collector database (AOGCapPlan.mdb) in Microsoft Access 2000 or a later version.
    4. From the CoreGroups table, in the Tables tab, delete the rows that have non- ASCII characters.
    5. Save the changes, and close Microsoft Access.
    6. Start the VMware VirtualCenter Server Windows service.
  • The Administrator Does Not Have Access to Virtual Machine Hard Disk Settings When the Access is Restricted Only to a Single Virtual Machine
    If the administrator has access only to a single virtual machine and the permissions on ESX are not propagated, the administrator cannot view or edit the virtual machine hard disk settings available under Edit Settings > Hardware > Hard Disk.
    The following error appears when the administrator tries to edit the settings:
    Exception of type Vmomi.Fault.NoPermission.
    In this release, you can view the hard disk settings. To extend the hard disk size or edit the settings, you must have additional permissions at the datacenter.

Networking

  • SNMP Trap Messages for Predictive Failures Disks Are Not Appropriate
    The SNMP trap messages for predictive failure disks are changed from messages similar to VMWARE-ENV-MIB::vmwEventDescription.4 = STRING: "Drive 1 in enclosure 32 on controller 0 - ONLINE"  to messages similar to  VMWARE-ENV-MIB::vmwEventDescription.4 = STRING: "Drive 1 in enclosure 32 on controller 0 - PREDICTIVE FAILURE".
  • ESX Server Host Crashes When Unloading Bnx2x Driver
    This release resolves an issue where the ESX Server host crashes when unloading the Bnx2x driver. An error message similar to the following might be displayed:
    VMware ESX Server [host name]
    Exception type 14 in world 1027:idle3 @ 0xa575d7
  • Updates the Samba Package Distributed With the ESX Server Service Console
    This release fixes an issue with the heap-based overflow flaw found in the Samba package that allows remote attackers to execute arbitrary code.
    Thanks to Alin Rad Pop of Secunia Research for identifying and reporting this issue.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-1105 to this issue.

Server Configuration

  • .config File Missing In the ESX Server Service Console
    Previously, the ESX Server service console kernel-source package omitted the .config file that directs which Linux kernel options are to be enabled. The kernel-source package now provides a .config file, which enables OEM Management Agent packages like Dell OpenManage, HP Insight Manager, and IBM Director to build their kernel modules.
  • Updates to the Service Console to 2.4.21-57 (RHEL3U9)
    This fix upgrades the service console kernel version to kernel-2.4.21-57.EL. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2007-5001, CVE-2007-6151, CVE-2007-6206, CVE-2008-0007, CVE-2008-1367, CVE-2008-1375, CVE-2006-4814, and CVE-2008-1669 to the security issues fixed in kernel-2.4.21-57.EL.
  • ESX Server Installer Does Not Create vmfs and vmkcore Partitions Correctly (KB 1004075)
  • Ramchecker Service Fails to Start on the ESX Server 3.5 Versions
    The Ramchecker utility is not supported, and does not work on ESX Server 3.5 versions. Starting with this release, to prevent the installation of the Ramchecker utility, the Ramchecker service is removed from the VMware-esx-lnxcfg RPM, and the Ramchecker binary is removed from the VMware-esx-apps RPM.
    On ESX Server 3.5 and ESX Server 3.5 Update1 systems, the Ramchecker service fails to start, with an error message similar to the following:
    Starting ramchecker /usr/lib/vmware/bin/ramcheck: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Error 28
  • Connecting a Remote CD-ROM or Floppy Drive to a Virtual Machine Fails With No Permission Error (KB 1004327)
  • -l Command Line Option Can Be Used In the esxtop Utility to Optimize CPU Utilization
    When several LUNs are added to an ESX Server and if the esxtop utility is used for collecting storage statistics, esxtop uses several CPU cycles to access VSI nodes and load meta information of adapters, targets, channels, luns, vcpus, nics, paths, worlds and so on for every update. The -l command line option can be used with esxtop to operate the esxtop utility in the lock mode. In the lock mode, CPU utilization is optimized as esxtop copies meta information from the previous snapshot instead of accessing the VSI nodes for every update.
    However, in the lock mode, storage statistics of new entities are not displayed.
  • "Permissions Issue Vmomi.Fault.NoPermission" error
    With VirtualCenter 2.5 and VirtualCenter 2.5 Update 1, if users are given the virtual machine power/virtual machine administrator user role at a resource pool level, they would get an Error message box with "Vmomi.Fault.NoPermission" while editing the virtual machine settings. This has been fixed in VirtualCenter 2.5 Update 2.
  • Dell Recovery CD Fails when recovery process is executed with a Virtual Floppy drive connected (KB 1004494)
  • CPU Affinity Settings do not Take Effect
    This release resolves an issue where CPU affinity settings do not take effect until the virtual machine is restarted.
  • ESX Server Displays Error on a Purple Screen During Memory Intensive Operations
    During memory intensive operations, ESX Server fails and displays the following error on a purple screen: Exception Type 14 in world.... This release fixes the issue.

Storage

  • Path Failover Might Not Complete Successfully with LSI3444E Under High Stress

    To ensure the IBM DS3200 SAS storage array provides proper path failover during heavy I/O in a VMware environment, you must reconfigure the Remove Device Missing Delay (RDMD) timer value to 10 seconds and the I/O Device Missing Delay (IODMD) timer value to 0 seconds in the BIOS for each SAS HBA. Failure to do so might cause I/O timeouts in the event of a SAS HBA failure or cable disconnect. The following error messages might be displayed in /var/log/vmkernel:

    Jan 29 10:59:29 stgbladeh101 vmkernel: 0:21:06:58.523 cpu1:1062)<4>mptscsih: ioc1: Attempting task abort on id=0! (sc=0x3e229200)
    Jan 29 10:59:29 stgbladeh101 vmkernel: 0:21:06:58.523 cpu1:1062)<4>mptscsih: ioc1: Abort ctx2abort=e00a1
    Jan 29 10:59:29 stgbladeh101 vmkernel: 0:21:06:58.537 cpu1:1062)LinSCSI: 3201: Abort failed for cmd with serial=31623, status=bad0001, retval=bad0001

    This issue is fixed in this release. You can retain the LSI default settings in the BIOS.

  • Virtual Machines Cannot Share a Raw LUN By Using Two Different RDM Files Unless RDM Filters Are Turned Off
    Starting with the ESX Server 3.5 Update 2 release, by default, two virtual machines cannot share a raw LUN by using different RDM files.
    When using the Microsoft Cluster Service, it might be required that two RDM files link to the same raw LUN. To enable two RDM files to link to the same LUN, RDM filters should be turned off in hostd and in the VirtualCenter Server by performing the following steps:

    1. To turn off the RDM filter in hostd, add the following lines in the /etc/vmware/hostd/config.xml file and restart hostd:
      <plugins>
             <solo>
                <rdmfilter>
                    <UsedAsVmRdm>false</UsedAsVmRdm>
                </rdmfilter>
             </solo>
          </plugins>

    2. To turn off the RDM filter in the VirtualCenter Server, in the VI Client, choose Administration ->Virtual Center Server Configuration, select Advanced Settings and add a row to set the vpxd.filter.rdmFilter variable to false.
  • Hot Addition/Deletion of LUNs on Virtual Machines as Raw Device Mappings (RDMs) Might Fail With Error Messages
    The following error message might be logged in hostd logs:

    Operation failed due to concurrent modification by another operation

    The above message happens in conjunction with another error: Foundry operation failed with system error: Device or resource busy while Hot Adding/Removing of RDMs
  • I/O Errors Occur after Device Is Removed from IBM DS3200 while Using LSI 3444E Adapter (KB 1004313)
  • VI Client displays the Current Firmware Version Used By the Server
    The Health tab in the VI Client displays the current firmware version that is being used by the ESX Server system.
  • VMKlinux Runs Out of Memory when Using an mptsas System with More Than 128 LUNs (KB 1004403)
  • File System Mount Info In the Managed Object Browser of a VirtualCenter Server Reflects VMFS or NFS Datastore Changes
    This release fixes an issue where the VMFS or NFS datastore changes fail to get reflected in the HostSystem > config > fileSystemVolume > mountInfo section in the Managed Object Browser (MOB) of a VirtualCenter Server.

Upgrade and Installation

  • ESX Server 2.x Upgrades to ESX Server 3.5 Update 2 Without Any Pegasus Error Messages
    When upgrading from ESX Server 2.x to ESX Server 3.5 Update 1, processing of Pegasus failed with an error message similar to the following:
    Processing /var/pegasus/vmware/install_queue/2 [FAILED]
    ERROR: See log - /var/pegasus/vmware/install_queue/2.log
    "Cimom not responding"

    This issue is resolved in the ESX Server 3.5 Update 2 release. For more information, refer KB 1004257
  • VMware Tools For Linux Virtual Machine Does Not Get Upgraded Properly
    While upgrading VMware Tools in a linux virtual machine after ESX Server host upgrade from versions 3i or 3.5 to ESX 35 Update 2, the vmhgfs module is not unloaded. This results in VMware Tools not getting upgraded properly. Running the command vmware-config-tools.pl for vmhgfs for module compilation might display the following error message:

    Trying to find a suitable vmhgfs module for your running kernel.

    This issue is fixed in this release.
  • ESX Server Hosts No Longer Go Into Disconnected State After Reinstalling VirtualCenter Server.
    The passwords used by VirtualCenter to connect to individual ESX Server hosts are encrypted with an SSL certificate. Uninstalling VirtualCenter Server no longer removes the SSL certificate folder. This permits a subsequent installation of VirtualCenter to use the same certificate, avoiding the host disconnection issue.
  • Patch Installation Might Require Obsolete Bundles to be Included in the Patch Depot (KB 1004363)
  • Upgrade Fails if VirtualCenter Database Name has More Than 20 Characters (KB 1004297)
  • Multiple VirtualCenter Servers Can Use The Same Microsoft SQL Database Server
    In the previous release, if multiple instances of VirtualCenter were installed using the same Microsoft SQL database server, only the last installed instance would have properly functioning statistics rollup jobs. In this release, each database has a unique set of statistics rollup jobs, allowing for multiple VirtualCenter installations to use the same database server. See KB 1003610 for more information.
  • Upgrading VMware Tools From ESX GA to a Later Version Fails
    This release resolves an issue where upgrading VMware Tools from ESX Server 3.5, ESX Server version 3.5 Embedded, or ESX Server version 3.5 Installable to a later version of the software (for example U1) (applies to all versions; ESX Server 3.5, ESX Server version 3.5 Embedded, and ESX Server version 3.5 Installable) might fail. The following error message might be displayed:
    A later version of 'VMware Tools' is already installed on this machine. The setup cannot continue.
  • During Installation of ESX Server 3.0.2 or ESX Server 3.5 the VMFS Partition Is Listed as Unknown on Partitioning Options Page (KB 1004032)
  • Garbage Values Cause VI Client and VC Server to Stop Responding.
    CDP is enabled (listen mode) on the vswitch by default when it is created. This results in passing of Virtual Infrastructure Client/Virtual Center Server invalid values in the OID field of the CDP packets, which causes the VI Client and the VC Server to stop responding.
  • VirtualCenter Database Upgrade Fails if SQL Server Database Name Contains a Space Character
    This release resolves an issue where VC database upgrade fails if SQL Server database name contains a space character. An error message similar to the following might be displayed:
    ERROR [42000] [Microsoft][SQL Native Client][SQL Server]The specified @database_name ('VMWARE Virtual Center') does not exist.
    (database name contains special characters).
  • File Existence Check Results in an Incorrect Error Message When Using esxupdate Command with a FTP Depot (KB 1004365)
  • Inconsistent File Naming of ESX Server Version 3.5 Update 1 Deliverables (KB 1004388)
  • VMware DRS Settings for Virtual Machines Are Lost When the VirtualCenter Server Is Upgraded
    This release fixes an issue where VMware DRS settings such as CPU and memory allocation settings for virtual machine are lost when the VirtualCenter Server is upgraded to a VirtualCenter 2.5 release.
  • Upgrading VMware Tools Using RPM on a Linux Guest Imported from Workstation Might Fail (KB 1004319)
  • ESX Server 3.0.1, ESX Server 3.0.2, and ESX Server 3.0.2 Update 1 Fail to Upgrade to ESX Server 3.5 Update 2
    ESX Server 3.0.1, ESX Server 3.0.2, and ESX Server 3.0.2 Update 2 fail to upgrade to ESX Server 3.5 Update 2, when the compressed bundle upgrade-from-esx3.0.x-3.5.0_Update_2-<build_number> is used with the depot (bundles directory). Executing the #esxupdate update command results in an error message similar to the following:
    [root@blr-2nd-1-dhcp308 upgrade-from-esx3.0.x-3.5.0_Update_2-100510]# esxupdate update
    INFO: No repository URL specified, going with file:/root/upgrade-from-esx3.0.x-3.5.0_Update_2-100510
    INFO: Configuring...
    ERROR: Invalid repository at file:/root/upgrade-from-esx3.0.x-3.5.0_Update_2-100510/: Cannot find descriptor.xml
    INFO: Make sure you have file: or http: prepended to the URL.

    Workaround: Apply patch ESX-1003519 on ESX Server 3.0.1, and patch ESX-1003525 on ESX Server 3.0.2 and ESX Server 3.0.2 Update 1, and then upgrade to ESX Server 3.5 Update 2 using the esxupdate -d (depot path of upgrade-from-esx3.0.x-3.5.0_Update_2-<build_number>) -b ESX350-Update02 update command with the esxupdate utility.
  • Performance data preserved when upgrading to VirtualCenter 2.5 using Oracle 9.2.0.8 database.
    In the previous release, performance data was lost after upgrading to VirtualCenter 2.5 using Oracle 9.2.0.8. An error message similar to the following might be logged in the database job log:

    ORA-12012: error on auto execute of job 49
    ORA-00001: unique constraint (VPX.VPX_SAMPLE_TIME4_U1) violated
    ORA-06512: at "VPX.STATS_ROLLUP3_PROC", line 223
    ORA-06512: at line 1

  • This issue is fixed in this release.

  • UTC Offset Time Zone Selector Provides Corrected US Time Zone Choices
    This release fixes an issue where the ESX Server installer incorrectly identifies UTC-5 through UTC-8 as US time zones, when providing UTC Offset options to set the time zone for the ESX Server being installed.
    Starting with the ESX Server 3.5 Update 2 release, the ESX Server installer correctly provides UTC+05 through UTC+08 as the UTC offset options for US time zones.
  • Filenames over 64 characters in ESX Server ISO image might get truncated during content extraction. (KB 1005283)
  • ESX Hosts No Longer Go Into Disconnected State After Reinstalling VirtualCenter Server.
    The passwords used by VirtualCenter to connect to individual ESX hosts are encrypted with an SSL certificate. Uninstalling VirtualCenter Server no longer removes the SSL certificate folder. This permits a subsequent installation of VirtualCenter to use the same certificate, avoiding the host disconnection issue.
  • Support for Guest Tools Installers to Detect Distribution-Specific Packages (DSP)
    In this release, the tar and rpm installers detect whether DSPs are present and the guest tools are already installed by checking for the presence of a marker file. If the file is present, the tar/rpm installer fails with an error message similar to the following:

    VMware Tools cannot be installed, since they have already been installed using a package-based mechanism (rpm or deb) on this system. If you wish to continue, you must first remove the currently installed VMware Tools using the appropriate packaged-based mechanism, and then restart this installer.


    If you encounter this error you can either retain the current tools installers and not install VMware Tools using DSPs, or remove the currently installed tools and then install tools using DSPs.
    Note: Without this fix, installing guest tools using the current tar-/rpm-based installers on a target system that already has guest tools installed using DSPs, might lead to errors.

Virtual Machine Management

  • Powered-off Virtual Machines Cannot be Unregistered from ESX Server host in Maintenance Mode.
    This release resolves an issue where powered-off virtual machines cannot be unregistered from the ESX Server host which is in maintenance mode. Trying to unregister virtual machines on an ESX Server host without this fix might generate the following error message: "A general system error: Invalid fault"
  • VI Client Closes on Certain Systems When Accessing the Remote Console of a Virtual Machine
    This release resolves an issue where certain dynamic link libraries on the client machine would cause the Virtual Infrastructure Client to close when accessing the remote console of a virtual machine. A non-related error message similar to the following might be displayed:

    Unable to power on VM: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
  • Cannot Browse vmimages Folder After Adding Hosts to a DRS-Enabled Cluster.
    This release resolves an issue where vmimages folder could not be browsed on an ESX Server host when the host is in DRS enabled cluster.

VirtualCenter, VI Client, and Web Access

  • VI Client Displays Incorrect Resource Share Values for VirtualCenter 2.5

    This release resolves an issue where the VI Client displays incorrect share values for VirtualCenter 2.5 when managing ESX Server 3.0.x and ESX Server 3.5 Server hosts.

    If you use the VI Client to access VirtualCenter 2.5, and then set a value of Low, Normal, or High for either CPU or Memory on a virtual machine, the value is set correctly on the ESX host, but an incorrect share value is displayed in your VI Client.

    The fix is for the virtual machine and the ResourcePool.
  • Support in VirtualCenter 2.5 Update 2 for manually adding computers for consolidation.
  • Virtual Center Alarm Definitions Now Accept More Than One Email Address
    In the previous release, Virtual Center Alarm Definitions would only accept one email address. In this release, Virtual Center Alarm Definitions accepts multiple email address, separated by semicolons.
  • VirtualCenter Server Process Continuously Spikes or Remains at 100% CPU Utilization And Eventually Fails.
    In the previous release, in environments with resource pools in clusters, the VirtualCenter Server process might continuously spike or stay at 100% CPU utilization, and, if left in this condition, eventually fail. This issue is fixed in this release.
  • Virtual Infrastructure Client Displays Information About Hot Spare Disks
    The Storage section in the Health Status panel of the Configuration tab in the Virtual Infrastructure Client indicates the physical disks that are configured as hot spare disks.
  • VirtualCenter Server Fails With Buffer Errors
    This release resolves an issue where the VirtualCenter Server fails while powering on a virtual machine whose backing file URL (for example, the datastore ISO file on NETFS) is more than 256 bytes. An error message similar to the following might be logged in vpxd logs at C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs

    Exception: C:/ob/bora-64192/bora/lib/string/str.c:192 Buffer too small 0x6dab39
  • Alarms Might Fail to Run Scripts with Parameters When Alarm Condition Is Reached
    This release fixes an issue where the VirtualCenter Server might fail to execute a script with parameters as part of the trigger action when the alarm condition is reached.
  • VirtualCenter Server Sends Property Update Notifications When Datastore Attributes Change at the Compute Resource Level
    VirtualCenter Server sends property update notification when any datastore change at the compute resource level is detected. Client applications can now receive update notification provided a property filter is created to receive notification for any changes to the datastore attribute at the compute resource level.
  • VirtualCenter 2.5 License File Might Not Work
    This release resolves an issue where an ESX Server host cannot be added to the VirtualCenter Server after installing VirtualCenter 2.5 license file on VMware License Server. The following error message might be displayed:
    There are not enough licenses to perform the operation
  • Virtual Machine Console Closes Unexpectedly When Collapsing Its Parent Resource Pool Branch
    In the previous release, the Virtual Machine Console would close unexpectedly when its parent resource pool branch was collapsed. This issue is fixed in this release.
  • Virtual Infrastructure Client Continues As Expected When Selecting Another Host While Viewing The Cisco Discovery Protocol Window
    In the previous release, navigating to the Cisco Discovery Protocol window and then selected another host, caused the Virtual Infrastructure Client to stop responding. This release fixes this issue.
  • Virtual Infrastructure Update Installation is Optional in the VI Client Installer
    In this release, the update service installation has been made optional (non-default) in the VI Client installer. To install Virtual Infrastructure Update, enable the check box in the VI Client installer. If this option is selected but an older version of VI Update is already installed on the system, VI Update will automatically be upgraded to the new version. If this option is selected but a later version of VI Update is already installed on the system, VI Update won't be installed.
  • In Non-English Virtual Infrastructure Client, a Performance Chart With Custom Duration Is Displayed Correctly
    In the previous release, when you use a non-English Virtual Infrastructure Client, a saved performance chart with custom duration would display performance data incorrectly. This issue has been fixed in this release.
  • Non Alpha Numerical Characters Are Supported in Annotations of Virtual Machines and ESX Server Hosts
    This release fixes an issue where, if non alpha numerical characters are used in the Notes text box while adding annotations to virtual machines or ESX Server hosts, VirtualCenter Server stops responding and logs an entry similar to the following in the vpxd.log file:
    Unhandled exception: not well-formed (invalid token).
  • VirtualCenter Server Fails to Add ESX Server 2.5.x Hosts That Are Not SSL Authentication Enabled
    Starting with the VirtualCenter 2.5 Update 2 release, the VirtualCenter Server fails to connect to ESX Server 2.5.x hosts that are not SSL authentication enabled, with an error message similar to the following:
    Unable to access to the specified host. It either does not exist, the server software is not responding, or there is a network problem.
    After upgrading to the VirtualCenter 2.5 Update 2 release, ensure that SSL authentication is enabled on an ESX Server host before adding it to a VirtualCenter Server. To enable SSL authentication in the ESX Server host, perform the following activities:
    1. In the /etc/vmware/config file, replace the line security.host.ruissl = "FALSE", with the line security.host.ruissl = "TRUE".
    2. Restart the xinetd service by using the # service xinetd restart command.

 

Top of Page

Installing the Language Pack on the ESX Server Host

For German, Japanese, or Simplified Chinese language support when you use Virtual Infrastructure Web Access or the VI Client with your ESX Server host, you must install the language pack.

To install the language pack:

  1. Download the VMware-ESXlangpack-2.5.0-85586.zip file from the download site.
  2. Extract the contents of the ZIP file into a temporary directory.
  3. Copy the files from the ESX Server/webAccess/ directory to the VI Web Access installation directory on your ESX Server host (usually /usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.26/webapps/).

    cp -pr ESX Server/webAccess/webapps/ui /usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.26/webapps/
    cp -pr ESX Server/webAccess/webapps/WEB-INF /usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.26/webapps/ui/

  4. Copy the localized files into the appropriate directory:

    For German use the following command:
    cp -pr ESX Server/docroot/de /usr/lib/vmware/hostd/docroot/

    For Japanese use the following command:
    cp -pr ESX Server/docroot/ja /usr/lib/vmware/hostd/docroot/

    For Simplified Chinese use the following command:
    cp -pr ESX Server/docroot/zh-CN /usr/lib/vmware/hostd/docroot/

  5. Edit the /etc/vmware/hostd/config.xml file to enable the correct default language. Find the following lines in config.xml
       <locale>
          <DefaultLocale>en_US</DefaultLocale>
       </locale>

    For German, replace the lines with the following:

       <locale>
          <DefaultLocale>de_DE</DefaultLocale>
       </locale>

    For Japanese, replace the lines with the following:

       <locale>
          <DefaultLocale>ja_JP</DefaultLocale>
       </locale>

  6. For Simplified Chinese, replace the lines with the following:

       <locale>
          <DefaultLocale>zh_CN</DefaultLocale>
       </locale>

  7. Type the following commands to restart VI Web Access and host agent services:

    service mgmt-vmware restart
    service vmware-webAccess restart

 

Top of Page

 

======= VMware Infrastructure 3 Release Notes
VMware

VMware Infrastructure 3 Release Notes

Note: An issue has been discovered by many VMware customers and partners with ESX Update 2 (build number 103908) and ESXi 3.5 Update 2 (build number 103909) where Virtual Machines fail to power on or VMotion successfully. This problem began to occur on August 12, 2008 for customers that had upgraded to ESX 3.5 Update 2. The problem is caused by a beta release product expiration that was mistakenly left enabled for the release build. New installations of build number 110268 of ESX Server 3.5 Update 2 will not experience this issue. For more information, see KB 1006716.

 

VMware ESX Server 3.5 Update 2 | 13 AUG 2008 | Build 110268

VMware Infrastructure Management Installer | 25 JUL 2008 | Build 104263 (English Only Build)
VirtualCenter 2.5 Server Update 2 | 25 JUL 2008 | Build 104215
Virtual Infrastructure Client | 25 JUL 2008 | Build 104215

VMware Infrastructure Management Installer | 25 JUL 2008 | Build 104265
VirtualCenter Server 2.5 Update 2 | 25 July 2008 | Build 104217
Virtual Infrastructure Client | 25 July 2008 | Build 104249

See Selecting the Appropriate VMware Infrastructure Management Installer Build for information.

Last Document Update: 18 DEC 2008

Check frequently for additions and updates to these release notes.

 

These release notes include the following topics:

Note: In many public documents, VMware ESX Server 3.5 is now known as VMware ESX 3.5 and VMware ESX Server 3i version 3.5 as VMware ESXi 3.5. These release notes continue to use the previous convention to match the product interfaces and documentation. A future release will update the product names.

What's New

The following information provides highlights of some of the enhancements available in this release of VMware Infrastructure 3:

Note: Not all combinations of VirtualCenter and ESX Server versions are supported and not all of these highlighted features are available unless you are using VirtualCenter 2.5 Update 2 with ESX Server 3.5 Update 2. See the ESX Server, VirtualCenter, and Virtual Infrastructure Client Compatibility Matrixes for more information on compatibility.

Features

  • Windows Server 2008 support – Windows Server 2008 (Standard, Enterprise, and Datacenter editions) is supported as a guest operating system.  With VMware memory overcommit technology and the reliability of ESX Server, you can maximize virtual machine density with this new guest operating system to achieve the highest ROI. Guest operating system customizations and Microsoft Cluster Server (MSCS) are not supported with Windows Server 2008.
  • Enhanced VMotion Compatibility – Simplifies VMotion compatibility issues across CPU generations. Enhanced VMotion compatibility (EVC) automatically configure server CPUs with Intel FlexMigration or AMD-V Extended Migration technologies to be compatible with older servers. After EVC is enabled for a cluster in the VirtualCenter inventory, all hosts in that cluster are configured to ensure CPU compatibility for VMotion. VirtualCenter does not permit the addition of hosts that cannot be automatically configured to be compatible with those already in the EVC cluster.
  • Storage VMotion – Storage VMotion from an FC/iSCSI datastore to another FC/iSCSI datastore.  This support is also extended on ESX Server/ESX Server 3i 3.5 Update 1.
  • VSS quiescing support – When creating quiesced snapshot of Windows Server 2003 guests, both filesystem and application quiescing are supported. With Windows Server 2008 guests, only filesystem quiescing is supported. For more information, see the Virtual Machine Backup Guide and the VMware Consolidated Backup 1.5 Release Notes.
  • Hot Virtual Extend Support – The ability to extend a virtual disk while virtual machines are running is provided. Hot extend is supported for vmfs flat virtual disks that do no have snapshots opened in persistent mode.
  • 192 vCPUs per Host – VMware now supports increasing the maximum number of vCPUs per host to 192 given that the maximum number of Virtual Machines per host is no more than 170 and that no more than three virtual floppy devices or virtual CDROM devices are configured on the host at any given time. This support is also extended on ESX Server 3.5 Update 1.

Hardware Enablement and Management:

  • 8Gb Fiber Channel HBAs – Support is available for 8Gb fiber channel HBAs. See the I/O Compatibility Guide for ESX Server 3.5 and ESX Server 3i for details.
  • SAS arrays – More SAS array configurations are now supported.  See the Storage/SAN Compatibility Guide for ESX Server 3.5 and ESX Server 3i for details.
  • 10 GbE iSCSI Initiator – iSCSI over a 10GbE interface is supported. This support is extended on ESX Server 3.5 Update 1, ESX Server version 3.5 Update 1 Embedded and ESX Server version 3.5 Update 1 Installable.
  • 10 GbE NFS Support – NFS over a 10GbE interface is supported.
  • IBM System x3950 M2 – x3950 M2 in a 4-chassis configuration is supported, complete with hardware management capabilities through multinode Intelligent Platform Management Interface (IPMI) driver and provider. Systems with up to 32 cores are fully supported.  Systems with more than 32 cores are supported experimentally.
  • IPMI OEM Extension Support – Execution of IPMI OEM extension commands is supported.
  • System Health Monitoring Through CIM Providers - More Common Information Model (CIM) providers are added for enhanced hardware monitoring, including storage management providers provided by QLogic and Emulex.  LSI MegaRAID providers are also included and are supported experimentally.
  • CIM SMASH/Server Management API The VMware CIM SMASH/Server Management API provides an interface for developers building CIM-compliant applications to monitor and manage the health of systems.  CIM SMASH is now a fully supported interface on ESX Server 3.5 and VMware ESX Server 3i.
  • Display of System Health Information – More system health information is displayed in the VI Client for both ESX Server 3.5 and VMware ESX Server 3i.
  • Remote CLI – Remote Command Line Interface (CLI), which was previously supported only on ESX Server 3i, is now supported on both Update 2 for ESX Server 3i version 3.5 and Update 2 for ESX Server 3 version 3.5. For more information on Remote CLI, see the Remote Command-Line Interface Installation and Reference Guide for more information.

Management Agents Support

  • HP Management Agents – HP Insight Management Agents provide server management capabilities for ESX Server hosts installed on supported server platforms.  A new 8.1 version is now supported.

Guest Operating System Support

  • Solaris10 U5 - Both the 32-bit and 64-bit versions are supported.
  • SUSE Linux Enterprise Server 10 SP2 - Both the 32-bit and 64-bit versions are supported. The 32-bit version supports the VMware Virtual Machine Interface (VMI) and so is performance-optimized for VMware environments.
  • Ubuntu 8.04 - Both the 32-bit and 64-bit versions are supported. The 32-bit version supports the VMware Virtual Machine Interface (VMI) and so is performance-optimized for VMware environments.

Service Console, Driver, and Library Updates

  • Service Console Operating System Update - The ESX Server Console operating system has been updated to RHEL 3.0 U9.  See the document Updated RPMs and Security Fixes for detailed information.
  • Driver Updates - The tg3 driver has been updated to version 3.81c.  The megaraid_sas driver has been updated to version 00.00.03.19.
  • Library Update - StoreLib has been updated to version 2.51.

VMware High Availability (HA)

VirtualCenter 2.5 update 2 adds full support for monitoring individual virtual machine failures based on VMware tools heartbeats. This release also extends support for clusters containing mixed combinations of ESX and ESX Server 3i hosts, and minimizes previous configuration dependencies on DNS.

VirtualCenter Alarms

VirtualCenter 2.5 Update 2 extends support for alarms on the overall health of the server by monitoring the health of each of the individual system components, such as memory and power supplies. You can now configure alarms to trigger when host health degrades.

Guided Consolidation Enhancements

Guided Consolidation now provides administrators with the ability to filter the list of discovered systems by computer name, IP address, domain name or analyzing status. Administrators can also choose to explicitly add physical hosts for analysis, without waiting for systems to be autodiscovered by the Consolidation wizard. Systems can be manually added for analysis by specifying either a hostname or IP address. Multiple hostnames or IP addresses, separated by comma or semi-colon delimiters, can also be specified for analysis. Systems can also be manually added for analysis by specifying an IP address range or by importing a file containing a list of hostnames or IP addresses that need to be analyzed for consolidation. Guided Consolidation also allows administrators to override the provided recommendations and manually start the conversion wizard.

Live Cloning of Virtual Machines

With VirtualCenter 2.5 Update 2, you can create a clone of a powered-on virtual machine without any downtime to the running virtual machine. Therefore, administrators are no longer required to power off a virtual machine to create a clone of it.

Windows Single Sign-on Support

You can now automatically authenticate to VirtualCenter using your current Windows domain login credentials on the local workstation, if the credentials are valid on the VirtualCenter server. This capability also supports logging in to Windows using Certificates and Smartcards. Windows single sign-on support can be used with the VI Client or the VI Remote CLI to make sure that scripts written using the VI Toolkits can take advantage of the Windows credentials of your current session to automatically connect to VirtualCenter. To enable single sign-on support, see KB 1006611.

Plug-In Updates

This release of the VMware Infrastructure 3 software suite also includes the following:

Top of Page

Prior Releases of VMware Infrastructure 3

Features and known issues from prior releases of VMware Infrastructure 3, which include ESX Server 3.x and VirtualCenter 2.x releases, are described in the release notes for each release. To view release notes for prior releases of VMware Infrastructure 3 components, click one of the following links:

ESX Server Releases

VirtualCenter Releases

Top of Page

Before You Begin

Note: If you are installing this release from anything other than physical DVD media, see the knowledge base article Filenames over 64 characters in ESX Server ISO image may get truncated during content extraction (KB 1005283) for important information on a known installation issue.

ESX Server, VirtualCenter, and Virtual Infrastructure Client Compatibility

The ESX Server, VirtualCenter, and Virtual Infrastructure Client Compatibility Matrixes guide provides details on the compatibility of current and previous versions of VMware Infrastructure 3 components, including ESX Server, VirtualCenter, and the VI Client.

Installation Notes for This Release

See the ESX Server Compatibility Guides before installing this software. You must verify that your server, I/O, storage, guest operating system, management agent, and backup software needs are compatible. These guides also address 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.5 and ESX Server 3i (PDF)
  •  I/O Compatibility Guide for ESX Server 3.5 and ESX Server 3i (PDF)
  • Storage/SAN Compatibility Guide for ESX Server 3.5 and ESX Server 3i (PDF)
  • Backup Software Compatibility Guide for ESX Server 3.5 and ESX Server 3i (PDF)

Read the Installation Guide 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 the following:

Installing using the VMware Infrastructure Management Installer and Physical Media

New: For this release, the VMware Infrastructure Management Installer requires a DVD drive when you use physical media to install VMware Infrastructure software.

Selecting the Appropriate VMware Infrastructure Management Installer Build

There are two builds of VMware Infrastructure Management Installer available for download. Select one of the following options :

Virtual Infrastructure Client Installer Changes

The VI Client standalone installer (available from ESX Web Access) allows installation of the VMware Infrastructure Update service, which is used for updating and patching ESX Server 3i hosts. The standalone VI Client Installer  is now modified to allow optional installation of the VMware Infrastructure Update service so as to reduce unnecessary proliferation of this tool. Note that the VirtualCenter Unified Installer  (available as part of the VC 2.5 Update 2 download) now installs VMware Infrastructure Update service when you choose the VI Client installation option.

Upgrading or Migrating to VirtualCenter 2.5 Update 2

This release also supports upgrading from VirtualCenter 1.4.1, VirtualCenter 2.0.2 (including Update 1, Update 2, and Update 3), VirtualCenter 2.5, or VirtualCenter 2.5 Update 1 to VirtualCenter 2.5 Update 2. Review the detailed upgrade and migration instructions and guidelines that are provided in the Upgrade Guide.

Note: Previous versions of VMware Update Manager are not compatible with VirtualCenter 2.5 Update 2 and must be upgraded to VMware Update Manager 1.0 Update 2 during the installation process.

Upgrading or Migrating to ESX Server 3.5 Update 2

This release of ESX Server 3.5 Update 2 allows upgrades only from previously supported versions. The ESX Server 3.5 Update 2 Installer prompts you to perform an upgrade only when a previously supported version of ESX Server is found. See the Installation Guide for installation requirements and the Upgrade Guide for the Upgrade Support Compatibility Matrix.

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

Upgrade type ESX Server 2.5.4
and 2.5.51
ESX Server 3.0.1 2 ESX Server 3.0.22 ESX Server 3.5 ESX Server 3.5 Update 1
Tarball Yes Yes3 Yes4 Yes Yes
ISO image Yes Yes Yes Yes Yes
  1. For ESX Server 2.5.1, ESX Server 2.5.2, and ESX Server 2.5.3, upgrade first to ESX Server 2.5.4 and then upgrade to ESX Server 3.5 Update 2. Or upgrade to ESX Server 3.5 and then upgrade to ESX Server 3.5 Update 2.
  2. For ESX Server 3.0.0, upgrade first to ESX Server 3.0.1 or higher and then upgrade to ESX Server 3.5 Update 2 using an ISO image. Or upgrade to ESX Server 3.5 and then upgrade to ESX Server 3.5 Update 2.
  3. For ESX Server 3.0.1 Patch ESX-1003519 (See KB 1003519) must be applied first before performing an upgrade using the tarball.
  4. For ESX Server 3.0.2 Patch ESX-1003525 (See KB 1003525) must be applied first before performing an upgrade using the tarball.

For more information on more information on installation and upgrade methods, see the Upgrade Guide.

Updated RPMs and Security Fixes

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

Top of Page

Patches Contained in this Release

This release contains all patches for the ESX Server software that were released prior to the release date of this product. See the ESX Server 3.5 Patches download page or click on the name of a patch for more information on the individual patches.

ESX Server 3.5 Update 2 contains the following patches:

Previously Released Patches

New Patches in Update 2 (13 AUG 2008 | Build 110268 )

Top of Page

Known Issues

This section contains known issues for this release in the following subject areas:

New Issues with ESX Server 3.5 Update 2, Build 110268

The following issues unique to the replacement build of ESX Server 3.5 Update 2 (Build 110268) have been found:

Backup

  • Consolidate Helper Snapshots Might Not Be Removed Automatically
    In the ESX Server 3.5 Update 2 release, Consolidate Helper snapshots are created iteratively to minimize the amount of time a virtual machine is inactive during snapshot creation. As a result, the Consolidate Helper snapshots are now called Consolidate Helper-XXX and not just Consolidate Helper. When you use VMware Consolidated Backup 1.1 with ESX Server 3.5 Update 2, if vcbMounter encounters a failure during a snapshot delete operation, this temporary snapshot might be left behind. The vbCleanup.bat command does not delete this Consolidate Helper-XXX snapshot. You must manually delete it using VI Client. This issue does not exist in VMware Consolidated Backup 1.5.

CIM and API

  • Firewall on ESX Server 3.5 interferes with CIM indication support

    Outgoing HTTP connections are blocked by the firewall on ESX Server 3.5. This prevents indications from reaching the indication consumer.

    Resolution: In the Service Console, open an outgoing port for connections to the indication consumer, using the following command:
    esxcfg-firewall -o <port-number>,tcp,out,http

    To close a port for http in the firewall:
    esxcfg-firewall -c <port-number>,tcp,out,http

  • Some CIM classes do not work properly on IBM Multinode systems
    The following anomalies are seen. For the following classes, the EnumerateInstance operation returns one instance fewer than the Enumerate InstanceNames operation:

    • CIM_AssociatedSensor
    • CIM_MemberOfCollection
    For the following classes, the GetInstance operation fails for some instances. However, the EnumerateInstances operation succeeds.
    • CIM_HostedService
    • CIM_Sensor
    • CIM_SystemDevice
    • CIM_Slot
    • CIM_ElementConformsToProfile
    For the following classes, the EnumerateInstances and EnumerateInstanceNames operations fail to return any results:
    • CIM_OwningCollectionElement
    • CIM_RedundancySet
  • Operation RequestStateChange(RestoreDefaultThresholds) results in error
    In the ESX Server 3.5 release, the operation RequestStateChange(RestoreDefaultThresholds) results in the following error message for some sensors:
    CIM_ERR_FAILED: index out of bounds

    In spite of the error message, the CIMOM does restore the thresholds.

  • VI Client displays incorrect name for power supply redundancy sensor on HP servers
    When you connect to an ESX Server installation on an HP server system using VI Client, the VI Client incorrectly displays the power supply redundancy sensor on the server as a physical power supply source. For example, for an HP server with redundancy sensor that has two physical power supplies, the VI Client displays the redundancy sensor as Power Supplies for Power Supply 3.

  • Executing a CallMethod query on a CIM_RecordLog instance might fail
    In ESX Server 3.5 Update 2, executing a CallMethod query (cm) on a CIM_RecordLog instance might not succeed at all times. You can, however, clear system event log through a remote management console or interface.
  • Mandatory property MaxReadable,NominalReading,NormalMax,NormalMin and PollingInterval in class CIM_NumericSensor shows in-correct values
    The instances of CIM_NumericSensor have this set of properties: MaxReadable,NominalReading,NormalMax,NormalMin. When the actual sensor does not support values of these properties, they are displayed as 0, in CIM responses; instead of unspecified.
  • Changes to the sensor threshold are not reflected immediately
    If you change the sensor threshold through CIM, enumeration of the sensor might not return the new property values immediately. The changes take effect about a minute later.
  • On some Dell MLK hardware, the NumberOfBlocks property for OMC_Memory instance has a value of 0. This issue is under investigation.
  • On HP 380 G5 machines running ESX Server 3.5 Update 2 the IPMI board's IP address is not returned in response to CIM_IPProtocolEndpoint queries.
  • In the ESX Server 3.5 release, invoking the operation Reset() on numeric power supply sensors results in the following error message:
    CIM_ERR_FAILED: index out of bounds
    As a workaround, you can use the RequestStateChange(Reset) operation.
  • InvokeMethod(RequestStateChange) for either Sensor and SEL fails when you use the WS-Man protocol.
  • The ModifyInstance() call to change sensor threshold fails when you use the WS-Man protocol.
  • An ESX Server 3.5 host that has been upgraded to ESX Server 3.5 Update 2 does not report CIM_AssociatedSensor instances correctly. The EnumerateInstance() and Association() queries for CIM_AssociatedSensor do not return any instances. As a workaround, do a clean installation of ESX Server 3.5 Update 2, or do a clean installation of ESX Server 3.5 U1 and then upgrade to ESX Server 3.5 Update 2.
  • Indications do not work on ESX Server 3.5 Update 2 when you use the WS-Man protocol.
  • On IBM athena hardware, some OMC_DiscreteSensor instances are found to have incorrect device IDs (with -1 as the last segment of the device ID).
  • On servers with ESX Server 3.5 Update 2 installed, SLP reports "service:wbem" available on http port 5888. However, the default firewall settings prevent access to port 5888. To access the port, unblock the port in the firewall configuration.
  • On some servers, incorrect PECI temperature sensor readings might be reported. Incorrect values are shown in the VI Client and in the NominalReading property of CIM_Sensor instances for CPU PECI tic for Processor sensors.
  • On ESX Server 3.5 Update 2, instances of VMware_Account (a subclass of CIM_Account) show a SystemName property with a value of "0". The SystemName property should contain the BIOS UUID of the server.
  • The InvokeMethod(RequestPowerStateChange) fails when you use the WS-Man protocol.
  • The chassis intrusion indication is not available for IBM Athena servers.

Guest Operating Systems

VMware High Availability (HA)

  • NEW: HA network compliance check
    During the configuration of HA in VirtualCenter 2.5 Update 2, the Task & Events tabs might display the following error message and recommendation:

    HA agent on <esxhostname> in cluster <clustername> in <datacenter> has an error Incompatible HA Network:
    Consider using the Advanced Cluster Settings das.allowNetwork to control network usage.


    Starting with Virtual Center 2.5 Update 2, HA has an enhanced network compliance check to increase cluster reliability. This enhanced network compliance check helps to ensure correct cluster-wide heartbeat network paths. See KB 1006606 for details.
  • VI Client Might Show the Host as Not Responding During HA-DRS Cluster Operations
    During HA-DRS cluster operations like adding or removing a host from a DRS cluster or applying DRS recommendations, VI Client might show the host as "Not responding", even when the host IP can be reached.
    Workaround
    Disconnect the host from the HA-DRS cluster and reconnect it. This refreshes the system and VI Client reflects the configuration changes that you have made. If the VI Client again shows the host as Not Responding, disconnect the host from the HA-DRS cluster, remove the host, and add the host back to the same cluster.
  • Virtual Machine Migrations Are Not Recommended When the ESX Server Host Is Entering the Maintenance or Standby Mode
    No virtual machine migrations will be recommended (or performed, in fully automated mode) off of a host entering maintenance or standby mode, if the VMware HA failover level would be violated after the host enters the requested mode. This restriction applies whether strict HA admission control is enabled or not.
  • VMware HA Health Monitoring Does Not Show Rebooting in the Console After a Host Failover
    After a host failure, the VMware console displays an empty window when the Health Monitoring is enabled for an HA cluster. The console does not display the virtual machines rebooting.

    Workaround
    You must open a new console to see the virtual machines restarting after the failover.

Internationalization

All fields in the VI Client and the VI WebAccess support non-ASCII character input, except for the following limitations:

Non-ASCII Character Entry Limitations

  • Specifying a non-ASCII value as an input string is not supported by the remote command line interface (RCLI).
  • The name of the computer on which Virtual Infrastructure 3 or any of its components are installed must not contain non-ASCII characters.
  • The name of the computer or virtual machine where VirtualCenter Server is installed must not have a non-ASCII computer name or the installation of VirtualCenter Server will fail.
  • Use the default installation path names specified in the installer for all the components. Do not change the install path, because the installer does not support installation path names containing non-ASCII characters and extended-ASCII characters.
  • Datastore names, Virtual Network names, and Image file names (CD, DVD, and floppy drive) are restricted to ASCII characters only.
  • Message of the Day must use only ASCII characters.
  • Logging in to the VirtualCenter server is supported for user names with ASCII characters only (login account name on Windows).
  • Image customization might fail if non-ASCII characters are used.
  • Custom attribute names and values must use only ASCII characters.
  • To conform to the general Internet practice and protocols, the following cannot contain non-ASCII characters: host names, workgroup names, domain names, URLs, email addresses, SMTP server names, and SNMP community string.
  • Guest operating system customizations using ASCII encoding are supported but customizations using UTF-8 encoded native characters of Japanese, Chinese, or German have limited support. For customizations with non-ASCII owner, organization, username, or password, VirtualCenter and the sysprep tool must be hosted in the same locale as that of the Guest OS. This includes the scenario to use UTF-8 encoded answer file.

Non-ASCII Character Display Limitations

  • When managing a VirtualCenter Server with the VI Client running on different languages of Windows, you might see some characters displayed incorrectly because of the difference in language-specific support on Windows.
  • If an error message includes log locations or user names containing non-ASCII characters, it will not display correctly in the localized environment.
  • When you use the Import Wizard of VMware Converter, the date and time format is sometimes inconsistent with the current locale.
  • Unicode characters are displayed as '???' under the Status column and the Task Details of the Task View tab in the Japanese locale.
  • The Commands section on the Summary tab is not displayed properly.

Guided Consolidation Limitations

The Guided Consolidation tab is available only in the en_US locale.

Translation Issues

The following are known issues with translation in this release:

  • The Upgrade wizard is not translated.
  • Some messages originating from the ESX Server host are not translated.
  • Some localized interface layouts are not yet completed.

Other Internationalization Issues

The following additional issues have been identified:

  • Values used in the Run a Script action for an alarm might not display properly after restarting VirtualCenter server if the Virtual Infrastructure Client host OS language and VirtualCenter Server/Database host OS languages are different.
  • In the Simplified Chinese version of VI Web Access, the Cancel button does not have the correct text and the text on the button is displayed incorrectly.
  • NEW: Connecting to an ESX Server 3.5 Update 2 host through VirtualCenter will not upgrade a localized VI Client
    If you connect to an ESX Server 3.5 Update 2 host through VirtualCenter, the localized VI client in use will not be upgraded to the Update 2 version.
  • The VI Client Might Override the Language Preference Setting
    The VI Client Might Override the Language Preference Setting and display some messages in a language other than its primary language. It might display messages that are dynamically generated by the server (VirtualCenter Server and ESX Server) in the primary language set on the server. This issue does not occur if all the software is running in the language that corresponds to the locale of the operating system.
  • Wrong Text Appears on the Reinstall Wizard of the German VI Client
    The reinstall wizard displays wrong text in the German VI Client.
    The reinstall wizard shows the following text
    Der Installations-Assistent ermöglicht Ihnen, Virtual Infrastructure Client 2.5 zu reparieren oder zu entfernen., instead of The installation wizard will allow you to remove Virtual Infrastructure Client 2.5.
  • Links Containing Machine-Generated Virtual Machine Names Do Not Work

    When you use WebAccess to browse the datastore by clicking a link containing machine-generated virtual machine name (typically starting with a plus sign and ending with slash, for example +5paw55qE5qih5p2,/), the Web browser displays a blank page or returns a page not found error. You can, however, access such virtual machines using the VI Client.

Migration with VMotion

Miscellaneous

Networking

Server Configuration

Storage

Upgrade and Installation

VirtualCenter Upgrade and Installation

Virtual Machine Management

  • User with 'Create' Privileges Cannot Create Virtual Machines(KB 1004417)
  • Cloned Virtual Machines do not Contain DNS Suffix (KB 1004299)
  • Deploying Virtual Machine From a Template Fails With No Permission Error (KB 1004295)
  • Cloned Virtual Machines See the .vmdk File of the Source Virtual Machine (KB 1004176)
  • VMware Tools Custom Script Not Executed for Suspend or Shut Down Events (KB 1004390)
  • Virtual Machines Might Not Power on After a Failover When the Host Is Isolated
    Virtual machines might not start after a failover when a host is isolated and the isolation response is set to Guest Shutdown which is the default configuration for a cluster. This might occur on clusters with fewer than five nodes and can happen on virtual machines that take more time to complete the guest shutdown.
    Workaround
    Set the Isolation Response to either Leave powered on or Power off for clusters which have fewer than five nodes.
    To set the Isolation Response for a virtual machine, select the cluster, click the Edit Settings link, and select Virtual Machine Options under VMware HA. From the Isolation Response pop-up menu, select either Leave powered on or Power off options for the specific virtual machine.
  • I/O Might Stall on Virtual Machines During Firmware Upgrade
    When Virtual machines are running on a shared LUN that has heavy I/O workload, and if the firmware is upgraded using the storage management utility or if the storage controller is restarted, I/O might stall on any of the virtual machines.
    Messages similar to the following might appear in the vmkernel.log file:
    1:01:05:07.275 cpu2:1039)WARNING: FS3: 4785: Reservation error: Not supported
    SCSI: 4506: Cannot find a path to device vmhba1:0:125 in a good state. Trying path vmhba1:0:125.
    1:01:05:10.262 cpu3:1039)ALERT: SCSI: 4506: Cannot find a path to device vmhba1:0:125 in a good state. Trying path vmhba1:0:125.
    1:01:05:40.748 cpu1:1083)<6>mptbase: ioc0: LogInfo(0x30030108): Originator={IOP}, Code={Invalid Page}, SubCode(0x0108)
    1:01:05:40.930 cpu0:1024)Log: 472: Setting loglevel (via VSI) for module 'SCSI' to 5

VirtualCenter, VI Client, and Web Access Issues


Top of Page

Resolved Issues

This release includes fixes in the following subject areas:

Backup

  • Virtual Disks Size Can Be Changed While the Virtual Machine Is Powered On
    On powered on virtual machines that are running on ESX Server 3.5 Update 2, the size of the virtual disks can be changed by using the Provision Size control that is available when editing the virtual disk settings of virtual machines.
  • VMware Consolidated Backup Fails to Perform Backup of Non-Windows and Non-Linux Virtual Machine Disks
    VMware Consolidated Backup might fail to perform backup of non-Windows and non-Linux virtual machine disks with error messages similar to the following:
    [2008-02-06 12:28:07.234 'vcbMounter' 3076457280 error] Error: Other error encountered: Snapshot creation failed: Custom pre-freeze script failed.
    [2008-02-06 12:28:07.234 'vcbMounter' 3076457280 error] An error occurred, cleaning up...
    [2008-02-06 12:28:07.356 'SOAP' 3076457280 trivia] Sending soap request to
    [TCP:cs-tse-h20:443]: logout

    Starting with the ESX Server 3.5 Update 2 release, VMware Consolidated Backup performs backup of non-Windows and non-Linux virtual machine disks successfully, without taking their quiescent snapshot.
  • VirtualCenter Server Fails When Multiple VCB Proxy Servers Perform Simultaneous Backups
    When an SDK application performs a VM lookup by starting the search by index API, and the SQL Server gets into a deadlock during lookup, the VirtualCenter Server fails. For example, this occurs is when multiple VCB proxy servers are connected to the VirtualCenter Server and if the SQL Server gets into a deadlock during backup, the VirtualCenter Server fails with error statements similar to the following in the log file:
    [2008-04-03 00:06:29.636 'App' 4700 info] [VpxLRO] -- BEGIN task-internal-43561 -- -- vim.SearchIndex.findByIp -- 2C3A8FF6-30F9-4E68-9ACF-2A6EFBCE9609
    [2008-04-03 00:06:32.605 'App' 4700 error] [Vdb::IsRecoverableErrorCode] Unable to recover from 40001:1205
    [2008-04-03 00:06:32.605 'App' 4700 error] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Check database connectivity before restarting. Error: Error[VdbODBCError] (-1) "ODBC error: (40001) - [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction." is returned when executing SQL statement "SELECT id FROM vpx_vm WHERE uuid_bios = ? AND is_template = 0"
    [2008-05-23 08:15:35.252 'App' 44264 verbose] Backtrace:
    [2008-05-23 08:15:35.252 'App' 44264 info] Forcing shutdown of VMware VirtualCenter now
  • vcbSnapAll Fails to Display a Relevant Error Message When Incorrect Login Credentials Are Provided for the ESX Server Host
    An irrelevant message similar to the following when incorrect login credentials are provided for the ESX Server host:
    Could not retrieve a list of virtual machines to back up with the search criteria (name:<VMname>)
    Starting with this release, a suitable message similar to the following is displayed:
    Other error encountered: Host address lookup for server <name> failed: Unknown host Could not retrieve a list of virtual machines to back up.
  • VCB Fails to Back Up Virtual Machines When a User Account Is Not Assigned the Disk Lease Privilege on the Root of the Object Tree
    This release resolves an issue where backups in SAN mode fail when the VirtualMachine.Config.DiskLease privilege is assigned only to the virtual machines that are backed up using VMware Consolidated Backup (but not to the root of the object tree in VirtualCenter).

CIM and API

  • HTTP 1.1 Chunking Fails
    This release resolves an issue in the previous implementation of the Small Footprint CIM Broker (SFCB) would fail if a client tried sending a chunked message. The SFCB was sending an acknowledgment to the wrong socket when HTTP 1.1 chunking was being used. This caused a failure in the transfer, since the sending client never received the proper acknowledgment.
  • System Health Information Is Now Monitored for Each Node of a multinode System
    The Intelligent Platform Management Interface (IPMI) based system health monitoring system now reports individual health information for each node of a multinode clustered system. Health information is displayed in the VI Client and can also be monitored by third party CIM-based management consoles.
  • VI Client Displays the Manufacturer and Model Name of the Server In the Health Status Tree
    The CIM window in the VI Client displays the manufacturer and model name of the server in the health status tree, in addition to the other hardware related information.
  • Web Services Description Language (WSDL) and API Reference Documentation Incorrectly Specify Properties of Type MethodFault[]
    This release resolves an issue where the web services description language (WSDL) and API reference documentation refers to the type of certain properties as MethodFault[], instead of LocalizedMethodFault[]. As a result, WSDL based clients are unable to de-serialize responses from the server that contain properties of type MethodFault[]. The fix updates the WSDL and API reference documentation for faults to specify LocalizedMethodFault[] rather than MethodFault[].
  • Adds vmkgdb And vmkdump_extract to DDK devtools.
    This release provides vmkgdb and vmkdump_extract tools that work with UserWorld coredumps to extract and analyze core dumps.
  • Custom Virtual Disk Name Displayed in the VI Client
    This release incorporates custom virtual disk names into the name of the storage displayed under Configuration > Health Monitoring in the VI Client.
  • This release resolves an issue where CIM queries for VMware_LatchedHealthState and VMware_RollupHealthState did not work in the Release Candidate build of ESX Server 3.5 Update 2.

Guest Operating Systems

  • NEW: PXE installation of guest operating system fails
    This release resolves an issue in the previous release where PXE installation failed for guest operating systems with the vmxnet or Enhanced vmxnet drivers. Starting with this release, PXE GOS installation works as expected for the e1000, flexible, and Enhanced vmxnet drivers.

VMware High Availability (HA)

  • Using VMware HA in conjunction with VMware ESX Server 3i hosts has the following restrictions, swap space must be enabled on individual ESX Server 3i hosts, and only homogeneous (non-mixed) clusters are supported at this time.
  • ESX Server 3i Hosts Without Swap Enabled Cannot be Added to an HA Cluster (KB 1004177)
  • Limited configurations are supported for VMware HA and ESX Server 3i hosts (KB 1004656)
  • Updated: DNS Resolution Is No Longer a Requirement to Enable VMware High Availability on ESX Server Hosts
    Previously, enabling VMware High Availability required DNS resolution of all ESX Server hosts in a High Availability cluster. This was done by configuring DNS records or by adding all of the host names and IP addresses to the /etc/hosts file on each server.
    Starting with the VirtualCenter 2.5 Update 2 release, DNS resolution or /etc/hosts file entries are no longer required to configure High Availability. The host name and IP address information are now provided by the managing VirtualCenter Server.
    Note: For ESX Server 3i systems, define a host name on the ESX Server 3i host by performing the following steps in the ESX Server 3i console user interface:
    1. Press F2 to Customize System.
    2. Choose Configure Management Network.
    3. Choose DNS configuration.
    4. Select the Use the following DNS Server addresses and hostname radio button.
    5. Replace localhost host name with a unique valid name.

Internationalization

  • VirtualCenter Server Service Now Allows For Non-ASCII Characters in DRS Rule Names and Advanced Options Settings
    In the previous release, VirtualCenter would fail to start if DRS rule names or advanced options settings contained non-ASCII characters. This is fixed in this release.
  • Text Truncated on the Network Access Page of the Add Network Wizard While Using Japanese VI Client
    Details of Networks (IP address) displayed on the Network Access page are truncated while accessing VirtualCenter using the Japanese VI Client.
    The Network Access window appears in the Add Network wizard when you select Add Networking from the Networking option under the Configuration tab.
    Workaround
    You can view the network information (IP address) in the Network Adapters page. Select Configuration>Networking>Properties>Network Adapters to display the Networks.

Migration with VMotion

  • The Power On Task Scheduled on Virtual Machines Fail After Migration (KB 1004091)
  • Storage VMotion on Virtual Machine with I/O Intensive Workload May Result Incorrectly in a Timeout Error (KB 1003276)
  • Virtual machine CPU usage spikes and remains abnormally high after VMotion in a VMware DRS enabled cluster (KB 1003638)
  • Virtual Machines with Large Memory Size Fails to Migrate when Migrate.MemChksum is Enabled
    Migrating virtual machines fails when one of the following occurs:
    • You enable Migrate.MemChksum (value is set to 1) on both source and destination ESX hosts.
    • The virtual machine has a memory size of more than 4GB.
  • The migration times out and the following error appears in the vmware.log file:
    MigrateStatusFailure: Failed waiting for data. Error bad0007. Bad parameter>
    and the VI Client reports the following error: A general system error occurred: Failed waiting for data. Error bad0007. Bad parameter.
    Workaround
    Configure the value of the following variables in the source and the destination ESX hosts. The variables are available under Configuration > Advanced Settings > Migrate:
    • Migrate.PageInTimeoutResetOnProgress: Set the value to 1.
    • Migrate.PageInProgress: Set the value to 30, if you get an error even after configuring the Migrate.PageInTimeoutResetOnProgress variable.

Miscellaneous

  • Guided Consolidation Feature Fails to Consolidate the Datacenter When Non-ASCII Characters are Used In Machine Names, Workgroup Names, or Windows Domain Names
    When non-ASCII characters are used in machine names, workgroup names, or Windows domain name, and if the Guided Consolidation feature is used, the VirtualCenter Server fails to consolidate the datacenter. An error message similar to the following appears:
    VirtualCenter must gather more information to enumerate the domains and workgroups in the enterprise. This may take several minutes. Try again later.
    Workaround: Starting with the Virtual Center 2.5 Update 2 release, to analyze a machine with non-ASCII characters in its name or its workgroup's name, manually add the machine's IP address in the Guided Consolidation wizard.
    For releases prior to VirtualCenter Server 2.5 Update 2, rename machine names, workgroup names, and Windows domain names to use only ASCII characters. In addition, remove machine names, workgroup names, and Windows domain names that have non-ASCII characters from the data collector’s Microsoft Access database, by performing the following steps:
    1. To prevent the VirtualCenter Server from locking up the Microsoft Access database of the data collector, and to prevent the VirtualCenter Server from attempting to start the VMware Capacity Planner service, stop the VMware VirtualCenter Server Windows service.
    2. To prevent the data collector from attempting to modify the Microsoft Access database, stop the VMware Capacity Planner Service Windows service.
    3. Open the embedded data collector database (AOGCapPlan.mdb) in Microsoft Access 2000 or a later version.
    4. From the CoreGroups table, in the Tables tab, delete the rows that have non- ASCII characters.
    5. Save the changes, and close Microsoft Access.
    6. Start the VMware VirtualCenter Server Windows service.
  • The Administrator Does Not Have Access to Virtual Machine Hard Disk Settings When the Access is Restricted Only to a Single Virtual Machine
    If the administrator has access only to a single virtual machine and the permissions on ESX are not propagated, the administrator cannot view or edit the virtual machine hard disk settings available under Edit Settings > Hardware > Hard Disk.
    The following error appears when the administrator tries to edit the settings:
    Exception of type Vmomi.Fault.NoPermission.
    In this release, you can view the hard disk settings. To extend the hard disk size or edit the settings, you must have additional permissions at the datacenter.

Networking

  • SNMP Trap Messages for Predictive Failures Disks Are Not Appropriate
    The SNMP trap messages for predictive failure disks are changed from messages similar to VMWARE-ENV-MIB::vmwEventDescription.4 = STRING: "Drive 1 in enclosure 32 on controller 0 - ONLINE"  to messages similar to  VMWARE-ENV-MIB::vmwEventDescription.4 = STRING: "Drive 1 in enclosure 32 on controller 0 - PREDICTIVE FAILURE".
  • ESX Server Host Crashes When Unloading Bnx2x Driver
    This release resolves an issue where the ESX Server host crashes when unloading the Bnx2x driver. An error message similar to the following might be displayed:
    VMware ESX Server [host name]
    Exception type 14 in world 1027:idle3 @ 0xa575d7
  • Updates the Samba Package Distributed With the ESX Server Service Console
    This release fixes an issue with the heap-based overflow flaw found in the Samba package that allows remote attackers to execute arbitrary code.
    Thanks to Alin Rad Pop of Secunia Research for identifying and reporting this issue.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-1105 to this issue.

Server Configuration

  • .config File Missing In the ESX Server Service Console
    Previously, the ESX Server service console kernel-source package omitted the .config file that directs which Linux kernel options are to be enabled. The kernel-source package now provides a .config file, which enables OEM Management Agent packages like Dell OpenManage, HP Insight Manager, and IBM Director to build their kernel modules.
  • Updates to the Service Console to 2.4.21-57 (RHEL3U9)
    This fix upgrades the service console kernel version to kernel-2.4.21-57.EL. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2007-5001, CVE-2007-6151, CVE-2007-6206, CVE-2008-0007, CVE-2008-1367, CVE-2008-1375, CVE-2006-4814, and CVE-2008-1669 to the security issues fixed in kernel-2.4.21-57.EL.
  • ESX Server Installer Does Not Create vmfs and vmkcore Partitions Correctly (KB 1004075)
  • Ramchecker Service Fails to Start on the ESX Server 3.5 Versions
    The Ramchecker utility is not supported, and does not work on ESX Server 3.5 versions. Starting with this release, to prevent the installation of the Ramchecker utility, the Ramchecker service is removed from the VMware-esx-lnxcfg RPM, and the Ramchecker binary is removed from the VMware-esx-apps RPM.
    On ESX Server 3.5 and ESX Server 3.5 Update1 systems, the Ramchecker service fails to start, with an error message similar to the following:
    Starting ramchecker /usr/lib/vmware/bin/ramcheck: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Error 28
  • Connecting a Remote CD-ROM or Floppy Drive to a Virtual Machine Fails With No Permission Error (KB 1004327)
  • -l Command Line Option Can Be Used In the esxtop Utility to Optimize CPU Utilization
    When several LUNs are added to an ESX Server and if the esxtop utility is used for collecting storage statistics, esxtop uses several CPU cycles to access VSI nodes and load meta information of adapters, targets, channels, luns, vcpus, nics, paths, worlds and so on for every update. The -l command line option can be used with esxtop to operate the esxtop utility in the lock mode. In the lock mode, CPU utilization is optimized as esxtop copies meta information from the previous snapshot instead of accessing the VSI nodes for every update.
    However, in the lock mode, storage statistics of new entities are not displayed.
  • "Permissions Issue Vmomi.Fault.NoPermission" error
    With VirtualCenter 2.5 and VirtualCenter 2.5 Update 1, if users are given the virtual machine power/virtual machine administrator user role at a resource pool level, they would get an Error message box with "Vmomi.Fault.NoPermission" while editing the virtual machine settings. This has been fixed in VirtualCenter 2.5 Update 2.
  • Dell Recovery CD Fails when recovery process is executed with a Virtual Floppy drive connected (KB 1004494)
  • CPU Affinity Settings do not Take Effect
    This release resolves an issue where CPU affinity settings do not take effect until the virtual machine is restarted.
  • ESX Server Displays Error on a Purple Screen During Memory Intensive Operations
    During memory intensive operations, ESX Server fails and displays the following error on a purple screen: Exception Type 14 in world.... This release fixes the issue.

Storage

  • Path Failover Might Not Complete Successfully with LSI3444E Under High Stress

    To ensure the IBM DS3200 SAS storage array provides proper path failover during heavy I/O in a VMware environment, you must reconfigure the Remove Device Missing Delay (RDMD) timer value to 10 seconds and the I/O Device Missing Delay (IODMD) timer value to 0 seconds in the BIOS for each SAS HBA. Failure to do so might cause I/O timeouts in the event of a SAS HBA failure or cable disconnect. The following error messages might be displayed in /var/log/vmkernel:

    Jan 29 10:59:29 stgbladeh101 vmkernel: 0:21:06:58.523 cpu1:1062)<4>mptscsih: ioc1: Attempting task abort on id=0! (sc=0x3e229200)
    Jan 29 10:59:29 stgbladeh101 vmkernel: 0:21:06:58.523 cpu1:1062)<4>mptscsih: ioc1: Abort ctx2abort=e00a1
    Jan 29 10:59:29 stgbladeh101 vmkernel: 0:21:06:58.537 cpu1:1062)LinSCSI: 3201: Abort failed for cmd with serial=31623, status=bad0001, retval=bad0001

    This issue is fixed in this release. You can retain the LSI default settings in the BIOS.

  • Virtual Machines Cannot Share a Raw LUN By Using Two Different RDM Files Unless RDM Filters Are Turned Off
    Starting with the ESX Server 3.5 Update 2 release, by default, two virtual machines cannot share a raw LUN by using different RDM files.
    When using the Microsoft Cluster Service, it might be required that two RDM files link to the same raw LUN. To enable two RDM files to link to the same LUN, RDM filters should be turned off in hostd and in the VirtualCenter Server by performing the following steps:

    1. To turn off the RDM filter in hostd, add the following lines in the /etc/vmware/hostd/config.xml file and restart hostd:
      <plugins>
             <solo>
                <rdmfilter>
                    <UsedAsVmRdm>false</UsedAsVmRdm>
                </rdmfilter>
             </solo>
          </plugins>

    2. To turn off the RDM filter in the VirtualCenter Server, in the VI Client, choose Administration ->Virtual Center Server Configuration, select Advanced Settings and add a row to set the vpxd.filter.rdmFilter variable to false.
  • Hot Addition/Deletion of LUNs on Virtual Machines as Raw Device Mappings (RDMs) Might Fail With Error Messages
    The following error message might be logged in hostd logs:

    Operation failed due to concurrent modification by another operation

    The above message happens in conjunction with another error: Foundry operation failed with system error: Device or resource busy while Hot Adding/Removing of RDMs
  • I/O Errors Occur after Device Is Removed from IBM DS3200 while Using LSI 3444E Adapter (KB 1004313)
  • VI Client displays the Current Firmware Version Used By the Server
    The Health tab in the VI Client displays the current firmware version that is being used by the ESX Server system.
  • VMKlinux Runs Out of Memory when Using an mptsas System with More Than 128 LUNs (KB 1004403)
  • File System Mount Info In the Managed Object Browser of a VirtualCenter Server Reflects VMFS or NFS Datastore Changes
    This release fixes an issue where the VMFS or NFS datastore changes fail to get reflected in the HostSystem > config > fileSystemVolume > mountInfo section in the Managed Object Browser (MOB) of a VirtualCenter Server.

Upgrade and Installation

  • ESX Server 2.x Upgrades to ESX Server 3.5 Update 2 Without Any Pegasus Error Messages
    When upgrading from ESX Server 2.x to ESX Server 3.5 Update 1, processing of Pegasus failed with an error message similar to the following:
    Processing /var/pegasus/vmware/install_queue/2 [FAILED]
    ERROR: See log - /var/pegasus/vmware/install_queue/2.log
    "Cimom not responding"

    This issue is resolved in the ESX Server 3.5 Update 2 release. For more information, refer KB 1004257
  • VMware Tools For Linux Virtual Machine Does Not Get Upgraded Properly
    While upgrading VMware Tools in a linux virtual machine after ESX Server host upgrade from versions 3i or 3.5 to ESX 35 Update 2, the vmhgfs module is not unloaded. This results in VMware Tools not getting upgraded properly. Running the command vmware-config-tools.pl for vmhgfs for module compilation might display the following error message:

    Trying to find a suitable vmhgfs module for your running kernel.

    This issue is fixed in this release.
  • ESX Server Hosts No Longer Go Into Disconnected State After Reinstalling VirtualCenter Server.
    The passwords used by VirtualCenter to connect to individual ESX Server hosts are encrypted with an SSL certificate. Uninstalling VirtualCenter Server no longer removes the SSL certificate folder. This permits a subsequent installation of VirtualCenter to use the same certificate, avoiding the host disconnection issue.
  • Patch Installation Might Require Obsolete Bundles to be Included in the Patch Depot (KB 1004363)
  • Upgrade Fails if VirtualCenter Database Name has More Than 20 Characters (KB 1004297)
  • Multiple VirtualCenter Servers Can Use The Same Microsoft SQL Database Server
    In the previous release, if multiple instances of VirtualCenter were installed using the same Microsoft SQL database server, only the last installed instance would have properly functioning statistics rollup jobs. In this release, each database has a unique set of statistics rollup jobs, allowing for multiple VirtualCenter installations to use the same database server. See KB 1003610 for more information.
  • Upgrading VMware Tools From ESX GA to a Later Version Fails
    This release resolves an issue where upgrading VMware Tools from ESX Server 3.5, ESX Server version 3.5 Embedded, or ESX Server version 3.5 Installable to a later version of the software (for example U1) (applies to all versions; ESX Server 3.5, ESX Server version 3.5 Embedded, and ESX Server version 3.5 Installable) might fail. The following error message might be displayed:
    A later version of 'VMware Tools' is already installed on this machine. The setup cannot continue.
  • During Installation of ESX Server 3.0.2 or ESX Server 3.5 the VMFS Partition Is Listed as Unknown on Partitioning Options Page (KB 1004032)
  • Garbage Values Cause VI Client and VC Server to Stop Responding.
    CDP is enabled (listen mode) on the vswitch by default when it is created. This results in passing of Virtual Infrastructure Client/Virtual Center Server invalid values in the OID field of the CDP packets, which causes the VI Client and the VC Server to stop responding.
  • VirtualCenter Database Upgrade Fails if SQL Server Database Name Contains a Space Character
    This release resolves an issue where VC database upgrade fails if SQL Server database name contains a space character. An error message similar to the following might be displayed:
    ERROR [42000] [Microsoft][SQL Native Client][SQL Server]The specified @database_name ('VMWARE Virtual Center') does not exist.
    (database name contains special characters).
  • File Existence Check Results in an Incorrect Error Message When Using esxupdate Command with a FTP Depot (KB 1004365)
  • Inconsistent File Naming of ESX Server Version 3.5 Update 1 Deliverables (KB 1004388)
  • VMware DRS Settings for Virtual Machines Are Lost When the VirtualCenter Server Is Upgraded
    This release fixes an issue where VMware DRS settings such as CPU and memory allocation settings for virtual machine are lost when the VirtualCenter Server is upgraded to a VirtualCenter 2.5 release.
  • Upgrading VMware Tools Using RPM on a Linux Guest Imported from Workstation Might Fail (KB 1004319)
  • ESX Server 3.0.1, ESX Server 3.0.2, and ESX Server 3.0.2 Update 1 Fail to Upgrade to ESX Server 3.5 Update 2
    ESX Server 3.0.1, ESX Server 3.0.2, and ESX Server 3.0.2 Update 2 fail to upgrade to ESX Server 3.5 Update 2, when the compressed bundle upgrade-from-esx3.0.x-3.5.0_Update_2-<build_number> is used with the depot (bundles directory). Executing the #esxupdate update command results in an error message similar to the following:
    [root@blr-2nd-1-dhcp308 upgrade-from-esx3.0.x-3.5.0_Update_2-100510]# esxupdate update
    INFO: No repository URL specified, going with file:/root/upgrade-from-esx3.0.x-3.5.0_Update_2-100510
    INFO: Configuring...
    ERROR: Invalid repository at file:/root/upgrade-from-esx3.0.x-3.5.0_Update_2-100510/: Cannot find descriptor.xml
    INFO: Make sure you have file: or http: prepended to the URL.

    Workaround: Apply patch ESX-1003519 on ESX Server 3.0.1, and patch ESX-1003525 on ESX Server 3.0.2 and ESX Server 3.0.2 Update 1, and then upgrade to ESX Server 3.5 Update 2 using the esxupdate -d (depot path of upgrade-from-esx3.0.x-3.5.0_Update_2-<build_number>) -b ESX350-Update02 update command with the esxupdate utility.
  • Performance data preserved when upgrading to VirtualCenter 2.5 using Oracle 9.2.0.8 database.
    In the previous release, performance data was lost after upgrading to VirtualCenter 2.5 using Oracle 9.2.0.8. An error message similar to the following might be logged in the database job log:

    ORA-12012: error on auto execute of job 49
    ORA-00001: unique constraint (VPX.VPX_SAMPLE_TIME4_U1) violated
    ORA-06512: at "VPX.STATS_ROLLUP3_PROC", line 223
    ORA-06512: at line 1

  • This issue is fixed in this release.

  • UTC Offset Time Zone Selector Provides Corrected US Time Zone Choices
    This release fixes an issue where the ESX Server installer incorrectly identifies UTC-5 through UTC-8 as US time zones, when providing UTC Offset options to set the time zone for the ESX Server being installed.
    Starting with the ESX Server 3.5 Update 2 release, the ESX Server installer correctly provides UTC+05 through UTC+08 as the UTC offset options for US time zones.
  • Filenames over 64 characters in ESX Server ISO image might get truncated during content extraction. (KB 1005283)
  • ESX Hosts No Longer Go Into Disconnected State After Reinstalling VirtualCenter Server.
    The passwords used by VirtualCenter to connect to individual ESX hosts are encrypted with an SSL certificate. Uninstalling VirtualCenter Server no longer removes the SSL certificate folder. This permits a subsequent installation of VirtualCenter to use the same certificate, avoiding the host disconnection issue.
  • Support for Guest Tools Installers to Detect Distribution-Specific Packages (DSP)
    In this release, the tar and rpm installers detect whether DSPs are present and the guest tools are already installed by checking for the presence of a marker file. If the file is present, the tar/rpm installer fails with an error message similar to the following:

    VMware Tools cannot be installed, since they have already been installed using a package-based mechanism (rpm or deb) on this system. If you wish to continue, you must first remove the currently installed VMware Tools using the appropriate packaged-based mechanism, and then restart this installer.


    If you encounter this error you can either retain the current tools installers and not install VMware Tools using DSPs, or remove the currently installed tools and then install tools using DSPs.
    Note: Without this fix, installing guest tools using the current tar-/rpm-based installers on a target system that already has guest tools installed using DSPs, might lead to errors.

Virtual Machine Management

  • Powered-off Virtual Machines Cannot be Unregistered from ESX Server host in Maintenance Mode.
    This release resolves an issue where powered-off virtual machines cannot be unregistered from the ESX Server host which is in maintenance mode. Trying to unregister virtual machines on an ESX Server host without this fix might generate the following error message: "A general system error: Invalid fault"
  • VI Client Closes on Certain Systems When Accessing the Remote Console of a Virtual Machine
    This release resolves an issue where certain dynamic link libraries on the client machine would cause the Virtual Infrastructure Client to close when accessing the remote console of a virtual machine. A non-related error message similar to the following might be displayed:

    Unable to power on VM: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
  • Cannot Browse vmimages Folder After Adding Hosts to a DRS-Enabled Cluster.
    This release resolves an issue where vmimages folder could not be browsed on an ESX Server host when the host is in DRS enabled cluster.

VirtualCenter, VI Client, and Web Access

  • VI Client Displays Incorrect Resource Share Values for VirtualCenter 2.5

    This release resolves an issue where the VI Client displays incorrect share values for VirtualCenter 2.5 when managing ESX Server 3.0.x and ESX Server 3.5 Server hosts.

    If you use the VI Client to access VirtualCenter 2.5, and then set a value of Low, Normal, or High for either CPU or Memory on a virtual machine, the value is set correctly on the ESX host, but an incorrect share value is displayed in your VI Client.

    The fix is for the virtual machine and the ResourcePool.
  • Support in VirtualCenter 2.5 Update 2 for manually adding computers for consolidation.
  • Virtual Center Alarm Definitions Now Accept More Than One Email Address
    In the previous release, Virtual Center Alarm Definitions would only accept one email address. In this release, Virtual Center Alarm Definitions accepts multiple email address, separated by semicolons.
  • VirtualCenter Server Process Continuously Spikes or Remains at 100% CPU Utilization And Eventually Fails.
    In the previous release, in environments with resource pools in clusters, the VirtualCenter Server process might continuously spike or stay at 100% CPU utilization, and, if left in this condition, eventually fail. This issue is fixed in this release.
  • Virtual Infrastructure Client Displays Information About Hot Spare Disks
    The Storage section in the Health Status panel of the Configuration tab in the Virtual Infrastructure Client indicates the physical disks that are configured as hot spare disks.
  • VirtualCenter Server Fails With Buffer Errors
    This release resolves an issue where the VirtualCenter Server fails while powering on a virtual machine whose backing file URL (for example, the datastore ISO file on NETFS) is more than 256 bytes. An error message similar to the following might be logged in vpxd logs at C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs

    Exception: C:/ob/bora-64192/bora/lib/string/str.c:192 Buffer too small 0x6dab39
  • Alarms Might Fail to Run Scripts with Parameters When Alarm Condition Is Reached
    This release fixes an issue where the VirtualCenter Server might fail to execute a script with parameters as part of the trigger action when the alarm condition is reached.
  • VirtualCenter Server Sends Property Update Notifications When Datastore Attributes Change at the Compute Resource Level
    VirtualCenter Server sends property update notification when any datastore change at the compute resource level is detected. Client applications can now receive update notification provided a property filter is created to receive notification for any changes to the datastore attribute at the compute resource level.
  • VirtualCenter 2.5 License File Might Not Work
    This release resolves an issue where an ESX Server host cannot be added to the VirtualCenter Server after installing VirtualCenter 2.5 license file on VMware License Server. The following error message might be displayed:
    There are not enough licenses to perform the operation
  • Virtual Machine Console Closes Unexpectedly When Collapsing Its Parent Resource Pool Branch
    In the previous release, the Virtual Machine Console would close unexpectedly when its parent resource pool branch was collapsed. This issue is fixed in this release.
  • Virtual Infrastructure Client Continues As Expected When Selecting Another Host While Viewing The Cisco Discovery Protocol Window
    In the previous release, navigating to the Cisco Discovery Protocol window and then selected another host, caused the Virtual Infrastructure Client to stop responding. This release fixes this issue.
  • Virtual Infrastructure Update Installation is Optional in the VI Client Installer
    In this release, the update service installation has been made optional (non-default) in the VI Client installer. To install Virtual Infrastructure Update, enable the check box in the VI Client installer. If this option is selected but an older version of VI Update is already installed on the system, VI Update will automatically be upgraded to the new version. If this option is selected but a later version of VI Update is already installed on the system, VI Update won't be installed.
  • In Non-English Virtual Infrastructure Client, a Performance Chart With Custom Duration Is Displayed Correctly
    In the previous release, when you use a non-English Virtual Infrastructure Client, a saved performance chart with custom duration would display performance data incorrectly. This issue has been fixed in this release.
  • Non Alpha Numerical Characters Are Supported in Annotations of Virtual Machines and ESX Server Hosts
    This release fixes an issue where, if non alpha numerical characters are used in the Notes text box while adding annotations to virtual machines or ESX Server hosts, VirtualCenter Server stops responding and logs an entry similar to the following in the vpxd.log file:
    Unhandled exception: not well-formed (invalid token).
  • VirtualCenter Server Fails to Add ESX Server 2.5.x Hosts That Are Not SSL Authentication Enabled
    Starting with the VirtualCenter 2.5 Update 2 release, the VirtualCenter Server fails to connect to ESX Server 2.5.x hosts that are not SSL authentication enabled, with an error message similar to the following:
    Unable to access to the specified host. It either does not exist, the server software is not responding, or there is a network problem.
    After upgrading to the VirtualCenter 2.5 Update 2 release, ensure that SSL authentication is enabled on an ESX Server host before adding it to a VirtualCenter Server. To enable SSL authentication in the ESX Server host, perform the following activities:
    1. In the /etc/vmware/config file, replace the line security.host.ruissl = "FALSE", with the line security.host.ruissl = "TRUE".
    2. Restart the xinetd service by using the # service xinetd restart command.

 

Top of Page

Installing the Language Pack on the ESX Server Host

For German, Japanese, or Simplified Chinese language support when you use Virtual Infrastructure Web Access or the VI Client with your ESX Server host, you must install the language pack.

To install the language pack:

  1. Download the VMware-ESXlangpack-2.5.0-85586.zip file from the download site.
  2. Extract the contents of the ZIP file into a temporary directory.
  3. Copy the files from the ESX Server/webAccess/ directory to the VI Web Access installation directory on your ESX Server host (usually /usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.26/webapps/).

    cp -pr ESX Server/webAccess/webapps/ui /usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.26/webapps/
    cp -pr ESX Server/webAccess/webapps/WEB-INF /usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.26/webapps/ui/

  4. Copy the localized files into the appropriate directory:

    For German use the following command:
    cp -pr ESX Server/docroot/de /usr/lib/vmware/hostd/docroot/

    For Japanese use the following command:
    cp -pr ESX Server/docroot/ja /usr/lib/vmware/hostd/docroot/

    For Simplified Chinese use the following command:
    cp -pr ESX Server/docroot/zh-CN /usr/lib/vmware/hostd/docroot/

  5. Edit the /etc/vmware/hostd/config.xml file to enable the correct default language. Find the following lines in config.xml
       <locale>
          <DefaultLocale>en_US</DefaultLocale>
       </locale>

    For German, replace the lines with the following:

       <locale>
          <DefaultLocale>de_DE</DefaultLocale>
       </locale>

    For Japanese, replace the lines with the following:

       <locale>
          <DefaultLocale>ja_JP</DefaultLocale>
       </locale>

  6. For Simplified Chinese, replace the lines with the following:

       <locale>
          <DefaultLocale>zh_CN</DefaultLocale>
       </locale>

  7. Type the following commands to restart VI Web Access and host agent services:

    service mgmt-vmware restart
    service vmware-webAccess restart

 

Top of Page