VMware

VMware vCenter Server 4.0 Update 2 Release Notes

VMware Infrastructure Management Installer | 10 JUN 2010 (For all locales)
vCenter Server 4.0 Update 2| 10 JUN 2010 | Build 258672
vSphere Client 4.0 Update 2| 10 JUN 2010 | Build 258672

Last Document Update: 10 SEP 2010

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of VMware vCenter Server 4.0 Update 2 offers the following improvements:

  • Guest Operating System Customization Improvements: vCenter Server now supports customization of the following guest operating systems:
    • Windows XP Professional SP2 (x64) serviced by Windows Server 2003 SP2
    • SLES 11 (x32 and x64)
    • SLES 10 SP3 (x32 and x64)
    • RHEL 5.5 Server Platform (x32 and x64)
    • RHEL 5.4 Server Platform (x32 and x64)
    • RHEL 4.8 Server Platform (x32 and 64)
    • Debian 5.0 (x32 and x64)
    • Debian 5.0 R1 (x32 and x64)
    • Debian 5.0 R2 (x32 and x64)
  • Resolved Issues:In addition, this release delivers a number of bug fixes that have been documented in the Resolved Issues section.

Prior Releases of VMware vSphere 4

Features and known issues from prior releases of vSphere 4.0, are described in the release notes for each release. To view release notes for prior releases of vSphere 4 components, click the following links:

Before You Begin

ESX, vCenter Server, and vSphere Client Version Compatibility


The vSphere Compatibility Matrixes provide details on the compatibility of current and previous versions of VMware vSphere components, including ESX, vCenter Server, the vSphere Client, and optional VMware products. In addition, check the vSphere 4.0 Update 1 Compatibility Matrixes for information on supported management and backup agents before installing ESX or vCenter Server.

Installation and Upgrade


Read the ESX and vCenter Server Installation Guide for step-by-step guidance on installing and configuring ESX and vCenter Server.

After successful installation, several configuration steps are essential. In particular, some licensing, networking, and security configuration is necessary. Refer to the following guides in the vSphere documentation for guidance on these configuration tasks.

Future releases of VMware vSphere might not support VMFS version 2 (VMFS2). VMware recommends upgrading or migrating to VMFS version 3 or higher. See the vSphere Upgrade Guide.

Future releases of VMware vCenter Server might not support installation on 32-bit Windows operating systems. VMware recommends installing vCenter Server on a 64-bit Windows operating system. If you have VirtualCenter 2.x installed, see the vSphere Upgrade Guide for instructions on installing vCenter Server on a 64-bit operating system and preserving your VirtualCenter database.

Upgrading or Migrating to vCenter Server 4.0 Update 2

You can upgrade from VirtualCenter 2.0.2, (including Update 1, Update 2, Update 3, Update 4, and Update 5) VirtualCenter 2.5, (including Update 1, Update 2, Update 3, Update 4, Update 5, and Update 6) vCenter Server 4.0, and vCenter Server 4.0 Update1 to vCenter Server 4.0 Update 2.

Note: Upgrading VirtualCenter Server 2.0.x to vCenter Server 4.0 or later is not supported on operating systems running the Japanese locale.

Plug-Ins Updates

This release of the vCenter Server 4.0 Update 2 software suite includes updates to VMware Update Manager, VMware Guided Consolidation, and VMware Orchestrator.

Documentation

The VMware vSphere 4.0 Update 1 documentation has been updated and is applicable for all update releases of vSphere 4.0, including VMware vSphere 4.0 Update 1 and Update 2. See the following documentation pages:

Internationalization

VMware vSphere 4.0 Update 2 is available in the following languages:

  • English
  • German
  • Japanese
  • Simplified Chinese

vSphere Client Locale Forcing Mode


With vSphere 4.0 Update 2, you can configure the vSphere Client to provide the interface text in English even when the operating system on which it is running is non-English. This configuration can be done for the duration of a single session by supplying a command-line switch. This configuration applies to the interface text and will not affect other locale-related settings such as date/time or numeric formatting.

The following vSphere Client command will cause the individual session to appear in English:
vpxClient -locale en_US

vCenter Server Upgrades

You can upgrade VirtualCenter Server 2.x, vCenter Server 4.0, and vCenter Server 4.0 Update 1 to vCenter Server 4.0 Update 2. To upgrade, first confirm that your database is supported with vCenter Server 4.0 Update 2, back up your supported database, SSL certificates, and VirtualCenter Server configuration. Then run the vCenter Server installer. The installer informs you that an earlier version of vCenter Server is on the computer and will be upgraded.

Notes:

  1. Upgrading VirtualCenter Server 2.0.x to vCenter Server 4.0 or later is not supported on operating systems running the Japanese locale.
  2. It is recommended that you run the Pre-Upgrade Checker tool (provided with your VMware vCenter Server 4.0 Update 2 installer package) prior to upgrading your vCenter Server.

Open Source Components for vSphere

Open source components and their respective licenses for the most recent generally available release of vSphere is available at http://www.vmware.com/download/vsphere/open_source.html, under the Open Source tab. You can also download the source files for any GPL and/or LGPL, or other similar licenses that require the source code or modifications to source code to be made available, for the most recent generally available release of vSphere, by clicking on the link noted above.

Resolved Issues

This release resolves issues in the following subject areas. Resolved issues documented as known issues in the earlier release are marked with the † symbol.

CIM and API

  • VirtualCenter stops responding while retrieving historical events
    While retrieving historical events from VirtualCenter, the VirtualCenter Server Service might stop responding. An error message similar to the following might be written to the logs:

    Panic: Assert Failed: "pos != string::npos" @ d:/build/ob/bora-161137/bora/vim/lib/vmomi/soapVisitor.cpp:731

    You can restart VirtualCenter, but it might fail again if you attempt to retrieve historical data.

    This issue is resolved in this release.

  • VIM API call QueryPerf () does not return any data for certain performance counters when queried against vCenter Server
    VIM API call QueryPerf() might not return any data when querying vCenter Server for certain performance counters. Querying the ESX host directly for the same performance metric works correctly. The issue might occur with metric counters that have a value that exceeds the integer limit. A single problematic counter might cause the whole query to return an empty result.
    The following are examples of metric counters that can have a value that exceeds the integer limit:
    • CounterId: 258 Instance: host/vim
    • CounterId: 258 Instance: host/system/vmotion
    • CounterId: 258 Instance: host/system
    The issue might occur with other metrics if their value exceeds the integer limit.

    This issue is resolved in this release. The QueryPerf() API now returns valid metric values for all performance counters.

Guest Operating Systems

  • Multiple DNS suffixes are not applied correctly after image customization of Linux distributions
    DNS suffixes are automatically appended when a Linux distribution tries to resolve a DNS domain name. When more than one DNS suffix is customized, only the last DNS suffix is applied. Depending on the Linux distribution, not all customized DNS suffixes appear in the Linux distribution user interface.

    This issue is resolved in this release.

Licensing

  • vCenter Server 4.0 cannot manage an ESX 3.x host if the VirtualCenter 2.5.x license server FQDN has a non-standard suffix
    If the fully qualified domain name (FQDN) of the VirtualCenter 2.5.x license server ends with .local or .eng instead of a standard suffix such as .com or .net, access to items such as Advanced Settings in the vCenter Server Settings window might fail with an Enter a valid license server error message.

    This issue is resolved in this release. vCenter Server 4.0 can be configured with a license server even if the FQDN has a non-standard suffix.

Miscellaneous

  • A user with custom roles cannot set an email action for an alarm
    A user with custom role might observe the following error while specifying an email action for an alarm:

    Permission to perform this operation was denied. You do not hold privilege "System > Read" on OptionManager "VpxSettings"

    You might succeed in creating an alarm without setting its action.

    This issue is resolved in this release.

  • Help menu items appear inactive or clicking other links for Help results in an error
    In vSphere Client installations on machines running non-English, non-Japanese, non-German, and non-Simplified Chinese Windows operating systems, Help menu items appear inactive. In addition, if you click other links or buttons for Help within the vSphere Client the following error message appears:

    Missing help file

    Starting with this release, vSphere Client displays English language Help files for locales that are not supported.

Networking

  • Virtual machines connected to a vNetwork Distributed Switch (vDS) are disconnected after a failover
    vDS virtual machine port changes persist the port configuration every five minutes. Since virtual machine port changes are not persisted immediately, virtual machines might lose network connectivity after a failover event if they have been configured to link to a vDS less than five minutes before the failover.

    This issue is resolved in this release.

Security

Server Configuration

  • vCenter Server might stop responding if an ESX host is added to a cluster that is attached to a host profile
    When a cluster is attached to a host profile and an ESX host is added directly to the cluster (by right-clicking the cluster and selecting Add Host), the host profile is not associated to the added host. This might cause the vCenter Server to stop responding when a scheduled task for checking compliance against that profile is run.

    This issue is resolved in this release.

  • Host profiles that configure service console port and VMkernel port to exist on the same port group in a DVS setup cannot be applied
    When you apply a host profile that configures the service console port and VMkernel port to exist on the same port group in a DVS setup, the applying host profile operation might fail with an error similar to the following:

    IP address <IP_Address_Number> is used for multiple virtual NICs

    This issue is resolved in this release.

  • Host profiles do not capture or duplicate physical NIC duplex information
    When you create a new host profile, the physical NIC duplex information is not captured. Therefore, when the reference host's profile is used to configure other hosts, the operation negotiates the duplex configuration for each physical NIC individually.

    This issue is resolved in this release. Starting with this release, host profiles capture physical NIC duplex information.

  • ESX hosts might stop responding if their IP address is changed by applying host profiles
    If ESX hosts are added to vCenter Server by using IP addresses, and the IP addresses of these ESX hosts are changed by applying host profiles, the hosts might stop responding. The applying host profile operation might time out and the ESX Server hosts remain in the non responsive mode until the ESX hosts are disconnected and reconnected to the vCenter Server.

    This issue is resolved in this release.

Storage

  • Datastore name is not displayed in SNMP trap for datastore alarm
    A vCenter Server SNMP trap that is sent for a datastore alarm might not display the datastore name. The datastore name might appear in an email alert.

    This issue is resolved in this release.
  • Unable to set preferred path for a fixed Policy within path management when vSphere Client is connected to the vCenter Server
    When you try to change the preferred path of a storage device set to a fixed policy with multiple paths, the vSphere Client might display the following error message:

    Unable to cast object of type 'LogicalUnitPolicy' to type 'FixedLogicalUnitPolicy'

    This issue is resolved in this release.

  • On thin-provisioned storage devices, using eagerzeroedthick allocation policy results in wasted storage space
    When a new virtual machine is deployed from a template on a VMFS-3 datastore, the eagerzeroedthick allocation policy is used. This results in a virtual disk that is fully allocated, and space is wasted on thin-provisioned storage devices. The same problem occurs when a virtual machine is migrated from one datastore to another by using Storage vMotion.

    This issue is resolved in this release. Starting with this release, the zeroedthick or eagerzeroedthick allocation type of the source disks is preserved if provisioning operations are performed on the same host with the nfc.eagerzeroedthick option set in the host's vpxa.cfg file. While performing these operations on another host, you can configure the eagerzeroedthick or zeroedthick allocation type by setting the nfc.eagerzeroedthick option in the host's vpxa.cfg file.

    Note: The fix does not work even if you set nfc.eagerzeroedthick option in the host's vpxa.cfg file if the provisioning operation is performed on the same host.

  • Storage Management Service fails to initialize
    For any RDM or VMFS-formatted LUNs shared by multiple ESX hosts, the LUN size might differ across hosts. If the shared LUN size is greater than 4GB, Storage Management Service might fail to initialize with an Unknown exception encountered during service initialization error.

    This issue is resolved in this release.

Upgrade and Installation

  • vCenter agent is not installed or upgraded on ESXi 4.0 hosts
    If you try to add an ESXi 4.0 host to vCenter Server 4.0 or 4.0 Update 1, remove and then re-add an ESXi 4.0 host back to vCenter Server 4.0 or 4.0 Update 1, or upgrade vCenter Server from 4.0 to 4.0 Update 1, vCenter agent might fail to install. This issue might occur when there is a memory fragmentation on the ESXi host. An error message similar to the following might be displayed on the vCenter Client:

    Cannot install the vCenter agent service. Unknown Installer error

    This issue is resolved in this release.

  • vCenter Server plug-ins fail to start after upgrading vCenter Server to vCenter Server 4.0 Update 1
    vCenter Server plug-ins might fail to start after upgrading vCenter Server to vCenter Server 4.0 Update 1. For example, for a vCenter Server plug-in such as Site Recovery Manager (SRM), the file proxy.xml located at C:\Documents and Settings\All Users\VMware\VMware VirtualCenter maps SRM components to vCenter Server components. This file is updated with SRM information during the SRM installation. The upgrade to vCenter Server 4.0 Update 1 resets proxy.xml to a state where no mapping information is available. As a result, the VMware vCenter Site Recovery Manager service might fail to start.

    This issue is resolved in this release.

vCenter Server, vSphere Client, and vSphere Web Access

  • Keyboard and regional settings are changed to US from United Kingdom after virtual machine customization
    When deploying a Windows 2000 virtual machine or template using customization, the keyboard and regional settings are changed to US from United Kingdom.

    This issue is resolved in this release.

  • Selecting the Power Management option of a virtual machine that has five or more network adapters results in an error
    On the vSphere Client, selecting the Power Management option of a virtual machine that has five or more network adapters might result in the following error message:

    Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index

    This issue is resolved in this release.

  • Changing the time of a scheduled task causes the next run to be set to an incorrect date
    On the vSphere Client, when you reschedule a weekly task, the Scheduled Tasks list might display an incorrect day for Next run. This might happen due to an issue with converting UTC to local time.

    This issue is resolved in this release.

  • You cannot mount an ISO or local CD-ROM device on a virtual machine when default ports in vCenter Server 4.0 are changed
    If you change the default HTTP or HTTPS ports (80 and 443) of vCenter Server 4.0, an attempt to mount an ISO or CD-ROM device on a virtual machine might fail with an error message similar to the following:

    A connection to the host could not be established

    This issue is resolved in this release. Starting with this release, you can mount ISO or CD-ROM devices even if you change the vCenter Server default ports.

  • Host CPU and Host Memory statistics might not be displayed for all virtual machines
    If the vCenter Server inventory has more than one virtual machine, in the vSphere Client Datastores view, Host CPU and Host Memory statistics are displayed only for the first virtual machine in the list.

    This issue is resolved in this release.

  • vCenter Server Hardware status does not display detailed Dual In-line Memory Module (DIMM) information on HP Proliant servers
    On all HP Proliant servers, vCenter Server hardware status displays memory sensor information but not its details such as Memory type and MaxMemorySpeed. These details are displayed if you install HP CIM provider VIB on the ESX host. The VIB is available for download on the HP Web site.

  • Ejecting a CD from a virtual machine causes vCenter Server to stop responding
    If you use the Lab Manager UI to eject a CD from a virtual machine while a provisioning operation is in progress on the vCenter Server, the VMware VirtualCenter Server Service might stop responding. A Panic: Win32 invalid parameter error message might be written to the vpxd log.

    This issue is resolved in this release.

  • ESX hosts are disconnected from vCenter Server if enumeration of attached datastores takes a long time
    When you perform I/O intensive operations such as taking multiple snapshots of virtual machines, hostd takes a long time to respond, and as a result, the ESX host might become disconnected from the vCenter Server. You might observe that the vdf command (or any command for querying the datastores) takes a long time to run. Errors might not be written to the logs as the operation eventually completes. However, the vpxd log marks the host and virtual machines as disconnected.

    This issue is resolved in this release.

  • VMware vCenter Server UI update performance degradation in environments containing hosts running ESX 4.0 and earlier versions of ESX
    While using vCenter Server 4.0 to manage an environment having a large number of ESX 4.0 and ESX 3.x hosts, UI performance might become degraded for ESX 3.x hosts. For example, when you select a virtual machine in the vSphere Client, there might be an excessive delay before its information is displayed on the Summary tab.

    This issue is resolved in this release.

  • cleanup_events_tasks_proc stored procedure fails to run properly on vCenter Server 4.0
    The Tasks and Events cleanup job cleanup_events_tasks_proc stored procedure fails to run properly on vCenter Server 4.0 under certain circumstances due to a database constraint conflict.

    This issue is resolved for new installations of vCenter Server 4.0 Update 2. If you are upgrading to vCenter Server 4.0 Update 2, follow the instructions in KB 1014893.

  • Incorrect unit value displayed for disk usage in alarm notification email
    Disk usage units, which should be displayed as KBps, are instead displayed as a % value in the notification email.
      
    This issue is resolved in this release.

  • Events exported from vCenter Server database are not in sequence
    When you export vCenter Server database events, the VPX_EVENT record of the SQL table might not be displayed in the correct sequence.

    This issue is resolved in this release.

  • Stateless event alarms repeatedly trigger actions that are set to run only once
    Stateless event alarms, such as the default vCenter alarms Cannot connect to network and Cannot connect to storage, send emails repeatedly, once every five minutes, even when configured to send notifications only once. The email notifications might continue to be sent even after the event that triggered the alarm has lapsed. You cannot stop such notifications.

    This issue is resolved in this release. Starting with this release, all actions for Stateless alarms, including actions that are configured to repeat, run only once.

  • vSphere Client fails to display historical performance overview data

    On the vSphere Client, the Performance Overview tab might fail to display the statistics for past day, week, month, and year with an error message similar to the following:

    Chart could not be loaded.

    However, real-time data is displayed. The following error might be written to stats.log

    [Date] [ERROR] com.vmware.vim.stats.webui.chart.StatsChartServlet : Unable to generate performance chart image. Details: null java.lang.NullPointerException

    This issue is resolved in this release.

  • vSphere Client takes longer than expected to display newly installed extensions in the list of installed extensions
    After the installation of extensions is finished, 30-60 seconds pass before newly installed extensions appear in the list of installed extensions.

    This issue is resolved in this release.

Virtual Machine Management

  • Virtual machine starts on the host it was registered on, even if it is scheduled to start on another host
    On an ESX host, when scheduling to power on a virtual machine, you have the option to select another host on which the virtual machine should be deployed. A virtual machine might start on the host it was registered on, even if it is scheduled to start on another host.

    This issue is resolved in this release.
  • A virtual machine fails to respond or power on when its network interface card (NIC) is attached to a port group with a name that exceeds 50 characters

    This issue is resolved in this release. Port group names now cannot be changed to a name that exceeds 50 characters. Previously assigned port group names that exceed 50 characters are not accessible by virtual machines.

vMotion and Storage vMotion

  • Storage vMotion fails even if the destination datastore has sufficient disk space
    Storage vMotion might fail even if the space available on the destination datastore is more than the moving disk space because the calculation considers the shared swap file size of the virtual machine as well. When the failure occurs, an error message similar to the following might be displayed in the Migrate Virtual Machine dialog box in the vSphere Client:

    Insufficient disk space on datastore

    This issue is resolved in this release. Starting with this release, shared swap file space is not considered in calculating the required space in the destination datastore.

  • vMotion times out if the virtual machine swap file is located on the local storage
    If the vswap file of a virtual machine running memory intensive operations is located on the local storage, a vMotion operation that you perform on the virtual machine might time out. The vCenter Server might display an operation timed out error message for the virtual machine migration operation, even if the migration completes.

    This issue might still occur. However, starting with this release, the timeout value is configurable. In earlier releases, the timeout value was hard coded.

    To configure the timeout value, add the following parameters to the vpxa.cfg file on the ESX host:

    <config>
    ..
    <vpxa>
    ..
    <vmotion>
    <vmIdAcquireTimeout><New timeout value in seconds></vmIdAcquireTimeout>
    </vmotion
    ..
    </vpxa>
    ..
    </config>

VMware High Availability and Fault Tolerance

  • VMware High Availability configuration might fail when advanced HA option das.allowNetwork uses vNetwork Distributed Switch (vDS) port group
    On an HA-enabled cluster, if you specify a vDS port group by using the advanced HA configuration option das.allowNetwork, the HA configuration on the hosts might fail with an error message similar to the following:

    Host [hostname] currently has no available networks for HA Communication. The following networks are currently used by HA: [portgroup name]

    This issue is resolved in this release. Starting with this release, das.allowNetwork works with vDS.

  • When a virtual machine running on a NAS datastore is configured to shut down in response to host isolation, the virtual machine might attempt to run simultaneously on two hosts in a network isolation event.
    If a virtual machine is configured with the default setting to shut down on host isolation, the virtual machine might fail to respond indefinitely while trying to shut down in the event of a multiple network failure that causes host isolation and the loss of network access to the datastore. HA tries to power off the virtual machine and restart it on another host. Two instances of the virtual machine might appear in the vSphere Client. There is no data corruption, because HA and VMFS correctly control access to the virtual machine's data, but the original virtual machine becomes non responsive. You can clear the condition by connecting directly the host that was isolated and dismissing the question.

    This issue is resolved in this release.
  • Upgrading from an ESX/ESXi 3.x host to an ESX/ESXi 4.0 host results in a successful upgrade, but VMware HA reconfiguration might fail
    When you use vCenter Update Manager 4.0 to upgrade an ESX/ESXi 3.x host to ESX/ESXi 4.0, if the host is part of an HA or DRS cluster, the upgrade succeeds and the host is reconnected to vCenter Server, but HA reconfiguration might fail. The following error message might be displayed on the host Summary tab:

    HA agent has an error : cmd addnode failed for primary node: Internal AAM Error - agent could not start. : Unknown HA error.


    This issue is resolved in this release.

Known Issues

The Known Issues section covers Functionality Caveats and provides a List of Known Issues.

Functionality Caveats

vSphere Web Access

vSphere Web Access is no longer being developed. Support for this product is provided on a best effort basis. You should use the vSphere Client, which contains all the functionality of Web Access.

Character Input Limitations

All fields in the vSphere Client and the vSphere Web Access interface support non-ASCII character input, except for the limitations listed below.

Non-ASCII Character Entry Limitations:

  • The name of the computer on which vSphere 4.0 Update 2 components are installed must not contain non-ASCII characters.
  • The name of the computer or virtual machine where vCenter Server is installed must not have a non-ASCII computer name or the installation of vCenter 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.
  • Logging in to the vCenter Server is supported only for user names with ASCII characters (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.
  • In accordance with general Internet 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, user name, or password, vCenter Server, and the sysprep tool must be hosted in the same locale as that of the guest operating system. This limitation includes UTF-8 encoded answer files.

Non-ASCII Character Display Limitations:

  • When managing a vCenter Server with the vSphere Client running on different languages of Windows, some characters might be 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 is not displayed correctly in the localized environment.

USB Pass-Through for Virtual Machines

Although you can add USB controllers to virtual machines, attaching USB devices is not supported.

List of Known Issues

The following issues are known to occur. The list of issues below pertains to vCenter Server 4.0, vCenter Server 4.0 Update 1, and to this release. Known issues not previously documented are marked with the * symbol.

The known issues are grouped as follows:

Installation

  • vCenter Server installation or upgrade fails if the database user name or password contains a semicolon *
    Installation or upgrade of vCenter Server might fail with an error message similar to the following, if the database user name or password that you provide contains a semicolon:

    Setup cannot create vCenter Server Directory Services instance. Refer to c:\users\Admini~1\...\jointool-0.log for more details. Click Yes to force this operation.

    When you click Yes, a message similar to the following might be displayed:

    Error 28038. Setup cannot create vCenter Server Directory Services instance. Refer to c:\users\Admini~1\AppData\Local\Temp\2\...\jointool-0.log for more details.

    Workaround: Do not use a semicolon in user names, passwords, and file paths.

  • vCenter Server Service fails to start if vCenter Server is installed with custom ports and remote DB2 database
    After you install vCenter Server using custom ports and remote DB2 database, vCenter Service might fail to start.

    Workaround : Stop VirtualCenter Management WebServices and then restart VirtualCenter Server Service.

  • Install process of vCenter Server 4.0 and 4.0 Update 1 might not be completed on Windows Server 2008 (KB 1013822)
  • vCenter Server 4.0 Update 1 and later fails to prompt for upgrade to vSphere 4.0 Update 1 Client in a multi-vCenter Server environment
    In a multi-vCenter Server environment where vCenter Server 4.0 and vCenter Server 4.0 Update 1 coexist, if you use vSphere Client to access a vCenter Server 4.0 Update 1 instance, you might not be prompted for upgrade to vSphere 4.0 Update 1 Client.

    Workaround: Make sure you use vSphere Client 4.0 Update 1 in a multi-vCenter environment. The vSphere Client installer is available in the vCenter Server 4.0 Update 1 installation folder. You can download it from http://hostname_of_vCenter_Server/client/VMware-viclient.exe.

  • Extraneous SQL Express database error message while uninstalling vCenter Server
    While uninstalling vCenter Server on a system which has SQL Server installed, you might see an error message similar to the following:

    Error 25061.Setup failed to remove the DSN used to access the local vCenter Server SQL Express database.

    This error message can be ignored. Click OK in the dialog box to continue the uninstall process.

  • Agent Pre-upgrade check utility fails to run
    If you try to run the Agent Pre-upgrade check utility from autorun.exe, you might get an error message similar to the following:

    The application failed to initialize properly(0x0000135). Click on OK to terminate the application.

    Workaround: Install .NET 2.0 or higher.

  • Cannot log in to VirtualCenter Server 2.5.x installed with custom ports when vSphere client and VI Client 2.5 coexist on the same system
    On a VirtualCenter Server 2.5.x system that has custom HTTPS port enabled, if you install VI Client 2.5.x, and later install vSphere Client , you might not be able to log back in to the VirtualCenter 2.5.x Server. The login might fail with an error message similar to the following:

    The request failed because of connection failure

    Workaround: Uninstall vSphere Client from the system.

  • vCenter Orchestrator fails to install when Terminal Server is running (KB 1015658)
  • Installation or upgrade of vCenter Server might fail with disk space error
    During installation of vCenter Server, when you provide the amount of free space estimated by the installer, the installation might fail and display a Not enough disk space error message. As a result, you might have to rerun the installation.

    Workaround: Provide at least 1GB of free space in addition to the amount recommended by the installer.

  • The vCenter Server installer cannot detect service ports if the services are not running
    When you install vCenter Server and accept the default ports, if those ports are being used by services that are not running, the installer cannot validate the ports. The installation fails, and an error message might appear, depending on which port is in use.

    This problem does not affect IIS services. IIS services are correctly validated, regardless of whether the services are running.

    Workaround: Verify which ports are being used for services that are not running before beginning the installation, and avoid using those ports.

  • vCenter Server service might not start if vCenter Server is installed as a local system account on a local Microsoft SQL Server database with Integrated Windows NT Authentication
    If you install an instance of vCenter Server as a local system account on a local SQL Server database with Integrated Windows NT Authentication and then add an Integrated Windows NT Authentication user to the local database server with the same default database as vCenter Server, vCenter Server might not start.

    Workaround: Remove the Integrated Windows NT Authentication user from the local SQL database server. Alternatively, change the default database for the local system user account to the vCenter Server database for the SQL Server user account setup.

  • vCenter Server installer reports incorrect warning message during an installation or upgrade
    During installation or upgrade, the vCenter Server installer reports a warning message to enable TCP/IP and named pipes for remote connections. This message is reported if you use a local SQL Server database and enter a server name other than (local) and "." when you create DSN.

    Workaround: Ignore the warning and click OK to continue the installation or upgrade.

  • vCenter Server installation on Windows Server 2008 with a remote SQL Server database fails in some circumstances
    If you install vCenter Server on Windows Server 2008, by using a remote SQL Server database with Windows authentication for SQL Server, and a domain user for the DSN that is different from the vCenter Server system login, the installation does not proceed, and the installer displays the following error message:

    25003.Setup failed to create the vCenter repository

    Workaround: In these circumstances, use the same login credentials for vCenter Server and for the SQL Server DSN.

  • vCenter Server installation fails on Windows Server 2008 when using a non-system user account
    When you specify a non-system user during installation, vCenter Server installation fails with the following error message:

    Failure to create vCenter repository

    Workaround: On the system where vCenter Server is being installed, turn off the User Account Control option under Control Panel > User Accounts before you install vCenter Server. Specify the non-system user during vCenter Server installation.

  • Uninstalling the vSphere Client leaves behind empty directories
    When you uninstall the vSphere Client, empty directories remain.

    Workaround: Navigate to the installation directory and delete the Virtual Infrastructure Client directory.

  • vSphere Client 4.0 download times out with an error message when you connect VI Client 2.0.x on a Windows 2003 machine to vCenter Server or an ESX/ESXi host
    If you connect a VI Client 2.0.x instance to vCenter Server 4.0 or an ESX/ESXi 4.0 host, vSphere Client 4.0 is automatically downloaded onto the Windows machine where the VI Client resides. This operation relies on Internet Explorer to perform this download. By default, Internet Explorer on Windows 2003 systems blocks the download if the VI Client instance is VI Client 2.0.x.

    Workaround: In Internet Explorer, select Tools > Internet Options > Advanced and uncheck the option Do not save encrypted pages to disk. Alternatively, download and install vSphere Client 4.0 manually from vCenter Server 4.0 or the ESX/ESXi 4.0 host.

  • Cannot reinstall or uninstall product after terminating the uninstallation of vSphere Client 4.0
    If vSphere Client installation is interrupted, a subsequent installation or uninstallation of the vSphere Client 4.0 results in the following error message:

    Error applying transforms. Verify that the specified transform paths are valid.

    Workaround: Use the Windows Installer Cleanup to uninstall vSphere Client 4.0.

  • Cannot log in to VirtualCenter Server 2.5 after installing VI Client 2.0.x, 2.5, and vSphere Client 4.0, and then uninstalling VI Client 2.0.x on a Windows Vista system
    After you uninstall the VI Client 2.0.x on a Windows Vista machine where VI Client 2.0.x, 2.5, and vSphere Client 4.0 coexist, you cannot log in to vCenter Server 2.5. Login fails with the following message:

    Class not registered(Exception from HRESULT:0x80040154(REGDB_E_CLASSNOTREG))

    Workaround: Disable the User Account Control setting on the system where VI Client 2.0.x, 2.5, and vSphere Client 4.0 coexist, or uninstall and reinstall VI Client 2.5.

  • If SQL Native Client is already installed, you cannot install vCenter with the bundled SQL Server 2005 Express database
    When you are installing vCenter with the bundled SQL Server 2005 Express database, if SQL Native Client is already installed, the installation fails with the following error message:

    An Installation package for the product Microsoft SQL Native Client cannot be found. Try the installation using a valid copy of the installation package sqlcli.msi.

    Workaround: Uninstall SQL Native Client if it is not used by another application. Then, install vCenter with the bundled SQL Server 2005 Express database.

  • A minimum of 650MB of free space on the boot drive is required to install vCenter Server
    Although vCenter Server itself does not need to be installed on the boot drive, some required components must be installed on the boot drive. 650MB of free space is required at installation time to accommodate these required components as well as temporary files used during the installation.

    Workaround: Ensure that you have at least 650MB of free space on the boot drive before installing vCenter Server.

  • vSphere Client installation might fail with Error 1603 if you do not have an active Internet connection
    You can install the vSphere Client either from the vCenter Server media or by clicking a link on the ESX, ESXi, or vCenter Server Welcome screen. The installer on the vCenter Server media (.iso file or .zip file) is self-contained, including a full .NET installer in addition to the vSphere Client installer. The installer called through the Welcome screen includes a vSphere Client installer that accesses the Web to get .NET installer components.

    If you do not have an Internet connection, the second vSphere Client installation method will fail with Error 1603 unless you already have .NET 3.0 SP1 installed on your system.

    Workaround: Establish an Internet connection before attempting the download, install the vSphere Client from the vCenter Server media, or install .NET 3.0 SP1 before clicking the link on the Welcome screen.

Upgrade

  • Clicking the agent pre-upgrade check link on the vCenter Server installation autorun window results in an error *
    The agent pre-upgrade needs to connect to the vCenter Server database in order to scan the required hosts, and needs the vCenter SSL certificate files for the connection. If the files are not found in their default location, the following error message might be displayed:

    Failed to load config files

    Workaround: Run the agent pre-upgrade check tool on a machine where vCenter Server is installed.

  • After upgrading vCenter Server to vCenter Server 4.0 Update 2, an ESX/ESXi host in a cluster that was powered off before the upgrade does not reconnect automatically when powered on *

    Workaround: Reconnect the ESX host manually.

  • Guided Consolidation Service fails to start after an upgrade *
    After you upgrade Guided Consolidation Service, accessing it might fail with an error message similar to the following:

    The server [server name] could not interpret clients request(the remote server returned error: (404) Not found

    Clicking OK for this message might display the following error message:

    Guided Consolidation Service is currently unavailable

    Workaround: Exit vCenter Server and restart VMware vCenter Collector Service.

  • vCenter Server database upgrade fails with FK_VPX_EVENT_ARG_REF_EVENT is not a constraint error (KB 1013246) *
  • Overview performance charts are not displayed for ESX hosts and virtual machines when VirtualCenter Server is upgraded to vCenter Server 4.0 (KB 1013820)
  • Past Week stats rollupvc40 SQL Server job fails to complete after upgrading to vCenter (KB 1014209)
  • After upgrading to vCenter Server 4.0 Update 1 the setting for the Maximum Number of Database Connections to a vCenter Server is reset to 10
    vCenter Server creates a maximum of 10 simultaneous database connections by default. If you change this value in vCenter Server 4.0 by editing the Maximum Number of Database Connections to be Created database setting and then perform the upgrade to vCenter Server 4.0 Update 1, the upgrade resets the setting to 10.

    Workaround: After the upgrade, change the Maximum number of Database Connections Created value as required.

  • The vSphere Host Update Utility reports an error after attempting to upgrade an ESX host after the initial upgrade fails
    If you try to upgrade a host by using the Retry option after the initial upgrade fails, the vSphere Host Update Utility might report the following error:

    Upgrade Agent Error:1

    Workaround: Close and restart the vSphere Host Update Utility. Then run the host upgrade.
  • Issues when upgrading VirtualCenter 2.5 to vCenter Server 4.0 Update 1 without upgrading VUM and Converter
    If you upgrade VirtualCenter 2.5 to vCenter Server 4.0 Update 1 without upgrading VMware Update Manager (VUM) and VMware Converter, you might encounter the following issues:
    • When you are logging in to vCenter Server, the vSphere Client might display the error message The request failed due to an SSL error. Clicking OK for this message might display the error message The server could not interpret the client's request. Login might succeed if you click OK for this error message.
    • After you log in to vCenter Server, the Hardware Status and Storage Views tabs for the ESX host might appear interchanged.

    Workaround: None. These issues do not occur if you upgrade all components, including VUM and Converter.

  • The vCenter Server system's Database Upgrade wizard might overestimate the disk space requirement during an upgrade from VirtualCenter 2.0.x to vCenter Server
    During the upgrade of VirtualCenter 2.0.x to vCenter Server, the Database Upgrade wizard might show an incorrect value in the database disk space estimation. The estimation shown is typically higher than the actual space required.

    Workaround: None.

  • Incompatible legacy plug-ins appear as enabled in the vSphere Plug-in Manager after upgrading to vCenter Server
    If you have VirtualCenter 2.5 installed with VMware Update Manager 1.0 or VMware Converter Enterprise for VirtualCenter 2.5, and you upgrade to vCenter Server, the legacy plug-ins appear as installed and enabled in the vSphere Client Plug-in Manager. However, earlier versions of the plug-in modules are not compatible with vCenter Server. In such cases, the plug-ins might be available, but are not functional.

    Workaround: Upgrade VMware Update Manager to VMware vCenter Update Manager and VMware Converter Enterprise to VMware vCenter Converter (for vCenter Server), and then install and enable the plug-ins.

  • If vSphere Host Update Utility loses its network connection to the ESX host, the host upgrade might not work
    If you use vSphere Host Update Utility to perform an ESX/ESXi host upgrade and the utility loses its network connection to the host, the host might not be completely upgraded. When this happens, the utility might stop, or you might see the following error message:

    Failed to run compatibility check on the host.

    Workaround: Close the utility, fix the network connection, restart the utility, and rerun the upgrade.

  • When you use vSphere Host Update Utility to perform an ESX host upgrade, the upgrade might fail
    When you use vSphere Host Update Utility to perform an ESX upgrade, the upgrade might fail with the following error:

    An error occurred during upgrade. Connection with upgrade agent has been lost.

    This happens when the upgrade is 26 percent complete. In the service console, the process halts while Stopping VMware ESX server Management services is displayed.

    Workaround: Reboot the ESX host manually by pressing the reset button. The ESX upgrade continues and completes successfully, but vSphere Host Update Utility does not display the progress. To view the current host status from vSphere Host Update Utility, click Retry.

  • The Next run time value for some scheduled tasks is not preserved after you upgrade from VirtualCenter 2.0.2.x to vCenter Server
    If you upgrade from VirtualCenter 2.0.2.x to vCenter Server, the Next run time value for some scheduled tasks might not be preserved and the tasks might run unexpectedly. For example, if a task is scheduled to run at 10:00 am every day, it might run at 11:30 am after the upgrade.

    This problem occurs because of differences in the way that VirtualCenter 2.0.2.x and vCenter Server calculate the next run time. You see this behavior only when the following conditions exist:

    • You have scheduled tasks, for which you edited the run time after the tasks were initially scheduled so that they now have a different Next run time.
    • The newly scheduled Next run time has not yet occurred.

    Workaround: Perform the following steps:

    1. Wait for the tasks to run at their scheduled Next run time before upgrading.
    2. After you upgrade from vCenter 2.0.x to vCenter Server, edit and save the scheduled task. This process recalculates the Next run time of the task to its correct value.

  • Opening performance charts after an upgrade results in an error message
    After you perform an upgrade using the Microsoft SQL Express edition database, the vSphere Client displays the error message Perf Charts service experienced an internal error when you open performance charts. This happens because the installer does not restart the database service after making changes in the database settings.

    Workaround: Perform the following steps:

    1. Stop the VMware VirtualCenter Server service in Windows.
    2. Restart the database service.
    3. Start the VMware VirtualCenter Server service.
    4. Open a new vSphere Client instance and log in to vCenter Server.
  • vCenter Server database upgrade fails for Oracle 10gR2 database with certain user privileges
    If you upgrade VirtualCenter Server 2.x to vCenter Server and you have connect, create view, create any sequence, create any table, and execute on dbms_lock privileges on the database (Oracle 10gR2), the database upgrade fails. The VCDatabaseUpgrade.log file shows following error:

    Error: Failed to execute SQL procedure. Got exception: ERROR [HY000] [Oracle][ODBC][Ora]ORA-01536: space quota exceeded for tablespace 'USERS'

    Workaround: As database administrator, enlarge the user tablespace or grant the unlimited tablespace privilege to the user who performs the upgrade.

Licensing

  • A host with a single server license that fails to be added to vCenter Server is not given the option to correct licensing during a subsequent add host operation
    When an ESX or ESXi host configured with a single server license is added to a licensed vCenter Server, vCenter Server displays an error message explaining that the host cannot be added.

    Workaround: Remove the disconnected host, and add it again with a non-single server license.

  • Virtual machines cannot power on if certain licenses are installed during a scripted or interactive installation
    If you do not have the correct license serial numbers for your hardware, when you install ESX/ESXi, you might encounter a licensing error. This problem is seen because the vendor and resource check validation of license keys is not performed during the installation. After a license is validated with lib/licensecheck, a subsequent test is needed to check that the system installed is within the limits imposed by the license. However, the installer does not perform this second check.

    Workaround: Switch to evaluation mode, and then get the appropriate license from the portal.

  • Purchased add-on licenses are not displayed in the License list on the vSphere Client Licensing page
    When you view your purchased licenses on the vSphere Client Licensing page, a separate product line item for add-on editions is not displayed. For example, if you purchased a vSphere 4.0 Update 1 Standard with vMotion license, or a vSphere 4.0 Update 1 Standard with vMotion and Data Recovery license, only the vSphere 4.0 Update 1 Standard license appears.

    Workaround: To view the product features and add-on features for a license key, perform the following steps:
    1. On the vSphere Home page, click Licensing.
    2. In the upper-right corner, click Manage vSphere Licenses to launch the License wizard.
    3. Click Next to go to the Assign Licenses page.
    4. Move your cursor over the host license key to see the available product and add-on features.

Networking

  • Compliance check returns a failure message for a compliant host profile
    In the Edit host profile pane of the vSphere Client, the physical network adapters for a given vSwitch (for example, vSwitch0) under Networking Configuration > vSwitch are configured to choose physical NICs based on minimum bandwidth of the NICs in Mbps. The compliance check of a host against this host profile returns failure messages as below, even though there are physical network adapters on the host with that minimum bandwidth.

      Physical NIC vmnic1 on vSwitch vSwitch1 doesn't match bandwidth/duplexity criteria
      Phyiscal NIC vmnic0 on vSwitch vSwitch0 doesn't match bandwidth/duplexity criteria


    The compliance check fails because it attempts to find physical network adapters whose speed is greater than the value specified for the minimum bandwidth of the NIC.

    Workaround: For Minimum bandwidth of the NIC in Mbps, specify a lower value than the speed of physical NICs on the host. For example, you can change the value to 999 instead of 1000 to choose physical network adapters whose speed is 1000Mbps or more.

  • The VmwVmNetNum of VM-INFO MIB is displayed as Ethernet0 when running snmpwalk
    When snmpwalk is run for VM-INFO MIB on an ESX/ESXi host, the VmwVmNetNum of VM-INFO MIB is displayed as Ethernet0 instead of Network Adapter1 while the MOB URL in the VmwVmNetNum of VM-INFO description is displayed as Network Adapter1.

    Workaround: None.

  • Removing an ESX/ESXi host configured with a vDS from a vCenter Server system results in inconsistent networking state on the host
    If you remove an ESX/ESXi host configured with a vDS from a vCenter Server system, the host cannot reconnect to the vDS. When you add the host back to the vCenter Server system, a warning similar to the following appears:

    The distributed Virtual Switch corresponding to the proxy switches d5 6e 22 50 dd f2 94 7b-a6 1f b2 c2 e6 aa 0f bf on the host does not exist in vCenter or does not contain the host.

    The virtual machines continue to function on their respective ports, but new virtual machines are not allowed to power on. You cannot modify the vDS settings for this host by using a vSphere Client connected to the vCenter Server system.

    Workaround: Perform the following steps:

    1. Use a vSphere Client to connect directly to the ESX/ESXi host. This workaround requires a direct connection.
    2. Migrate the virtual machines off of the invalid vDS ports one by one by editing the settings of each virtual machine. This will result in prolonged network interruption to the virtual machines.
    3. Select Host > Configuration > Networking > Distributed Virtual Switch and click Remove.
    4. In a vSphere Client connected to the vCenter Server system, refresh the network settings of the host. The errors are cleared.
    5. Add the host back to the vDS, either manually or by using a host profile.
    6. Migrate the virtual machines back to their respective ports or port groups on the vDS by right-clicking the vDS and selecting Migrate Virtual Machine Networking. This process also results in network interruption to the virtual machines.

Storage

  • vCenter Server reports errors while performing the Synchronizing host task *
    When vCenter Server performs the Synchronizing host task, error messages similar to the following are logged in the vpxd.log file:

    Update for property timestamp failed

    Workaround: Such error messages are harmless and can be safely ignored.
  • vCenter Server fails to open RDM after the RDM’s LUN number changes
    VMware does not support LUN number (position) changes within the target. When the LUN number changes, vCenter Server fails to open the RDM that is built on that LUN. A raw device mapping file (RDM) resides on the VMFS datastore and points to a LUN. The LUN number shows the position of the LUN within the target. When this number (or position) changes, the vml identifier (vml_ID) for the RDM file also changes. For example, you can’t disconnect VMFS datastores and reconnect them in a different order. This changes the identification of the LUN so that it is no longer accessible, and vCenter Server prevents the virtual machine from powering on. vSphere Client uses the vml_ID for backward compatibility.

    Workaround: Remove the RDM and re-create it. This generates a new vml_ID that the LUN can recognize.

  • If ESX/ESXi hosts fail or reboot during Storage vMotion, the operation might fail and virtual machines might become orphaned
    If hosts fail or reboot during Storage vMotion, the vMotion operation might fail. The destination virtual machine's virtual disks might show up as orphaned in the vSphere inventory after the host reboots. Typically, the virtual machine's state is preserved before the host shuts down.

    If the virtual machine does not show up in an orphaned state, verify if the destination VMDK files exist.

    Workaround: You can manually delete the orphaned destination virtual machine from the vSphere inventory. Locate and delete any remaining orphaned destination disks if they exist on the datastore.

  • Using Storage vMotion to relocate a virtual machine back to its source volume might result in an insufficient disk space error
    When you use Storage vMotion to move a virtual machine to another datastore and then back to its source volume, the vSphere Client does not immediately refresh the size of the source datastore, resulting in an error.

    Workaround: Refresh the datastore in the vSphere Client. If the reported size of the datastore does not change after one attempt, wait for 30 minutes and refresh again.

  • Storage vMotion of NFS volume might be overridden by NFS server disk format
    When you use Storage vMotion to migrate a virtual disk to an NFS volume or perform other virtual machine provisioning that involves NFS volumes, the disk format is determined by the NFS server where the destination NFS volume resides. This overrides any selection made in the Disk Format menu.

    Workaround: None.

  • Storage vMotion does not support source RDM conversion to target NFS volumes
    Disk-only Storage vMotion fails for virtual mode RDMs when you convert the disks to flat/sparse format on NFS volumes.

    Workaround: Perform the following steps to migrate virtual mode RDMs to NFS volumes:
    1. Use Storage vMotion to convert an RDM virtual machine disk to disk type flat/sparse using intermediate an SAN, local, or iSCSI volume.
    2. Use Storage vMotion to relocate the converted disks from the SAN, local, or iSCSI volume to an NFS volume.

Backup

  • Reverting to snapshot might not work if you cold migrate a virtual machine with a snapshot from an ESX/ESXi 3.5 host to an ESX/ESXi 4.0 Update 1 host
    You can cold migrate a virtual machine with snapshots from an ESX/ESXi 3.5 host to ESX/ESXi 4.0 Update 1 host. However, reverting to a snapshot after migration might not work.

    Workaround: None.

  • VMware Consolidated Backup (VCB) is not supported with Fault Tolerance
    A VCB backup performed on an FT-enabled virtual machine powers off both the primary and the secondary virtual machines and might render the virtual machines unusable.

    Workaround: None.

Server Configuration

  • Host profiles that set the physical NIC configuration to auto-negotiate cannot be applied on hosts that don't support auto-negotiation *
    In a host profile, if the physical NIC is configured to auto-negotiate, and you apply this profile to a host that does not support auto-negotiate, the operation might fail with a message similar to the following:

    Error during the configuration of the host: Input/output error: Input/output error


    Workaround: None

  • vSphere Client reports incorrect host profile compliance while using the Advanced configuration option *
    On the vSphere Client, if you edit the Advanced configuration option of a host profile and run a host compliance check against this profile, the compliance check might incorrectly report the host as compliant, when it is not. Further, when you apply the host profile to a host, the vSphere Client does not report the configuration changes that you make in Advanced configuration option > Advanced Option, which incorrectly implies that no changes can be applied to the host.

    Workaround: There is no workaround to get the compliance check to correctly report noncompliance. However, you can apply the advanced option changes from the profile to the host by clicking Apply even if no configuration changes are reported in the UI.

  • SNMP PowerOn traps generated during vmware_hostd restart
    When you restart vmware_hostd, only the Warm Start trap message should be generated by default. However, for all virtual machines running on your host, the PowerOn trap messages are also generated.

    Workaround: None. You can ignore the PowerOn trap messages.

  • Host profiles do not capture or duplicate physical NIC duplex information
    When you create a new host profile, the physical NIC duplex information is not captured. This is the intended behavior. Therefore, when the reference host's profile is used to configure other hosts, the operation negotiates the duplex configuration on a per physical NIC basis. This provides you with the capability to generically handle hosts with a variety of physical NIC capabilities.

    Workaround: To set the physical NIC duplex value uniformly across NICs and hosts that are to be configured using the reference host profile, modify the host profile after it is created and reapply the parameters.

    To edit the profile, perform the following steps:

    1. On the vSphere Client Home page, click Host Profiles.
    2. Select the host profile in the inventory list, then click the Summary tab and click Edit Profile.
    3. Select Network configuration > Physical NIC configuration > Edit.
    4. Select Fixed physical NIC configuration in the drop-down menu and enter the speed and duplex information.

  • The health status of the ESX/ESXi host server components does not appear on the Hardware Status tab
    If you change the HTTPS port number in the SFCB configuration file (sfcb.cfg) to a port other than the default and restart the SFCB (CIM) server, the health status of the ESX/ESXi host server components does not appear on the Hardware Status tab. This behavior is also seen if you log in directly to an ESX/ESXi host and click the Configuration tab to view the health status. Status information for the server components does not appear. This problem occurs because vCenter Server and the SFCB server are communicating on different ports.

    Workaround: Make sure that the SFCB server communicates only through the default port.

  • vCenter service status and hardware status are not displayed after changing the vCenter Server system name
    After you upgrade from vCenter Server 4.0 to vCenter Server 4.0 Update 1 or install vCenter Server 4.0 Update 1, if you change the system name for vCenter Server installation, the vCenter service status and hardware status might not be displayed.

    Workaround: When you change the name of the system on which vCenter Server is installed, you should also change the system names at the following locations in vSphere Client:

    • Change the vCenter Server name at Administration > vCenter Server Settings > Runtime Settings
    • Replace the new system name in the URL for the keys VirtualCenter.VimApiUrl and VirtualCenter.VimWebServicesUrl at Administration > vCenter Server Settings > Advanced Settings

vCenter, vSphere Client, and vSphere Web Access

  • Discrepancies in the OverallStatus value of a virtual machine *
    vCenter Server retrieves the correct value for the OverallStatus property of a virtual machine, if you use the VirtualMachineSummary data object. However, if you check the OverallStatus by using the HostConnectInfo.VM.OverallStatus data object, vCenter Server returns a different value.

    Workaround: Use the VirtualMachineSummary data object to get the OverallStatus property value of a virtual machine. You can ignore the value that is returned when the HostConnectInfo.VM.OverallStatus data object is used.
  • Host performance chart statistics are not printed *
    On the vSphere Client, when you print a chart from the Advanced page of the Performance tab, the chart statistics might not be printed.

    Workaround: None.

  • Non processor devices are listed as processors in the vCenter Server Hardware Status tab *
    The vCenter Server Hardware Status tab might incorrectly display devices such as vFlash, disk-drive bays, and internal dual SD module (IDSM) as processors in the Sensor information page. The issue does not affect ESX/ESXi 4.0.x.

    Workaround: None.

  • vCenter Server alarm actions are triggered repeatedly even after the state of the alarm reverts to normal *
    Some vCenter Server event and state-based alarm actions are triggered repeatedly even after the alert status reverts to green (normal).

    Workaround: Avoid setting any repeating actions for alarms triggered by the following alert-level transitions: from red to yellow, and from yellow to green.

  • Cannot change vSphere Client video card settings *
    On the vSphere Client, if you edit the virtual machine properties to increase the Maximum number of displays value of a video card, the setting reverts to the default value of 1.

    Workaround: To get basic support for multiple displays, you can add a setting to the .vmx file manually. For example, to emulate two monitors, add the setting svga.numDisplays="2" in the virtual machine's .vmx file.

  • vSphere Client exports performance data for only one of the selected performance metric *
    When exporting performance data for an ESX host, if you select more than one metric for the Stacked Graph (Per VM) chart option, the resulting .xls file reports data for only the first selected metric.

    Workaround: Export performance data for the Stacked Graph (Per VM) chart separately for each metric.
  • Some events cannot trigger alarms *
    Alarms set to trigger on the following events are not triggered if the object associated with the event is unavailable upon completion of the event.

    VM Removed
    Host Removed
    Datastore Deleted

    Workaround: None

  • vCenter Client datastore browser connected to vCenter Server fails to download .vmx or .nvram files *
    vCenter Client datastore browser connected to vCenter Server might fail to download the .vmx or .nvram file of powered-on virtual machines located on a shared storage with an error message similar to the following:

    Expected put message. Got: ERROR

    This issue is resolved in this release. See KB 1019286 for more details.

  • Storage Performance graphs in the Overview performance page are not displayed correctly *
    On the vSphere Client, the graph for Space used in GB (Top 10) at Datastores > Performance might not correctly display the statistics for the past month or year.

    Workaround: None.
  • Summary tab of vSphere Client displays incorrect guest OS identifier for 64-bit FreeBSD guests *
    vSphere Client Summary tab might incorrectly display 64-bit FreeBSD guest OS as FreeBSD (32-bit).

    Workaround: None.
  • vSphere Client plug-ins fail to load if system path contains quotation marks *
    Some plug-ins might fail to load if the system path contains quotation marks. If quotation marks are removed from the system path, these plug-ins load as expected.

    Workaround: Use short names without quotation marks.
  • Virtual disk provisioning with scheduled Storage vMotion task fails *
    When you perform a Storage vMotion operation via a scheduled Storage vMotion task, virtual machine disk provisioning from thick to thin format or vice versa might fail.

    Workaround: Initiate Storage vMotion manually.
  • VMware VirtualCenter Management Webservices (vws) fails to retrieve vCenter Service health status data *
    vCenter Server health status data might not be displayed after you install vCenter Server 4.0 on a machine that has a name beginning with vws. An error message similar to the following might be written to vws.log:

    [2010-01-31 17:51:56,165 Thread-30 ERROR 'com.vmware.vim.health.impl.ComponentSpec'] Error while trying to login to https://vws/Login java.net.UnknownHostException: vws

    Workaround: Make sure that you install vCenter Server on a machine that has a name which does not begin with vws.

  • Searching for users and groups in a large environment when using Add Permissions wizard results in error or incomplete result *
    When you search for users and groups in the Add Permissions window, the search times out in large environments.

    The problem is mitigated in vCenter Server 4.0 and later by grouping search attributes with their associated types.
  • DB2 database issues after installing vCenter Server on DE locale (KB 1021971)*
  • Performance chart issues on a DE locale vCenter Server installed on Microsoft Windows Server 2003 32-bit or 64-bit with DB2 database (KB 1022019) *
  • Performance Chart Overview connection issue with vSphere database server (KB 1012812)
  • Performance Overview data is not displayed after upgrading to vCenter 4.0 or to vCenter 4.0 Update 1 (KB 1015606)
  • vSphere Client 4.0 Update 1 installed on Windows Server 7 fails to connect to VirtualCenter Server versions 2.x and 2.5.x

    Workaround: None. Windows Server 7 does not support VirtualCenter Server versions 2.x and 2.5.x.
  • vSphere Client Performance tab displays incorrect networking data
    The vSphere Client might display a virtual machine's network traffic data incorrectly on the Advanced page of the Performance tab.

    Workaround: In the service console run the esxtop command and press n for network data. If you are using ESXi, run the command resxtop –server <serverIP> from the vSphere CLI installed on Linux and press n for network data. Windows vSphere CLI does not support the command resxtop.
  • Custom ports are not detected when you log in to vCenter Server using remote DB2 database
    While using a remote DB2 database with vCenter Server, if you customize the HTTPS and HTTP ports (443 and 80 respectively by default), the custom ports are not detected, and vCenter Server still continues to listen in default ports. As a result, logging in through vSphere Client fails with the following error:

    vSphere Client could not connect with the vCenter Server [host name].
    Details: A connection failure occurred (Unable to connect to the remote server)

    You might be able to log in to vCenter Server by using localhost with the default port (443). After logging in, vCenter Health Status might display error messages similar to the following:

    Unable to retrieve health data from https://host name:<Custom Https Port>/vpxdhealth
    Unable to retrieve health data from http://localhost:<Custom Http Port>/sms/smService-web

    Workaround: Customize the values for ports: HTTTP -<Custom Port> and HTTPS – <Custom Port> from Administration  > vCenter Server Settings  > Ports in the vSphere Client. This ensures that the database is updated with these values. Restart vCenter Server Service.

  • Overview performance charts might not be displayed for clusters or resource pools (KB 1013829)
  • Web Access Service fails to start after vCenter install
    VMware VirtualCenter Management Webservices fails to start after installing vCenter. Error messages similar to the following might be written to the Tomcat service log at C:\VMware\Infrastructure\tomcat\logs:

    [2009-07-22 20:05:25] [info] Procrun (2.0.4.0) started
    [2009-07-22 20:05:25] [info] Running Service...
    [2009-07-22 20:05:25] [info] Starting service...
    [2009-07-22 20:05:25] [174 javajni.c] [error] The specified module could not be found.
    [2009-07-22 20:05:25] [994 prunsrv.c] [error] Failed creating java C:\VMware\Infrastructure\jre\\bin\server\jvm.dllagement services.
    [2009-07-22 20:05:25] [1269 prunsrv.c] [error] ServiceStart returned 1
    [2009-07-22 20:05:25] [info] Run service finished.
    [2009-07-22 20:05:25] [info] Procrun finished.


    Workaround: Click Start > Programs > VMware > VMware Tomcat > Configure Tomcat. In the window that appears, click Java, and in the text box for Java Virtual Machine, confirm that the path points to the location of the JRE installed during the installation of vCenter. Click Apply and then click OK. The Web Access Service starts successfully.

  • vCenter Service Status displays exception in locale detection error
    When you log in to vCenter Server through vSphere Client and navigate to Administration > vCenter Service Status, the vCenter Service Status might display an Unexpected exception in locale detection, using default: [object Error]error message. Clicking OK for this message might result in a dialog box displaying the An error has occurred in the script on this page Internet Explorer script error. Clicking Yes in the dialog box results in a blank vCenter Service Status screen. If you right-click on the blank screen and select Refresh, vCenter Service status displays correctly.

    Note: In some cases the Internet Explorer script error reappears even after you click Yes repeatedly, and the blank screen is not displayed. When this happens, stop the vSphere Client application in Task Manager, and log in again.

  • vSphere Client prompts for reboot after upgrade
    vSphere Client might prompt a system reboot after you upgrade from vSphere Client 4.0 to vSphere Client 4.0 Update 1.

    Workaround: None.

  • IE 7 and IE 8 browsers stop working if you click multiple times in the console area of a virtual machine
    IE 7 and IE 8 browsers might stop working if you click multiple times in the console area of a virtual machine when you are logged in to vCenter Server using vSphere Web Access on Windows Server 2008 systems.

    Workaround: Restart your browser.

  • Removing a virtual machine's virtual switch that is being used might result in an error message
    If you try to remove a virtual switch that a powered-on virtual machine is using, an error message appears. The warning message should alert you that the virtual switch is in use and cannot be removed. Removing virtual switches in such cases might cause the virtual machine to become unusable.

  • vSphere Web Access displays incorrect virtual machine CPU speed after the number of virtual processors is increased
    In vSphere Web Access, the Performance section of the Summary tab for a selected virtual machine displays incorrect information about CPU speed after the number of CPUs for the virtual machine has been increased. For example, if the number of CPUs for a virtual machine are increased from 1 CPU with a clock speed of 1.559Mhz to 2 CPUs, vSphere Web Access should display the number of CPUs and their clock speed as 2 x 1.559Mhz. However, the clock speed is incorrectly displayed as 3.117 (1.559 multiplied by 2).

    Workaround: None.

  • Using special characters in virtual machine names during virtual machine creation results in an error when connected to vCenter Server with vSphere Web Access
    When connected to vCenter Server with vSphere Web Access, using special characters, such as :"|\'{}[]-*^&@#!`~, in the virtual machine name during virtual machine creation triggers the following error:

    RuntimeFault: A general system error occurred.

    Workaround: None.
  • Virtual machine templates stored on shared storage become unavailable after Distributed Power Management (DPM) puts a host in standby mode or when a host is put in maintenance mode
    The vSphere Client associates virtual machine templates with a specific host. If the host storing the virtual machine templates is put into standby mode by DPM or into maintenance mode, the templates appear disabled in the vSphere Client. This behavior occurs even if the templates are stored on shared storage.

    Workaround: Disable DPM on the host that stores the virtual machine templates. When the host is in maintenance mode, use the Datastore browser on another host that is not in maintenance or standby mode and also has access to the datastore on which the templates are stored to find the virtual machine templates. Then you can provision virtual machines using those templates.

  • Disabled alarms for inventory objects are enabled if vCenter Server is restarted
    If an alarm for an inventory object, such as a hosts, virtual machine, datastore, and so on, is disabled in vCenter Server and vCenter Server is restarted, the alarms are enabled after the vCenter Server restart is complete.

    Workaround: Disable the alarms on the appropriate inventory objects when vCenter Server restarts.

  • For large vCenter Server inventories, when you open the vSphere Client in Linked Mode with the inventories of all vCenter Server systems fully expanded, the vSphere Client might be nonresponsive for several minutes
    Fully expanded vSphere Client inventories are those with clusters and datacenters expanded. If you close the vSphere Client after fully expanding the inventories, the next time you open it, the expanded inventory view is loaded. As a result, the vSphere Client might become non responsive for several minutes, depending on the number of vCenter Server systems and the number of objects in each vCenter Server system's inventory. The vSphere Client starts responding after it loads all inventory objects.

    Workaround: Do not to expand the nodes of every vCenter Server system in the inventory of a Linked Mode group. Collapse the nodes before you close the vSphere Client to avoid loading the expanded nodes at startup.

  • Multiple SSL warning messages appear when vCenter Server systems are joined in a Linked Mode group
    If multiple vCenter Server systems are joined in a Linked Mode group and do not use SSL certificates for authentication, multiple SSL warnings might be displayed in the vSphere Client when you log in.

    Workaround: Address each warning individually. Select the Always ignore this certificate option on each host. You must configure vCenter Servers to use SSL certificates.

  • vSphere Client displays inaccurate information in the General section of the Summary tab for hosts
    Under heavy load, the right-hand panel in the vSphere Client might fail to refresh and displays an inaccurate information in the General section.

    Workaround: Refresh the vSphere Client manually by selecting a different host, and then selecting the first host again.
  • Guided Consolidation cannot import systems that are running vCenter Converter
    Guided Consolidation import operations encounter a problem when the source system (the imported system) is running vCenter Converter. Guided Consolidation imports the system and attempts to uninstall vCenter Converter from the source system. The import operation succeeds but the following error is displayed when Guided Consolidation attempts to uninstall vCenter Converter:

    VMware Converter Agent Install failed.

    Workaround: Uninstall vCenter Converter from source systems before attempting to import them using Guided Consolidation.

  • The vSphere Client Roles menu does not display role assignments for all vCenter Server systems in a Linked Mode group
    When you create a role on a remote vCenter Server system in a Linked Mode group, the changes you make are propagated to all other vCenter Server systems in the group. However, the role appears as assigned only on the systems that have permissions associated with the role. If you remove a role, the operation only checks the status of the role on the currently selected vCenter Server system. However, it removes the role from all vCenter Server systems in the Linked Mode group without issuing a warning that the role might be in use on the other servers.

    Workaround: Before you delete a role from vCenter Server system, ensure that the role is not being used across other vCenter Server systems. To see if a role is in use, go to the Roles view and use the navigation bar to select each vCenter Server system in the group. The role's usage is displayed for the selected vCenter Server system.

    See vSphere Basic System Administration to learn about best practices for users and groups as well as information on setting roles for Linked Mode vCenter Server groups.

  • Networking problems and errors might occur when analyzing machines with VMware Guided Consolidation
    When a large number of machines are under analysis for Guided Consolidation, the vCenter Collector Provider Services component of Guided Consolidation might be mistaken for a virus or worm by the operating system on which the Guided Consolidation functionality is installed. This occurs when the analysis operation encounters a large number of machines that have invalid IP addresses or name resolution issues. As a result, a bottleneck occurs in the network and error messages appear.

    Workaround: Do not add machines for analysis if they are unreachable. If you add machines by name, make sure the NetBIOS name is resolvable and reachable. If you add machines by IP address, make sure the IP address is static.
  • You cannot re-display the toolbar in the Reports view of the Storage Views tab after you hide it
    The Reports view of the Storage Views tab has a toolbar that contains an object filter menu and a search field. These controls enable you to filter the reports tables based on object type, storage attributes, and keywords. If you hide the toolbar by selecting Hide from the toolbar's right-click menu, there is no mechanism to re-display it.

    Workaround: Close and reopen the vSphere Client.

  • Starting or stopping the vctomcat Web service at the Windows command prompt might result in an error message
    On Windows operating systems, if you use the net start and net stop commands to start and stop the vctomcat Web service, the following error message might appear:

    The service is not responding to the control function.
    More help is available by typing NET HELPMSG 2186.

    Workaround: You can ignore this error message. If you want to stop the error message from occurring, modify the registry to increase the default timeout value for the service control manager (SCM). For more information, see the following Microsoft KB article: http://support.microsoft.com/kb/922918.

  • vCenter Server allows addition of the same ESX/ESXi system twice with two different IPv6 addresses
    If you add an ESX/ESXi system to the vCenter inventory, and if that system is already managed by vCenter under a different IP address, the vCenter Server does not detect the problem. The ESX/ESXi system appears in the inventory with a new IP address, with status disconnected. Connections to the ESX/ESXi system that use the old IP address remain active.

    Workaround: Do not add the same ESX/ESXi system twice.

  • If a system has virtual network adapter, Guided Consolidation might compute a larger number of NICs for that system than the number of physical NICs
    The number of NICs for a system computed by Guided Consolidation can be larger than the number of physical NICs for the system if the system has virtual network adapters. In this case, you might get the following warning during the Plan Consolidation phase: "Host does not have the desired number of VM networks. A consolidation will result in the mapping of multiple networks of the physical computer to a single VM network." This happens for any machine with virtual NICs (for example, for any virtual machine and any (physical or virtual) machine running VMware Workstation or other hosted virtualization platform).

    Workaround: No workaround needed. You can ignore the warning.

  • Error message appears if you add a second virtual disk to a virtual machine
    Suppose you create a virtual machine with default options by using Web Access connected to ESX/ESXi 4.0. If you then connect from vSphere Web Access to the vCenter Server that manages the ESX/ESXi host and add a second virtual disk to the same virtual machine with the option Create a New Virtual Disk, the error The specified file already exists on the server appears.

    Workaround: Use the vSphere Client to connect to vCenter Server and add a second virtual disk to the virtual machine.

  • Adapter Type drop-down menu missing vmxnet3 option on virtual machine running SUSE Enterprise Linux
    A virtual machine running SLES 10 or SLES 11 for which SLES is selected as the guest operating system type does not include vmxnet3 in the Adapter Type drop-down menu. The problem is most likely to occur in virtual machines that are migrated from ESX Server 3.x to ESX 4.x, but it might also occur in other circumstances.

    Workaround: The vmxnet3 option becomes available if you change the guest operating system type from SLES to SLES10 or SLES11.
    1. Power off the virtual machine.
    2. Right-click the virtual machine and select Edit Settings.
    3. In the Options tab, click General Options.
    4. In the version field, select either SLES10 or SLES11.
  • The vSphere Client does not update sensors that are associated with physical events
    The vSphere Client does not always update sensor status. Some events can trigger an update, such as a bad power supply or the removal of a redundant disk. Other events, such as chassis intrusion and fan removal, might not trigger an update to the sensor status.

    Workaround: None.
  • The vSphere Client might take longer than expected to display newly installed extensions in the list of installed extensions
    After the installation of extensions is finished, 30-60 seconds pass before newly installed extensions appear in the list of installed extensions.

    Workaround: Restart the vSphere Client.

  • Restarting mgmt-vmware does not restart VMware Web Access
    When you restart the mgmt-vmware service, the VMware Web Access service does not restart. Instead, the service stops after a while and you cannot use VMWare Web Access to connect to the ESX host.

    Workaround: Start the VMware Web Access service manually. Do this by running the following command in the ESX service console: service vmware-webAccess start

  • Web Access service does not start after finishing ESX installation
    When you use Web Access to connect to an ESX host, the following message appears:

    503 Service Unavailable

    The reason is that after you finish installing ESX, the Web Access service does not start automatically.

    Workaround: To start the Web Access service on the ESX host, run the following command: service vmware-webAccess start

  • Joining a Linked mode group after installation is unsuccessful if UAC is enabled on Windows Server 2008
    When User Account Control (UAC) is enabled on Windows Server 2008 32-bit or 64-bit operating systems and you try to join a machine to a Linked Mode group on a system that is already running vCenter Server, the link completes without any errors, but it is unsuccessful. Only one vCenter Server appears in the inventory list.

    Workaround: Complete the following procedures:

    After installation, perform the following steps to turn off UAC before joining a Linked Mode group:

    1. Select Start > Setting > Control Panel > User Accounts to open the User Accounts dialog box.
    2. Click Turn User Account control on or off.
    3. Deselect User Account Control (UAC) to help protect your computer and click OK.
    4. Reboot the machine when prompted.

    Start the Linked Mode configuration process as follows:

    1. Select Start > All Programs > VMware > vCenter Server Linked Mode Configuration.
    2. Click Next.
    3. Select Modify Linked-Mode configuration and click Next.
    4. Click Join this vCenter Server instance to an existing Linked-Mode group or another instance and click Next.
    5. Enter the server name and LDAP port information and click Next.
    6. Click Continue to complete the installation.
    7. Click Finish to end the linking process.

    Log in to one of the vCenter Servers and verify that the servers are linked. After the vCenter Servers are linked, turn on UAC as follows:

    1. Select Start > Setting > Control Panel > User Accounts to open the User Accounts dialog box.
    2. Click Turn User Account control on or off.
    3. Select User Account Control (UAC) to help protect your computer and click OK.
    4. Reboot the machine when prompted.

  • Joining two vCenter Server instances fails with an error message in status.txt about failure to remove VMwareVCMSDS
    Joining an existing standalone vCenter Server instance to a Linked Mode group causes the vCenter Server installer to fail. When this happens, vCenter Server does not start on the machine where you are performing the installation. Also, messages indicating problems with LDAP connectivity or the LDAP service being unreachable are written to the <TEMP>/status.txt file, where <TEMP> is the temporary directory defined on your Windows system. To diagnose this problem, open the status.txt file and look for the following message:

    [2009-03-06 21:44:55 SEVERE] Operation "Join instance VMwareVCMSDS" failed: : Action: Join Instance
    Action: Removal of standalone instance
    Action: Remove Instance
    Problem: Removal of instance VMwareVCMSDS failed: The removal wizard was not able to remove all of the components. To complete removal, run "Adamuninstall.exe /i:<instance>" after resolving the following error:

    Folder '<vCenter Server installation directory>\VMwareVCMSDS' could not be deleted.
    The directory is not empty.

    Workaround: Perform the following steps:

    1. From a command prompt with administrator-level privileges, change directories to the vCenter Server installation directory.
    2. Delete the VMwareVCMSDS directory.
    3. Recover the local LDAP instance by typing jointool.bat recover.

Virtual Machine Management

  • VmBeingClonedEvent is not generated when a virtual machine is cloned inside a vApp *
    If you clone a virtual machine outside the vApp, then events are generated in the vSphere Client, and the VmBeingClonedEvent record is written to the vpxd log.

    Workaround: None
  • vCenter Server might stop responding if you add hard disk to a virtual machine and add any advanced configuration parameter at the same time *
    When editing virtual machines properties, if you add a hard disk to the virtual machine and then add advanced configuration parameter without closing the virtual machine properties window, the VMware vCenter Server service might stop and the vSphere Client might disconnect from the vCenter Server.

    Workaround: Add the hard disk, close the Edit Setting wizard for the virtual machine, re-launch the edit setting wizard, and add the advanced configuration parameters.
  • The Installation Boot options for a virtual machine are not exported to OVF
    When you create an OVF package from a virtual machine that has the Installation Boot option enabled, this option is ignored during export. As a result, the OVF descriptor is missing the InstallSection element, which provides information about the installation process. When you deploy an OVF package, the InstallSection element is parsed correctly.

    Workaround: After exporting the virtual machine to OVF, manually create the InstallSection parameters in the OVF descriptor. If a manifest (.mf) file is present, you must regenerate it after you modify the OVF descriptor.
    Example: <InstallSection ovf:initialBootStopDelay="300"> <Info>Specifies that an install boot is needed.</Info> </InstallSection>
    The inclusion of the InstallSection parameters in the descriptor informs the deployment process that an install boot is required to complete deployment. The ovf:initialBootStopDelay attribute specifies the boot delay.See the OVF specification for details.
  • An IDE hard disk added to a hardware version 7 virtual machine is defined as Hard Disk 1 even if a SCSI hard disk is already present
    If you have a hardware version 7 virtual machine with a SCSI disk already attached as Hard Disk 1 and you add an IDE disk, the virtual machine alters the disk numbering. The IDE disk is defined as Hard Disk 1 and the SCSI disk is changed to Hard Disk 2.

    Workaround: None. However, if you decide to delete one of the disks, do not rely exclusively on the disk number. Instead, verify the disk type to ensure that you are deleting the correct disk.

  • The vCenter Server fails when the delta disk depth of a linked virtual machine clone is greater than the supported depth of 32
    If the delta disk depth of a linked virtual machine clone is greater than the supported depth of 32, the vCenter Server fails and the following error message appears:

    Win32 exception: Stack overflow

    In such instances, you cannot restart the vCenter Server unless you remove the virtual machine from the host or clean the vCenter Server database. Consider removing the virtual machine from the host rather than cleaning the vCenter Server database, because it is much safer.

    Workaround: Perform the following steps:

    1. Log in to the vSphere Client on the host.
    2. Navigate to the virtual machine clone in the inventory.
    3. Right-click the virtual machine and choose Delete from Disk.
    4. Restart the vCenter Server.

    Note: After you restart the vCenter Server, if the virtual machine is listed in the vSphere Client inventory and the Remove from Inventory option is disabled in the virtual machine context menu, you must manually remove the virtual machine entry from the vCenter database.

  • Deployment of a non-persistent virtual machine by using CloneVM_Task fails
    Deployment of a non-persistent virtual machine by using CloneVM_Task in vCenter Server might fail in VirtualCenter 2.5 and vCenter Server 4.0. For example, if virtual machine A has a non-persistent disk and is cloned to virtual machine B, and virtual machine B is cloned to virtual machine C, the cloning operation fails with a fault.CustomizationPending.summary error message. However, if virtual machine B is powered on before it is cloned to virtual machine C, the cloning operation is completed successfully. Further, when a virtual machine is powered on after the virtual machine is clone-customized, the guest customization cycle might run only once.
    These symptoms occur when the virtual machine does not have VMware Tools installed, or is running an older version of VMware Tools.

    Workaround:

    1. Go to vSphere Client >Administration > vCenter Server Settings >Advanced Settings.
    2. Add a new key or modify the existing key guestcust.always-use-vmount and set its value to true.
      This enables deployment of non-persistent virtual machines in a chain and allows the guest customization cycle to run every time that virtual machines with nonpersistent disks are powered on.
  • Cannot connect to the client CD/DVD drive by using Passthrough IDE mode
    In the vSphere Client, connecting to the client CD/DVD drive as a non-administrative user by using Passthrough IDE mode might fail.

    Workaround: Log in as administrator.

vMotion and Storage vMotion

  • Migrating a powered-off or suspended ESX 3.x virtual machine with snapshots to another datastore might make the target virtual machine unusable *
    When you attempt to migrate a powered-off or suspended ESX 3.x virtual machine with snapshots to another datastore, you might see the following warning message:

    This virtual machine has snapshots enabled. Under certain conditions, some virtual disk files might not copy automatically to the target datastore. You will be unable to power on this virtual machine until the remaining virtual disk files are copied manually from the source datastore. To learn more, search the VMware Knowledge Base for "migrating 3.x snapshots.

    After you complete the migration of the virtual machine, you might see the following error message when you attempt to power on the virtual machine:

    File <unspecified filename> was not found

    Workaround: See KB 1020709.

  • Virtual machines might fail to vMotion between ESX 3.5 Hosts that are at different patch levels *
    When ESX 3.5 Hosts at different patch levels are managed by vCenter Server 4.0, the virtual machines on ESX 3.5 hosts might fail to migrate to other ESX 3.5 hosts, due to legacy virtual machine VMX settings. An error similar to the following is displayed:

    A general system error occurred: The product version of the destination host does not support one or more CPU features currently in use by the virtual machine. Such features from CPUID level 0x80000001 register 'ecx' are indicated with a '1' bit: 0000:0000:0000:0000:0000:000x:xxx0:x01x


    Workaround: Disable CPU compatibility testing in vCenter Server 4.0. In the vSphere Client connected to vCenter Server, perform the following steps:
    1. Select Administration > vCenter Server Settings
    2. Select Advanced Settings
    3. Type config.migrate.test.CpuCompatibleWithHost as the key with the value false, and click Add.
    4. Click OK.

  • Upgrade vMotion of an ESX 2.5.5 virtual machine fails, if the target ESX host is on a DRS-enabled cluster
    On vCenter Server 4.x, an Upgrade vMotion of an ESX 2.5.5 virtual machine to an ESX 4.x host that is on a DRS-enabled cluster might fail. An error message similar to the following might be displayed:

    No host is compatible with the virtual machine

    Workaround: Disable DRS on the cluster and then perform the Upgrade vMotion operation.

  • Storage vMotion conflicts with remote CD/DVD and floppy disk device connections
    CD/DVD and floppy remote backup devices are not supported with Storage vMotion. However, when you perform Storage vMotion on a powered-on virtual machine hosted by ESX/ESXi 4.0 Update 1, the toolbar icon for connecting and disconnecting CD/DVD and floppy devices remains enabled, allowing you to add these devices while Storage vMotion is in progress even though this might cause failures.

    Workaround: Before initiating Storage vMotion, disconnect all remote CD/DVD and floppy devices attached to the virtual machine by clicking the CD/DVD and floppy device connect/disconnect icon.

  • Storage vMotion on ESX/ESXi 3.5 hosts does not display correct disk type if disk type is changed during Storage vMotion
    The Storage vMotion wizard presents an option to convert disk type (from thick to thin or from thin to thick) for virtual machines on any ESX/ESXi host version. After a disk is converted and Storage vMotion is complete, the disk type is not reflected properly for ESX/ESXi 3.5 hosts. The vSphere Client still reflects the old disk type.

    Workaround: Power off the virtual machine, un-register it, and then re-register it.

  • Reverting to a snapshot might fail after reconfiguring and relocating the virtual machine
    If you reconfigure the properties of a virtual machine and move it to a different host after you have taken a snapshot of it, reverting to the snapshot of that virtual machine might fail.

    Workaround: Avoid moving virtual machines with snapshots to hosts that are very different (for example, different version, different CPU type, etc.)

VMware HA and Fault Tolerance

  • vCenter Server reports timeout error after vMotion *
    After you migrate all virtual machines from an ESX host within a short interval (about 10 seconds of each other), the following error might be displayed in the Tasks & Events tab of the host.

    HA agent has an error: Timeout while communicating with the HA agent

    Errors similar to the following might be written to the vpxa log:

    [2009-08-06 03:54:41.358 0xf7b9ab90 error 'App'] [MIGRATE] (1249555939468000) VMAP error in CompleteSource
    [2009-08-06 03:54:41.361 0xf7b9ab90 verbose 'App'] [VpxVmomi] Invoke error: vim.host.VMotionManager.completeSource session: 521e2b88-6177-ff48-cdf4-8af2932abac0 Throw: vpxapi.DasCommunicationFault

    Workaround: None. These errors can be ignored.

  • VMware HA might report misleading timeout errors when powering on or failing over a host with many virtual machines
    VMware HA timeout errors might appear a few minutes after powering on or migrating (using VMware HA) a host with many virtual machines (more than 70). This timeout error disappears when most of the virtual machines are powered on.

    Workaround: These errors can be ignored.

  • Suspended virtual machines with independent nonpersistent disks do not failover on VMware HA hosts
    If you have suspended or powered off virtual machines on a host that has VMware HA enabled and if the virtual machine disks are configured to be independent and nonpersistent, failover does not happen. Such disks are not migrated to another host if the host fails, is powered off, or is placed in Maintenance Mode. Migrating these virtual machines is currently not supported on HA because the machines are not compatible with any other host in the cluster.

    Workaround: Un register the virtual machine and register it on a compatible host.

  • Secondary virtual machine remains in inventory after Fault Tolerance has been turned off for primary virtual machine
    In some rare cases, selecting Turn Off Fault Tolerance in the vSphere Client for a primary virtual machine succeeds but the associated secondary virtual machine object is left in the inventory. This occasionally happens when a failover operation has just occurred and the new secondary virtual machine has not yet been started. This does not cause any serious consequences because the files of the secondary virtual machine should have already been deleted.

    Workaround: Manually delete the secondary virtual machine.

  • Trying to change the disk format of an FT-enabled virtual machine while migrating it across datastores results in a fault
    If you attempt to change the disk format of a powered-off, FT-enabled virtual machine while migrating it across datastores, the vSphere Client displays an InvalidArgument error message indicating that the operation has failed. The correct behavior is for the vSphere Client to disable the option to change the disk format.

    Workaround: When you relocate an FT-enabled virtual machine to another datastore, select the Same format as source as the default option.

  • Changing the system time on an ESX/ESXi host produces a VMware HA agent error
    If you change the system time on an ESX/ESXi host, after a short time interval, the following HA agent error appears:

    HA agent on <server> in <cluster> in <data center> has an error.

    This error is displayed in both the event log and the host's Summary tab in the vSphere Client.

    Workaround: Correct the host's system time and then restart vpxa by running the service vmware-vpxa restart command.

  • Configuring VMware High Availability (HA) on a heavily loaded system might result in an error message
    If you are enabling HA on a host that is experiencing a heavy load from its guest virtual machines, HA configuration might be interrupted for the host and an error message is displayed:

    HA Agent on the host failed

    Workaround: Reconfigure HA for the host, preferably after reducing the load either by powering off virtual machines or by migrating them to another host in the cluster using vMotion.

  • Failover to VMware FT secondary virtual machine produces error message on host client
    When VMware Fault Tolerance is failing over to a secondary virtual machine, if the host chosen for the secondary virtual machine has recently booted, the host client sees this attempt as failing and displays the following error message:

    Login failed due to a bad username or password.

    This error message is seen because the host has recently booted and it is possible that it has not yet received an SSL thumbprint from the vCenter Server. After the thumbprint is pushed out to the host, the failover succeeds. This condition is likely to occur only if all hosts in an FT-enabled cluster have failed, causing the host with the secondary virtual machine to be freshly booted.

    Workaround: None. The failover succeeds after a few attempts.

  • Virtual Machine Monitoring feature in VMware HA is not supported for ESX or ESXi releases prior to ESX 3.5 U3
    With VMware HA enabled for a cluster managed by vCenter Server 4.0 Update 1, the Virtual Machine Monitoring feature does not function correctly on ESX or ESXi hosts earlier than ESX Server 3.5 Update 3 and might cause false virtual machine failovers.

    Workaround: Disable the Virtual Machine Monitoring feature for such virtual machines or upgrade the ESX/ESXi host to ESX Server 3.5 Update 3 or later.

  • Non responsive Secondary virtual machines or copies of virtual machines with possibly different names might remain in the host inventory if there is an interruption when turning on Fault Tolerance
    If you have a virtual machine on which VMware HA is enabled and you turn on Fault Tolerance, a non responsive secondary virtual machine might be added to the cluster's inventory, or you might end up with multiple copies of the virtual machine with different names. This situation occurs if the destination ESX/ESXi host of the secondary virtual machine loses connectivity to its managing vCenter Server through a reboot, power loss, or disconnection from the network while the secondary copy is being created and might result in incomplete configuration settings on the secondary virtual machine.

    Workaround: Delete the non responsive secondary virtual machine from the vCenter Server inventory.

Guest Operating System

  • Static IP settings are not applied to a RHEL 5.1 virtual machine
    If you clone and customize a Red Hat Enterprise Linux Server release 5.1 virtual machine on which VMware Tools is installed using Operating System Specific Packages (OSP) and apply static IP settings to the clone, the static IP settings might not be applied to the destination virtual machine. Instead, the destination virtual machine might get auto-configured through DHCP.

    Workaround: This issue might occur due to the Kudzu service running on the RHEL guest operating system. If the Kudzu service starts on the destination virtual machine after customization, it detects the NIC as a newly added hardware and applies default DHCP settings to it and saves the static IP settings file ifcfg-ethx as ifcfg-ethx.bak. To resolve the issue, turn off Kudzu service on the source virtual machine prior to customization. Run the following command to turn off Kudzu: /sbin/chkconfig --level 345 kudzu off

  • SMP virtual machines with large amount of memory might start slowly
    SMP virtual machines with large amounts of memory might boot slower than on native hardware. Degraded performance occurs only during the boot phase as the guest operating system zeroes memory. The issue is observed on, but might not be limited to, Windows Server 2003 64-bit guest operating systems.

    Workaround: None.

  • VMware Guided Consolidation sub component fails when installed on a Windows Server 2008 64-bit virtual machine running on ESX/ESXi or Workstation hosts
    If you install VMware Guided Consolidation on a Windows 64-bit operating system running in a virtual machine hosted by ESX 3.5/ESXi 3.5 with Update 3, Patch 9 or earlier, the Guided Consolidation VMwareCollectorSubProcess.exe sub component might fail. Multiple processes running VMwareCollectorSubProcess.exe run for many hours. All analysis appears to be stalled and remains stalled (the process IDs do not change). The symptoms reappear even after rebooting the system. Multiple error logs appear in the Event Viewer attributed to VMwareCollectorSubProcess.exe. This problem also occurs on Workstation 5.5, but is fixed in Workstation 6.5.

    Workaround: You must be running ESX 3.5/ESXi 3.5 Patch 10 or later, or upgrade to ESX 4.0 Update 1/ESXi 4.0 Update 1 or Workstation 6.5.

Internationalization

  • VirtualCenter Server fails when upgrading from VirtualCenter 2.0.2 to vCenter 4.0 on a Japanese locale with SQL Server 2005
    When you upgrade from VirtualCenter 2.0.2 to vCenter 4.0 on a Japanese locale with SQL Server 2005, VirtualCenter Server might fail.

    Workaround: None

Miscellaneous

  • Stopping or restarting the vCenter Server service through the Windows Services Control MMC plug-in might lead to an error message
    Under certain circumstances, the vCenter Server service might take longer than usual to start. Stopping and restarting the vCenter Server service through the Windows Services Control MMC plug-in might lead to the following error message:

    Service failed to respond in a timely manner.

    This message indicates that the time required to shut down or start up vCenter Server was more than the configured system-wide default timeout for starting or stopping the service.

    Workaround: Refresh the Services Control screen after a few minutes, which should show that the service has been correctly stopped and restarted.

  • Diagnostic data from vCenter might be contained in file that cannot be decompressed
    While extracting a .tgz file that contains diagnostic data from vCenter, a dialog lists files that cannot be extracted, as well as an error message:

    Symbolic link points to missing files.

    Workaround: None.