VMware ESX Server 3.5 Update 5 Release Notes


VMware ESX Server 3.5 Update 5 | 03 Dec 2009 | Build 207095

Note: As part of the end of availability for some VMware Virtual Infrastructure product releases, the ESX 3.5 Update 5 upgrade package ESX350-Update05.zip has been replaced by ESX350-Update05a.zip in order to remove dependencies upon patches that will no longer be available for download. Hosts upgraded using ESX350-Update05a.zip are equivalent to those upgraded using the older package, but patch bundles released before ESX 3.5 Update 5 will not be required during the upgrade process.

Last Document Update: 06 May 2010

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


  1. Not all combinations of VirtualCenter and ESX Server versions are supported. All of these highlighted features are available only if you are using VirtualCenter 2.5 Update 5 with ESX Server 3.5 Update 5. See the ESX Server, VirtualCenter, and VMware Infrastructure Client Compatibility Matrixes for more information on compatibility.
  2. VMware recommends VMware Tools upgrade for this version of ESX Server.

The following information provides highlights of some of the enhancements available in this release of VMware ESX Server:

Enablement of Intel Xeon Processor 3400 Series – Support for the Intel Xeon processor 3400 series has been added. Support includes Enhanced VMotion capabilities. For additional information on previous processor families supported by Enhanced VMotion, see Enhanced VMotion Compatibility (EVC) processor support (KB 1003212).

Driver Update for Broadcom bnx2 Network Controller – The driver for bnx2 controllers has been upgraded to version 1.6.9. This driver supports bootcode upgrade on bnx2 chipsets and requires bmapilnx and lnxfwnx2 tools upgrade from Broadcom. This driver also adds support for Network Controller - Sideband Interface (NC-SI) for SOL (serial over LAN) applicable to Broadcom NetXtreme 5709 and 5716 chipsets.

Driver Update for LSI SCSI and SAS Controllers – The driver for LSI SCSI and SAS controllers is updated to version 2.06.74. This version of the driver is required to provide a better support for shared SAS environments.

Newly Supported Guest Operating Systems – Support for the following guest operating systems has been added specifically for this release:

For more complete information about supported guests included in this release, see the VMware Compatibility Guide: http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software.

  • Windows 7 Enterprise (32-bit and 64-bit)
  • Windows 7 Ultimate (32-bit and 64-bit)
  • Windows 7 Professional (32-bit and 64-bit)
  • Windows 7 Home Premium (32-bit and 64-bit)
  • Windows 2008 R2 Standard Edition (64-bit)
  • Windows 2008 R2 Enterprise Edition (64-bit)
  • Windows 2008 R2 Datacenter Edition (64-bit)
  • Windows 2008 R2 Web Server (64-bit)
  • Ubuntu Desktop 9.04 (32-bit and 64-bit)
  • Ubuntu Server 9.04 (32-bit and 64-bit)

Newly Supported Management Agents – See VMware ESX Server Supported Hardware Lifecycle Management Agents for current information on supported management agents.

Newly Supported Network Cards – This release of ESX Server supports HP NC375T (NetXen) PCI Express Quad Port Gigabit Server Adapter.

Newly Supported SATA Controllers – This release of ESX Server supports the Intel Ibex Peak SATA AHCI controller.

  • Some limitations apply in terms of support for SATA controllers. For more information, see SATA Controller Support in ESX 3.5. (KB 1008673)
  • Storing VMFS datastores on native SATA drives is not supported.

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:

Top of Page

Before You Begin

ESX Server, VirtualCenter, and VMware Infrastructure Client Compatibility

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

Hardware Compatibility

  • Learn about hardware compatibility:

    The Hardware Compatibility Lists are now available on the Web-based Compatibility Guide at http://www.vmware.com/resources/compatibility. This new format is a single point of access for all VMware compatibility guides. The previous PDF versions will no longer be updated. The Web-based Compatibility Guide provides the option to search the guides, and save the search results in PDF format.
    Subscribe to be notified of Compatibility Guide updates via This is the RSS image that serves as a link to an RSS feed.

  • Learn about VMware Infrastructure compatibility:

    VMware Infrastructure Compatibility Matrixes (PDF)


All the documentation for ESX Server 3.5 Update 4 applies to ESX Server 3.5 Update 5 as well. For a complete list of manuals and other documentation, see VMware Infrastructure 3 Documentation.

Top of Page

Installation and Upgrade

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:

Upgrading or Migrating to ESX Server 3.5 Update 5

This release of ESX Server 3.5 Update 5 allows upgrades only from previously supported versions. The ESX Server 3.5 Update 5 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.

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

Upgrade Type ESX Server 3.0.1 ESX Server 3.0.2 ESX Server 3.0.3 ESX Server 3.5 ESX Server 3.5
Update 1
ESX Server 3.5
Update 2
ESX Server 3.5
Update 3
ESX Server 3.5
Update 4
Upgrade ZIP No No No Yes Yes Yes Yes Yes
ISO image Yes Yes Yes Yes Yes Yes Yes Yes

  • For ESX Server 2.5.x, upgrade first to ESX Server 3.0.1 or higher and then upgrade to ESX Server 3.5 Update 5 using an ISO image. Alternatively, upgrade to ESX Server 3.5 or higher and then upgrade to ESX Server 3.5 Update 5 using an ISO image or Upgrade ZIP bundle.

  • 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 5 by using an ISO image. Alternatively, upgrade to ESX Server 3.5 and then upgrade to ESX Server 3.5 Update 5 using an ISO image or Upgrade ZIP bundle.

  • Upgrade from ESX Server 3.5 Update 5 to ESX Server 4.0 is not supported. However, you can upgrade to ESX Server 4.0 Update 1.

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

Updated RPMs and Security Fixes

For a list of RPMs updated in ESX Server 3.5 Update 5, see Updated RPMs and Security Fixes. This document does not apply to the ESX Server 3i products.

Upgrading VMware Tools

VMware recommends VMware Tools upgrade for this version of ESX Server. The VMware Tools version should be 7.4.8. The Windows SVGA driver version is upgraded to

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 for more information on the individual patches.

ESX Server 3.5 Update 5 contains all the fixes in ESX Server 3.5 Update 4 and the following patches released after ESX Server 3.5 Update 4:

In addition, ESX Server 3.5 Update 5 fixes new issues (see the Resolved Issues section) and these issues are also released in the following individual patch bundles:

Top of Page

Resolved Issues

This release resolves issues in the following subject areas:


  • The vcbSnapAll command might fail with an error when backup_destination is set as scp. This issue is resolved in ESX 3.5 Update 5.


  • In earlier releases of ESX Server, on some Dell MLK hardware, the NumberOfBlocks property for OMC_Memory instance has a value of 0.

  • Log is filled with storelib Physical Device Device ID messages
    In some cases, providers using LSI Logic drivers (megaraid2, megaraid_sas, mptscsi) repeatedly log messages such as storelib Physical Device Device ID and fill up the /var/log/messages log file. These messages are part of debug code. In this release, these debug code messages are not logged at this location.

  • A debug message is logged every two minutes in the system log
    The following debug message is logged every two minutes in /var/log/messages:
    trying to open /sbin/modprobe edd 2>&1

  • On ESX Servers hosts that do not have any LSI controllers, LSI providers repeatedly log the message failed to get TopLevelSystem in the system log. In this release, this message is not logged if the LSI controllers are not present.

  • vSphere Client shows memory status of the host machine as Unknown on the servers running ESX Server 3.5 Update 4
    On servers running ESX Server 3.5 Update 4, the dual in-line memory modules (DIMM) display the memory status as Unknown, whereas the DIMMs on other systems show potentially incorrect status as OK.

  • Health Status and storage-related information are changed on the VI Client after upgrading to ESX Server 3.5 Update 4
    After upgrading to ESX Server 3.5 Update 4, the Health Status and storage-related information are changed on the VI Client. Also, using the CIM client, if you make an EI operation on some of the classes, such as VMWARE_StorageExtent, you get an error message similar to the following:

    /var/pegasus/bin/cimcli CIMException: Cmd= enumerateInstances Object= VMWARE_StorageExtent
    ProviderLoadFailure: (/var/pegasus/lib/libvmwprovider.so) Provider is not a CMPI style provider. Cannot find VMware_StorageExtent_Create<mi-type>MI symbol.

Guest Operating Systems

  • Increased the I/O timeout value for Linux guest operating systems that have 2.6.13 or greater kernel version
    Starting with ESX 3.5 Update 5 release, VMware Tools installs a udev rule file on Linux operating systems with kernel version greater than or equal to 2.6.13. This rule file changes the default timeout value of VMware virtual disks to 180 seconds. This helps the guest operating system to survive better during a failover scenario.

  • The memory scrubber service in Solaris pops memory balloon
    The memory scrubber service in Solaris pops memory balloon by accessing the memory pages reserved by the balloon driver. In this release, the memory scrubber service is disabled when the balloon driver is loaded, thereby reducing the memory balloon pop rate.

  • The balloon driver is reset frequently on Solaris virtual machines
    Some Solaris virtual machines frequently reset the balloon driver. In this release, two parameters are introduced that lets you disable ballooning. These parameters are:

    • sched.mem.balloon.resetlimit: Number of balloon resets after which the ballooning function is disabled. The default value is 12.
    • sched.mem.balloon.decayperiod: Number of seconds after which the value of the reset counter is halved. The default value is 43200 seconds (12 hours).

    These parameters can be configured in the .vmx file. When the sched.mem.balloon.resetlimit parameter becomes zero, ballooning is disabled. After ballooning is disabled on a virtual machine, you can enable it only by restarting the virtual machine.

  • Applications requiring the msvcp71.dll file fail to open if the VSS component is uninstalled
    If you uninstall VMware Tools or the VSS components of VMware Tools, applications that require the msvcp71.dll file fail to open when the virtual machine is rebooted. This issue is fixed in this release.

  • The Virtual Machines tab in VirtualCenter displays Windows 2008 Server virtual machines as Windows Vista virtual machines.

  • Guest operating system's memory usage is overestimated causing memory alarms in VirtualCenter Server to go off spuriously
    A guest operating system's memory usage might be overestimated on Intel systems that support EPT technology or on AMD systems that support RVI technology. This might cause the memory alarms in the VirtualCenter Server to go off even if the guest operating system is not actively accessing a lot of memory.

  • VMware Tools installation prompts for the i8042prt.sys file on Windows XP Embedded virtual machine
    When installing VMware Tools on a Windows XP Embedded virtual machine, the installer might prompt for the i8042prt.sys file. You must manually select this file from C:\Windows\system32\drivers and click OK.
    Note: In this case, the \Windows\system32\drivers folder path is assumed to be on the C: drive.

  • Windows virtual machines fail with blue screen when accessed through RDP sessions.
    Some Windows virtual machines might fail with an error on blue screen when accessed through a Remote Desktop Protocol (RDP) session.

  • Java applications running in SMP (Symmetric Multi-Processing) virtual machines with VMI enabled might fail.

  • Auto-upgrade of VMware Tools on a Windows virtual machine requires manual intervention
    During an auto-upgrade of VMware Tools on a Windows virtual machine through the VI client, the installer might display a dialog box requesting user input. To finish the upgrade process, you must log in to the virtual machine and respond to the dialog box. In this release, the issue is fixed and the auto-upgrade process completes without any manual intervention.

  • Virtual machines using the Virtual Machine Interface (VMI) might boot very slowly.

  • A virtual machine using the Virtual Machine Interface (VMI) might stop responding. This issue is resolved in the ESX Server 3.5 Update 5 release.

  • Symmetric Multi-Processing (SMP) virtual machines utilizing AMD's Rapid Virtualization Indexing (RVI) feature might display a black screen up to 30 seconds after powering on.

  • VMware Tools upgrade overwrites the SVGA driver without checking the version of the existing SVGA driver.

  • VMware Tools repair or modification fails with a fatal error
    When you repair or modify VMware Tools on a virtual machine from Control Panel > Add/Remove program, the installer fails and rolls back with the error Fatal Error during Installation. In this release, the repair option from Control Panel > Add/Remove program is removed. You must instead run setup.exe directly from the original media that was used for a fresh installation.

VMware High Availability (HA)

  • ESX automatically enables firewall after VMware HA traffic, VMotion, cloning, or patching
    When performing certain operations such as vMotion, cloning, configuring HA, or patching in ESX host, the ESX console operating system firewall might revert to a previously stored configuration. This reversion occurs if you have changed the firewall configuration with tools other than the supported esxcfg-firewall command.
    Do not disable the firewall by running the chkconfig firewall off command or by blocking the firewall startup script. To disable the firewall, configure it to pass all traffic by running the esxcfg-firewall --allowIncoming --allowOutgoing command.
    Do not change the active firewall configuration by using the iptables command or any other Linux firewall management commands. Manage the console operating system firewall configuration only with the esxcfg-firewall command, vSphere, or VI Client.
    To manage the console operating system firewall configuration using the vSphere Client:

    1. Select the host in the Inventory panel.
    2. Select the Configuration tab.
    3. Click Security Profile.
    4. Click the Properties link.
    5. Edit the configuration details in the Properties window.

    If you want to add a new firewall service definition, create an additional XML file in the /etc/vmware/firewall directory. You can then enable the new service using the esxcfg-firewall -e <newservicename> command.
    If you want to enhance an existing ESX-provided service, copy its XML definition from the original file in the /etc/vmware/firewall directory (services.xml or one of the other files). Provide a name to the new service to distinguish it from the original service (which will still be available under the old name). You should then disable the old service and enable the new one. For example, esxcfg-firewall -d ftpClient -e myFtpClient.
    Do not modify the original ESX-provided firewall XML files. These files might be replaced by a patch or upgrade later and might remove your changes.


  • Virtual machine powers off when VMotion fails
    When VMotion fails because of high memory-intensive load of virtual machines or any similar issue, the virtual machine might get powered off. This issue is resolved in this release, allowing virtual machines to continue functioning on the source if VMotion fails.


  • ESX Server host might fail with a purple screen error during shutdown or reboot if the pegasus and wsman deamons are not stopped. This issue is fixed in this release.

  • ESX Server fails to boot and displays a purple screen on some ASUS systems
    As per ACPI specifications, data formats returned by the _PRS and _CRS methods must match for any interrupt link devices implementing them. If the BIOS incorrectly implements different formats, the ESX Server might fail to boot and display a purple screen. The fix detects inconsistency in data formats and lets the system boot ignoring the faulty information.

  • File permission issues when reading swap on NFS
    The file permission issues have been fixed in this release.

  • Memory reclaimed from idle virtual machines even though free memory is available
    In a configuration that contains multiple virtual machines with large memory sizes, memory reclamation is triggered on idle virtual machines even though there is free memory available. This issue is resolved in this release.

  • Configuration Data is Lost Upon Reboot
    If the / partition of the ESX Server service console is full, any command that modifies esx.conf results in the loss of all configuration data. For example, when the file system is full, attempts to modify vswitch configuration result in loss of all configuration data. As a result, networking fails after reboot. This release of ESX Server fixes this issue preventing data loss under such a condition. Also, an error message mentioning that the filesystem is full is displayed.


  • ESX Server does not detect CDP information on Intel MT or PT NICs after native VLAN change (KB 1006379)

  • ESX host fails if its available TCP/IP sockets are exhausted and an NFS Client has a directory mounted.

  • TSO frames are disabled on all tg3 NICs
    tg3 NICs have a long history of problems with TSO (TCP segmentation offload) frames and their implementation does not provide any significant boost. Starting with this release, TSO frames are disabled on all tg3 NICs.

  • ESX Server might stop responding if the bnx2 NIC is reset by NetWatchDog
    If the bnx2 NIC is reset by NetWatchDog, bnx2 initialization fails. This release of ESX Server introduces a fix that stops resetting the NIC if it fails initialization five times by NetWatchDog and displays a message similar to the following:
    Jul 15 10:17:09 prme-stg270 vmkernel: 0:00:12:51.090 cpu12:1127)<5>bnx2: giving up resetting vmnic1 initialization failed 4 times

  • Excessive serial logging in large PCPU systems might cause ESX Server hosts to fail with messages on a purple screen
    In the case of excessive serial logging in large PCPU systems, ESX Server hosts might fail with messages on a purple screen. This release of ESX Server modifies the behavior of serial logging of ESX Server hosts. By default serial logging is enabled. In VirtualCenter Server, the logSynchronous option is removed. This option is accessible from VirtualCenter > Configuration > Advanced Settings > VMkernel > Boot > logSynchronous. You can now enable or disable serial logging as follows:

    • From VirtualCenter Server: Set the Misc.LogToSerial option to an appropriate value. This option can be accessed from VirtualCenter > Configuration > Advanced Settings > Misc.
    • From ESX Server: Run the following command from the service console:
      esxcfg-advcfg –s <value> /Misc/LogToSerial

  • Systems with Intel igb card generate a large number of interrupts per second
    This issue is fixed in this release. With this fix, systems with Intel igb cards run in dynamic conservative mode by default and have a lower rate of interrupts per second. Also, the TCP throughput performance is optimum.

  • The esxcfg-firewall command throws a panic error if wrong input is provided when opening multiple ports. This issue is fixed in this release.

  • New command options added to set and get the value for maxActive uplinks
    This release of ESX Server introduces new options for the esxcfg-vswitch command. These options are -X and -x, and let you to set and get the value for maxActive uplinks respectively.

  • ESX Server installed on a Dell 6650 server with BCM5700 NICs might stop responding with a purple screen error.

  • NetQueue is disabled by default in unm_nic
    In ESX Server 3.5 Update 5, NetQueue is disabled by default in the NetXen driver. Currently, VMware does not support NetQueue on the NetXen driver.

  • Fixes a buffer corruption issue that occurs in hostd when multiple clients simultaneously establish a connection with an ESX Server host.

  • Linux guest operating systems lose network connectivity after VMware Tools upgrade
    If VMware Tools is upgraded on a Linux guest operating system, the guest operating system loses network connectivity. After the upgrade, the guest operating system stops the network service and does not restart the service automatically. This issue occurs even for an automatic upgrade of VMware Tools on linux guest operating systems.

  • This release of ESX Server supports the esxcfg-nic -a command for BCM5715S NIC in ESX Server 3.5

  • Firewall service is stopped when the system is switched to the single user mode
    When the system is in the single user mode, all the network-related services, including the firewall services, are stopped. When the system is switched back to multi-user mode, firewall service and all other network-related services are restarted automatically.

  • ESX Server fails with Exception 14 in world vsi_traverse when running the vm-support command.


  • This update release does not address any new security issues. It does include all the previously released security fixes.

Server Configuration

  • Guest operating systems can access SCSI CD-ROM (KB 1008673)

  • Insufficient memory for COS results in system failure with purple screen error
    In ESX Server 3.5 Update 5, the memory reserved for the Console OS (COS) is increased, thereby reducing the possibility of a server failure due to lack of memory. This increased memory reservation is available only if you perform a fresh installation of ESX Server 3.5 Update 5. If you upgrade to ESX Server 3.5 Update 5 from an earlier version of ESX Server, the memory settings from the earlier version are retained. In this case, you might want to manually increase the reserved memory and swap depending on your COS memory requirements. You can increase the reserved memory and swap by following the instructions provided in Increasing reserved physical memory for COS and swap to avoid ESX Server failure (KB 1013243).

  • This release of ESX Server includes a fix that provides a mechanism to improve the performance of ESX Server hosts which might be impacted due to IRQ sharing. See ESX Server 3.5 Might Display Performance Issues Due to IRQ Sharing (KB 1003710) for more details.

  • Starting with this release, users can set the NTP properties in the UTC time zone by using VI Client after installing ESX Server.


  • Updated RDM size is not displayed on the virtual machine
    In earlier releases of ESX Server, the updated RDM size is displayed on the virtual machines only if the ESX Server is restarted. Starting with this release, the updated RDM size is displayed in the virtual machines by running the LUN rescan. You need not restart the ESX Server.

  • Multiple rescans of VMFS volumes on ESX Server results in error on a purple screen
    Running multiple rescan of VMFS volumes on ESX Server machines that have IBM Director agents installed might result in an error on a purple screen.

  • This release fixes an issue where virtual machines might power off during a snapshot operation when path failover occurs on the storage where virtual machines reside.

  • Microsoft cluster in CIB configuration might failover due to VMFS activity
    In a CIB (Cluster-in-a-box) configuration, a failover might occur due to reservation conflicts arising from VMFS operations performed by another host sharing the same volume. When the conflict arises, SCSI errors are logged in the Windows event log.

  • VMFS heartbeat corruption is encountered in the VMFS volumes resulting in failure of virtual machines
    In prior releases, when VMFS heartbeat corruption is encountered in the VMFS volumes, virtual machines might fail to power on. However, the expected messages indicating heartbeat corruption for the VMFS volume are not logged in the VMkernel logs. In ESX 3.5 Update 5, log messages similar to the following are logged in the VMkernel logs:

    Mar 24 17:06:25 blr-2nd-1-dhcp274 vmkernel: 0:01:34:08.655 cpu4:1039)WARNING: FS3: ReadHostPulse:1017: FS 49c2390a-1976a3cb-1449-001aa0ae5b61 may be damaged.
    Mar 24 17:06:25 blr-2nd-1-dhcp274 vmkernel: 0:01:34:08.666 cpu4:1039)WARNING: FS3: ReadHostPulse:1028: Corrupt heartbeat detected at offset 0x3b9e00: [state 0 offset 0 gen 0 owner 00000000-00000000-0000-000000000000 journalAddr 0

    If you want to resolve these log messages, contact VMware support.

  • After the user unmaps a few LUNs from EMC Invista or EMC DGC storage arrays and rescans the LUNs on ESX hosts, the warning message: D:0x0/H:0x0 0x0 0x0 0x0 appears. This warning message is fixed in ESX 3.5 Update 5.

  • The vport count is inconsistent when several multiple-NPIV configured virtual machines are started simultaneously
    This issue occurs because the virtual ports are not created for all virtual machines. This release of ESX Server fixes the inconsistency in the number of virtual ports created on the proc node.

  • A race condition in the DentryCache initialization causes the system to fail with an error on a purple screen.

  • VMotion times out on ESX Server hosts that have large number of inactive VMFS volumes
    On ESX Server hosts that have many inactive VMFS volumes, VMotion might fail. Also, the virtual machines on such hosts might take a long time to power on.

  • Active path cannot be marked OFF if there is active I/O operation on the target storage array
    In earlier releases of ESX Server, you can mark the active storage paths OFF anytime by running the esxcfg-mpath command from the service console of the ESX Server host or through the VI Client or VirtualCenter Server. Starting with ESX 3. 5 Update 5, the active path cannot be marked OFF if there is active I/O operation on the target storage array or when there is active reservation on the storage path. However, the non-active paths may be marked OFF any time.

Upgrade and Installation

  • Ability to install ESX Server using an NFS server configured for TCP support (KB 1015512)

  • The upgrade procedure fails with the More than one vmkernel found error when upgrading from ESX 3.5 to ESX 3.5 Update 2. This issue might occur when upgrading from ESX 3.5 to any ESX 3.5 update releases prior to ESX 3.5 Update 5.

  • The esxupdate command does preserve customized settings in /etc/yum.conf
    Custom modifications made to the /etc/yum.conf file are overwritten when a patch or update release is installed and the modifications are lost. This issue is fixed in this release.

VirtualCenter, VI Client, and Web Access

  • "Requested registry access is not allowed" is displayed when a non-administrator user tries to launch VI Client (KB 1009284)

  • Configuring a portgroup to use the Route based on ip hash and Beaconing Probing policies causes duplication of packets
    Prior to this release, configuring a portgroup to use the Route based on ip hash policy for Load Balancing and the Beacon Probing policy for Network Failover Detection results in the duplicate packets. Starting with this release, VI Client disallows such a configuration and displays the following error message:
    Setting Network Failover Detection to "Beacon Probing" and Load balancing to "Route based on ip hash" at the same time is not a valid configuration. Please change your settings.
    However, a few corner cases do exist, which lets a portgroup to inherit a policy setting, and therefore might have the Route based on ip hash and Beaconing Probing policies set on it.

  • I/O error occurs when downloading a large file from the datastore browser or when exporting a virtual appliance to OVF
    In prior releases, when downloading or uploading a large file using the datastore browser an I/O error might be displayed. This issue also occurs when exporting a virtual appliance to OVF.

  • VI Client displays a large number of log messages containing the text DiagnosticMgr.Browse in the hostd logs
    If you connect directly to an ESX Server host using VI Client and click the Show All button in Administration > System Logs, large number of log messages with the text DiagnosticMgr.Browse might be displayed in the hostd logs. This issue occurs due to an error in the calculation of the end of log by VI Client. This error has been rectified in this release.

Virtual Machine Management

  • ESX Server host might stop responding during shutdown, in a specific use case that arises, only if virtual machines on the host are configured for autostart/autostop. In this release of ESX Server, the script that handles auto start and stop of virtual machines is fixed to address this issue.

  • This release of ESX Server resolves an issue of poor performance of the virtual machines for a short duration immediately after VMotion of virtual machines between ESX Server hosts.
    The following scenarios might lead to the occurrence of this issue:

    • A guest operating system is using large page files frequently
    • Virtual machines are already swapping before the start of VMotion

Top of Page

Known Issues

This section describes the known issues in this release of ESX Server. These issues are categorized under the following subject areas:


  • On an NEC Express 5800 140Ba-10 server the cimprovagt or cimserver process runs up to 99% of CPU 0 on the COS. As a result, the remaining applications, including snmpd, fail to perform.

  • After upgrading to ESX Server 3.5 Update 5, when ESX Server is restarted, Pegasus install queue failure error is reported during the boot process. (KB 1015294)

  • 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 by using the 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 a redundancy sensor that has two physical power supplies, the VI Client displays the redundancy sensor as Power Supplies for Power Supply 3.

  • Running a CallMethod query on a CIM_RecordLog instance might fail
    In ESX Server 3.5 Update 2 or later, running a CallMethod query on a CIM_RecordLog instance might not succeed at all times. You can, however, clear the system event log through a remote management console or interface.

  • Some CIM classes do not work properly on IBM Multinode systems
    For the following classes, the EnumerateInstances() operation returns one instance fewer than the EnumerateInstanceNames() 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
  • 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.

  • 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.

    Workaround: In the service console, open an outgoing port for connections to the indication consumer by 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

  • In the ESX Server 3.5 release, invoking the Reset() operation on numeric power supply sensors results in the following error message:
    CIM_ERR_FAILED: index out of bounds
    Workaround: Use the RequestStateChange(Reset) operation.
  • Indications do not work on ESX Server 3.5 when you use the WS-Man protocol.
  • The ModifyInstance() call to change sensor threshold fails when you use the WS-Man protocol.
  • The chassis intrusion indication is not available for IBM Athena servers.

  • InvokeMethod(RequestPowerStateChange) and InvokeMethod(RequestStateChange) fail when you use the WS-Man protocol

Guest Operating Systems

  • Solaris Update Manager fails to start and displays font-related errors on the xterm window. (KB 1013079)

  • VMware Tools fails to install SVGA driver automatically on Windows XP Embedded Studio (KB 1015250)

  • The XPDM SVGA driver of VMware Tools is unstable on Windows 7 (32-bit and 64-bit) and Windows 2008 R2. Therefore, this driver is not installed on virtual machines running these guest operating system releases. Upgrading to the current version of VMware Tools on these operating systems will also remove the SVGA driver, if it exists.

  • The Sleep option from the Shut Down option list in Windows 7 is unavailable
    In a Windows 7 virtual machine, the Sleep option is unavailable in the Shut Down option list because the XPDM SVGA driver is not installed by VMware Tools on these guest operating system releases. The default Vesa driver is included, which does not support the Sleep feature.

  • Windows Guest operating systems might fail to resume from standby or hibernation state
    Virtual machines running Windows Server 2008 and Windows Server 2003 based guest operating system in the standby or hibernation state might stop responding when resumed from standby or hibernation states.
    See KB 946331 on the Microsoft support Web site.

  • After installing VMware Tools on SUSE Linux Enterprise Server 10 with SP3, VMware Tools might fail to start the vmxnet fast network service.
    Workaround: Perform the following tasks:

    1. During the VMware Tools installation process, answer NO for the following question:
      Before running VMware Tools for the first time, you need to configure it by invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want this program to invoke the command for you now?

    2. After installing VMware Tools, run the following command:
      vmware-config-tools.pl --compile

  • x64-based versions of Windows Vista and Windows Server 2008 guest operating systems require Microsoft hotfix
    x64-based versions of Windows Vista and Windows Server 2008 guest operating systems without Microsoft hotfix http://support.microsoft.com/kb/950772 might encounter a situation where the guest operating system stops responding and returns the following error:
    MONITOR PANIC: vcpu-3:ASSERT vmcore/vmm/cpu/segment.c:430
  • The cursor disappears after VMware Tools has been configured

    This issue has been observed on ESX Server 3.5 with SUSE Linux Enterprise Server 8 (with or without SP4) guests. Immediately after you configure VMware Tools, the mouse cursor is not visible.

    Workaround: Reboot the virtual machine.


All fields in the VI Client and Web Access 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 VMware 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. Otherwise, the installation of VirtualCenter Server fails.
  • Use the default installation path names specified in the installer for all components. Do not change the install path to include 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, host names, workgroup names, domain names, URLs, email addresses, SMTP server names, and SNMP community strings cannot contain non-ASCII characters.
  • Guest operating system customizations that use 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 does 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 be displayed properly after restarting the 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.
  • 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.
  • The wrong text appears on the reinstall wizard of the German VI Client
    The reinstall wizard displays the 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 the wizard should present the following message: 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 VMware Web Access 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 by using the VI Client.
  • Virtual machine names that contain non-ASCII characters might not be displayed correctly when accessing the ESX Server using Web Access.


  • Storage VMotion of a large number of virtual disks fails
    Migrating a large number of virtual disks at the same time with Storage VMotion might fail with the following error message:
    Received an error from the server: A general system error occurred: failed to reparent/commit disk(s) (vim.fault.Timedout)

    To migrate a virtual machine with a large number of virtual disks, migrate the disks in batches as follows:
    1. Migrate the virtual machine configuration file and a subset of the virtual disks (no more than five at a time) from the source location to the destination.
    2. Migrate the virtual machine configuration file back to the source location.
    3. Repeat steps 1 and 2 until all the virtual machine disks and the virtual machine configuration file have been migrated to the destination
  • Migration with VMotion during high memory usage might fail with "Operation Timeout"
    Performing a migration with VMotion on a virtual machine with memory overcommitment and with the swapfile located on an alternative datastore (other than the one on which virtual machine home resides) might not succeed all the time and might fail with VirtualCenter showing error message Operation Timeout.


  • Some Dell BIOSes may have duplicate interrupt routing entries in the ACPI table (KB 1013804)

  • Health Status incomplete after HP Insight Manager installation (KB 1015607)

  • The IBM Director Server Web interface with IBM Director 6.1.2 platform agent installed displays the MAC address of the vmnic as the name of the LAN Connection. To retrieve the LAN Connection name use the ElementName property.

  • IBM Systems Director 6.1 cannot be installed on ESX Server hosts
    Installation of IBM Systems Director 6.1 Server on ESX Server hosts fails with a message similar to the following:
    Could not find a supported operating system for IBM Systems Director.

    IBM Systems Director 6.1 Server is currently not supported on ESX Server 3.5. IBM Director Server can be installed on any Windows machine, and the IBM Director common agent can be installed on the ESX Server 3.5 host.
  • Converter Enterprise Client plug-in must be installed and enabled after upgrading
    VirtualCenter Server 2.5 Update 2 does not support the earlier versions of the Converter Enterprise Client plug-in. You must, therefore, install and enable the Converter Enterprise Client plug-in after upgrading to VirtualCenter Server 2.5 Update 2. To install and enable the Converter Enterprise Client plug-in, click Manage Plugins on the Plugins menu. In the Plugin Manager window, select the Available tab and click Download and Install.
  • Health Status for a Few IPMI Sensors Shows "Unknown" When Multinode IBM System x3950 M2 Server Functions Under Heavy CPU Usage
    If a multinode IBM System x3950 M2 Server under heavy CPU usage hosts more than 80 virtual machines, the Health Status for a few IPMI sensors like Processors, Memory, Storage, Power, System, Chassis, and Watchdog shows "Unknown" for a few minutes.
    To view the Health Status page, click the Health Status link under the Configuration tab in the VI Client.
    To update the sensor status, click Refresh, available on the Health Status page. This update takes approximately 10 minutes.
  • VI Client Shows the Health Status of IBM x Series Servers With LSI 1078, as "Alert" When the Status of the Sensors Is Not Displayed as "Alert"
    VI Client displays the health status of IBM System x3850 M2/x3950 M2 Servers with LSI 1078 IR SAS controller, in red ("Alert") when the sensors and subcomponents are not shown in red.
    To view the Health Status page, click the Health Status link under the Configuration tab in the VI Client.
    Install the latest firmware (version or later) for the LSI 1078 IR SAS controller that is available from IBM Corporation.
  • An ESX Server Web Interface Might Fail to Display the Latest IPMI System Event Log Record
    When the IPMI System Event Log (SEL) is cleared, the IPMI SEL entries available through the ESX Server web interface at https://<IP address of ESX Server host>/host/ipmi_sel, might not be the latest IPMI SEL record.


  • Network connectivity lost on some Intel NICs after rebooting ESX Server (KB 1015620)

  • If ESX Server is installed using a kickstart file, the firewall rules are reset after reboot
    If you install ESX Server using a kickstart file, which specifies authentication servers such as NIS and Active Directory, the firewall rules for these servers are not saved. The firewall rules are reset to default rules after reboot. See KB 1001154 for the workaround.

  • ESX Server does not support more than one vmknic on the same subnet. (KB 1013077)

  • Link and unlink operation on the vswitch does not correctly update the teaming policy of the vswitch where the portgroup lives
    When portgroup is specified with any NIC teaming policy, rather than inheriting the policy from vswitch, any link or unlink operation on the vswitch (by running the command esxcfg-vswitch -L/-U <vmnicX> <vSwitchY>) does not correctly update the teaming policy of the vswitch where the portgroup lives. The state (active or standby) of the uplinks might not be displayed correctly in the VI Client. The number of the active links are as specified in the original teaming policy setting of the portgroup.

  • NetXen P2 Cards Support No More Than 128 GB of RAM on a Machine (KB 1009386)
  • ESX Server hosts become unresponsive during a network broadcast storm

    When a network broadcast storm occurs, ESX Servers might become unresponsive due to an issue with the tg3 network driver. During this time, service console or virtual machines that use the tg3 NIC might lose network connectivity. Rebooting the machine or unloading/loading the driver restores connectivity, but does not resolve the issue.

    ESX hosts with tg3 port cannot send or receive packets after being subjected to a broadcast storm. The following error messages might be logged in VMkernel:

    1. WARNING: Net: 1082: Rx storm on 1 queue 3501>3500, run 321>320
    2. VMNIX: WARNING: NetCos: 1086: virtual HW appears wedged (bug number 90831), resetting
  • Duplicate Packets Are Created When Beacon Probing is Used With a VLAN of 4095
    During a virtual machine network operation where the VLAN ID is set to 4095 and the associated vSwitch is configured with beacon probing, duplicate packets are generated.
    Workaround: When using a VLAN ID of 4095, set Network Failover Detection to Link Status only instead of Beacon Probing. ( KB 1004373)
  • Extended netperf testing for IPv6 fails
    Running high levels of stress using netperf on Internet Protocol Version 6 (IPv6) enabled virtual machines over 12 hours might result in the shutdown of sockets. The following sockets are known to be affected: TCP_STREAM, UDP_STREAM, TCP_RR, and UDP_RR. Error messages similar to the following might be displayed in the virtual machine console:

    send_tcp_rr: data recv error: Connection timed out
    netperf: cannot shutdown tcp stream socket: Transport endpoint is not connected

    This is a known issue.
  • Wake on LAN (WOL) Is Not Supported for Some NetXen NIC Cards

    Wake on LAN (WOL) is not supported for some NetXen NIC cards. However, executing the # ethtool vmnic* command in the service console displays WOL as supported for all NetXen NIC cards.

    Workaround:Use a different NIC card that supports WOL.
  • Even when a NetXen device has no traffic, it shows its speed as 65536 and its duplex as half
    This issue occurs when a corrupt Tx packet is received: NetXen returns a -1 status error and the hardware, the firmware, or both abort. This is a known issue in the NetXen driver.

    Workaround: Unload and load the NetXen driver.
  • Network connectivity is lost when the NIC speed on a NetXen driver is configured manually

    Configuring the speed manually through esxcfg-nics or any other command on a NetXen 3031 NIC might cause loss of network connectivity. NetXen NICs do not support manual speed setting. The speed must be set through auto-negotiation.

Server Configuration

  • The ypbind (NIS) service does not start after boot
    The ypbind service fails to start after ESX Server is booted even though ypbind is set to on by default. This can happen if either the portmap or ypbind service is not properly configured to start at boot time. See KB 1015289 for troubleshooting tips and solutions.

  • Error Message on IBM x3850 M2 and x3950 M2 Servers During Boot
    A SysAlert error message similar to the following might be displayed on IBM x3850 M2 and x3950 M2 servers during the boot sequence:
    0:00:01:02.384 cpu19:1291)USB Control/bulk timeout; usb device may not respond
    You might observe a message from each slave node.
    This is a known issue. The errors that are generated during boot will not affect the normal functioning of the system, and can be safely ignored.
  • In Troubleshooting mode, the poweroff command shuts down ESX Server but does not remove server power
    This issue applies to all versions of ESX Server, including the current release. When the host is booted into Troubleshooting (Service Console only) mode, the poweroff command is not able to remove power from the host. It performs its normal function of shutting down the host operating system, then displays the message "Power down." However, the Service Console lacks the ACPI support that would allow it to complete the power off operation.

    After the "Power down" message is displayed, you can safely remove power manually through normal methods, such as by using a remote management console, turning off power switches, or pulling the plug.
  • Installing on an HP ProLiant BL 280c G6 server results in a timeout message
    The following message is issued when ESX Server 3.5 Update 4 is installed on HP Proliant BL 280c G6 server:
    USB control / bulk_msg: timeout

    This message comes from the Linux service console and indicates that a USB host controller has detected a timeout on an attached USB device. The host controller could be either a high speed (ehci) or a full/low speed controller. The cause could be a loss of connection with any attached device; for example, an ILO cdrom, a keyboard, or a USB flash drive. After this message is issued the device will not function until after a device power event such as a device detach and reattach or an overall system power off and power on. A reboot may or may not clear such a condition. Alternatively, the ehci host controller can be unloaded using rmmod, although this will only clear conditions detected by the high speed host controller.

    This message can be safely ignored. If a device, for example a USB keyboard, is non-responsive a device power event can be implemented by detaching the device and reattaching it (for ILO storage devices this is done via the remote media tab). No other system impact has been observed in relationship with this message.


  • Core dumps are lost when multiple ESX hosts share a dump partition
    If multiple ESX hosts that share a dump partition fail and save core dumps simultaneously, the core dumps might be lost.
  • LSI jobs and nonconcrete storage pools do not persist between boots
    The persistence scheme implemented by LSI creates a new file on the host operating system for each job and non-concrete storage pool (a storage pool that is not associated with a storage volume). These files will not persist between boots. As a result, non-concrete storage pools will no longer be available after the host operating system is rebooted. In addition, any jobs executed before the reboot will not be visible.
    Support for 10GbE IP storage (iSCSI and NFS) with the update releases is for connectivity. Performance levels can vary.
  • Creating a large file on a spanned VMFS datastore might fail if the first datastore extent is smaller than 1GB
    If you try to create a large virtual disk file in a spanned VMFS datastore, this operation might fail. Generally, this problem occurs when the first datastore extent is small, less than 1GB in size, and is due to a lack of pointer blocks.
    Workaround: If possible, recreate the datastore using the larger partition first and adding the smaller extents later.
  • Serial Attached SCSI (SAS) Disk Arrays Cannot Be Added as Raw Device Mapping Disks Using the VI Client
    When using the VI Client to create virtual machines on raw device mapping disks or add a hard disk to a virtual machine, the Raw Device Mapping option is disabled in the New Virtual Machine Wizard, and in the Add Hardware Wizard.
    Workaround: To add SAS disk arrays as raw device mapping disks:
    1. Run a command with the following syntax in the ESX Server service console:
    # vmkfstools -r <raw_device_path> -a <bus_type> <RDM_file_name>
    2. Use the Add Hardware Wizard to add the newly created virtual disk as an existing disk, to the virtual machine.
  • Capacity of a LUN added to a datastore might not be visible when VI Client is connected to an ESX Server host
    The Storage panel in the Configuration tab of the VI Client allows you to modify the properties of a datastore. When the VI Client is connected to an ESX Server host, if you add LUNs to a datastore by clicking Add Extent in the Properties window of the datastore, the capacity for the added LUN might not be displayed in the Properties window.
    Workaround: Close the Properties window, click the Storage link in the Configuration tab, and re-open the Properties window.
  • ESX host displays benign error message while accessing an optical device
    During mounting or copying from an optical device, the ESX Server host displays a hda: lost interrupt message on the screen. This error message might also be written to /var/log/messages. This issue does not cause any data corruption, and can be ignored.

Upgrade and Installation

  • System becomes unusable if esxupdate runs out of disk space
    When esxupdate is used to upgrade to ESX Server 3.5 Update 3, the system will become unusable if esxupdate runs out of space on either the /, /boot, or /usr partitions.
    Workaround: Before applying a patch make sure you have enough space in your /, /boot, or /usr partitions. To determine if there is enough space for the Upgrade, you can perform a test installation as described in the ESX Server 3 Patch Management Guide.

ESX Server Upgrade and Installation

  • The esxupdate -l query Command Lists VMware-vpxa As a Newly Installed RPM Package
    When an ESX Server host that is connected to the VirtualCenter Server is upgraded to an ESX Server 3.5 release version using the esxupdate utility, the esxupdate - l query command lists VMware-vpxa as a newly installed RPM package, because the VirtualCenter Client installs the VMware-vpxa rpm package when it connects to the ESX Server host for the first time.

Other Upgrade and Installation Issues

  • Power Off Button Sometimes Does Not Work in Web Access
    In some cases, the power off button for a virtual machine is not available or does not respond when clicked.
    Workaround: Refresh the browser window and the power off button should work properly.
  • Upgrading VirtualCenter and VMware Update Manager May Fail to Upgrade the Update Manager Database
    You can use the Unified Installer to simultaneously upgrade VirtualCenter and VMware Update Manager, but problems with custom database configurations might occur. VirtualCenter and VMware Update Manager can store information in a single database or in separate databases. If your deployment includes separate databases, and you do not use the Custom option during upgrade, the VMware Update Manager database might not be upgraded. Instead, one of two things can happen:
    • If there is no Update Manager database in the VirtualCenter database instance, a new Update Manager database is created.
    • If there is an existing but unused Update Manager database, this is upgraded. Unused Update Manager databases can occur when an initial installation is completed and then subsequently, a separate Update Manager database is established.
    In both cases, the custom Update Manager database that was being used is not updated. After the upgrade, the system uses the incorrect database that the unified installer has either updated or created.

    To avoid this issue, select the Custom type for the installation and specify the Update Manager database your deployment is using.

Virtual Machine Management

  • VMware Tools icon is missing from the Control Panel for 64-bit Windows Vista and Windows 2008 guest operating systems
    Only the 32-bit control panel is available for VMware tools on Windows Vista and Windows 2008 guest operating systems and so VMware Tools does not appear in the control panel of the 64-bit operating systems.

    Workaround: Use the 32-bit control panel applet that is available from the VMware Tray or from C:\Program Files (x86)\VMware\VMware Tools\VMControlPanel.cpl or <VMware tools install path>\VMControlPanel.cpl.
  • 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
  • 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.
    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.

VirtualCenter, VI Client, and Web Access Issues

  • Powering on or powering off a virtual machine using Web Access results in multiple redundant error messages being written to hostd.log with error messages
    When you power on or power off a virtual machine by using Web Access, error messages similar to the following are logged in the hostd.log file in /var/log/vmware/ every 2 or 3 seconds:
    Throw vmodl.fault.ManagedObjectNotFound

  • VirtualCenter Server Fails to Initialize Immediately If the Latest Version of VMware Capacity Planner Service is Not Used
    If the VMware Capacity Planner Service for the VirtualCenter Server 2.5 Update 2 release is not installed, the VirtualCenter Server takes a long time to initialize, and during this time the VI Client cannot connect to the VirtualCenter Server. In addition, the consolidation feature is not available in the VI Client.
    To use the consolidation feature, uninstall any earlier version of the VMware Capacity Planner Service, install the VMware Capacity Planner Service for the VirtualCenter 2.5 Update 2 release, and restart the VirtualCenter Server.
  • A time zone label is different depending on the way ESX Server 3.5 Update 4 was installed
    When creating a kickstart file, ks.cfg, using Web Access, a time zone name available in the drop-down menu is Asia-Calcutta. However, the same item is listed as Asia-Kolkata when the installation is performed by using either the GUI or text. This presents no issue other than providing inconsistent naming

VMware High Availability (HA)

  • Virtual Machine Migrations Are Not Recommended When the ESX Server Host Is Entering the Maintenance or Standby Mode
    VMware DRS will not recommend or perform (when in fully automated mode) virtual machine migrations 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 Health Monitoring is enabled for an HA cluster. The console does not display the virtual machines rebooting.

    You must open a new console to see the virtual machines restarting after the failover.
  • 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 VirtualCenter 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.

Top of Page

Using Language Packs 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, the language pack must be on the host and the default locale set to your desired language. Starting with ESX Server 3.5 Update 3, the language pack files are installed on all hosts and do not need to be copied to the host before changing the locale.

To set the default locale on the host.

  1. Edit the /etc/vmware/hostd/config.xml file to enable the correct default locale. Find the following lines in config.xml:

    For German, replace the lines with the following:


    For Japanese, replace the lines with the following:


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


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

    service mgmt-vmware restart
    service vmware-VMware Web Access restart