VMware

VMware vCenter Server 4.1 Update 2 Release Notes

VMware Infrastructure Management Installer | 27 Oct 2011 (For all locales)
vCenter Server 4.1 Update 2 | 27 Oct 2011 | Build 491557
vSphere Client 4.1 Update 2 | 27 Oct 2011 | Build 491557

Last Document Update: 27 Oct 2011

What's in the Release Notes

The release notes cover the following topics:

What's New

The VMware vCenter Server 4.1 Update 2 release offers the following improvements:

  • Support for new processors: vCenter Server 4.1 Update 2 supports hosts with processors on AMD Opteron 6200 series (Interlagos) and AMD Opteron 4200 series (Valencia).
    Note: For the AMD Opteron 6200 and 4200 series (Family 15h) processors, vCenter Server 4.1 Update 2 treats each core within a compute unit as an independent core, except while applying licenses. For the purpose of licensing, vCenter Server treats each compute unit as a core. For example, although a processor with 8 compute units can provide the processor equivalent of 16 cores on vCenter Server 4.1 Update 2, only 8 cores will be counted towards license usage calculation.

  • Additional vCenter Server Database Support: vCenter Server now supports the following databases.
    • Microsoft SQL Server 2008 Express (x32 and x64)
    • Microsoft SQL Server 2008 R2 Express (x32 and x64)

  • Resolved Issues: This release delivers a number of bug fixes that have been documented in the Resolved Issues section.

Earlier Releases of VMware vSphere 4.1

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

Before You Begin

ESX, vCenter Server, and vSphere Client Version Compatibility

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

Installation and Upgrade

You can install vCenter Server 4.1 on Windows 64-bit platforms only. If you have VirtualCenter 2.x installed, see the vSphere Upgrade Guide for instructions about installing vCenter Server on a 64-bit operating system and preserving your VirtualCenter database.

For step-by-step guidance on installing and configuring ESX and vCenter Server, see ESX and vCenter Server Installation Guide.

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

Later releases of VMware vSphere might not support VMFS version 2 (VMFS2). The best practice is to upgrade or migrate to VMFS version 3 or later. See the vSphere Upgrade Guide.

Before you install or upgrade to vCenter Server 4.1 Update 2, verify that the database parameter options are set. For more information, see KB 1024449.

Upgrading or Migrating to vCenter Server 4.1 Update 2

You can upgrade from VirtualCenter 2.5 Update 6, vCenter Server 4.0, vCenter Server 4.0 Update 1, vCenter Server 4.0 Update 2, vCenter Server 4.0 Update 3, vCenter Server 4.1, and vCenter Server 4.1 Update 1 to vCenter Server 4.1 Update 2.

To upgrade, first verify that your database is supported with vCenter Server 4.1 Update 2, back up your supported database, SSL certificates, and VirtualCenter Server configuration, and 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.

Upgrading vSphere Client

After you upgrade vCenter Server or the ESX/ESXi host to vSphere 4.1 Update 2, you are prompted to upgrade the vSphere Client to vSphere Client 4.1 Update 2. The vSphere Client upgrade is mandatory. You must use only the upgraded vSphere Client to access vSphere 4.1 Update 2.
Note: You must use vSphere Client 4.1 Update 2 to access vCenter Servers that are part of a linked mode group with at least one vCenter Server 4.1 Update 2 instance.

Plug-Ins Updates

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

Documentation

The VMware vSphere 4.1 documentation is applicable for the VMware vSphere 4.1 Update 2 release. See the following documentation pages:

Internationalization

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

  • English
  • French
  • German
  • Japanese
  • Simplified Chinese

vSphere Client Locale Forcing Mode

With vSphere 4.1 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 does not affect other locale-related settings such as date/time or numeric formatting.

The following vSphere Client command causes the individual session to appear in English:

vpxClient -locale en_US

Open Source Components for vSphere

Open source components and their respective licenses for the most recent generally available release of vSphere are available at http://www.vmware.com/download/vsphere/open_source.html, on the Open Source tab. From this link, you can also download the source files for any GPL 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.

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.

For a list of resolved issues that might occur if you upgrade from vSphere 4.1 Update 2 to vSphere 5.0, see KB 2007404.

Guest Operating System

  • Guest operating system customization might fail when live cloning a virtual machine on Windows Server 2008 Release 2
    Cloning a Windows Server 2008 Release 2 virtual machine while it is powered on fails if you also customize the virtual machine. The result is that the destination virtual machine does not boot.

    This issue is resolved for virtual machines running on ESX/ESXi Server 4.1 Update 2 hosts.

  • Loopback entry in the /etc/hosts file might not be retained
    When deploying a new virtual machine from a template or cloning an existing virtual machine, if you customize the Linux guest operating system for the virtual machine, the loopback entry in the /etc/hosts file of the virtual machine might change. For example, the line 127.0.0.1 localhost.localdomain localhost in the /etc/hosts file changes to 127.0.0.1 <Host_Name/Alias> localhost.localdomain localhost. This issue might cause certain applications to stop working.

    This issue is resolved in this release.
  • Cannot log in to a customized virtual machine if password has characters such as &, <, >, ", or '
    If you customize a Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 virtual machine and the password of the virtual machine has any of the characters &, <, >, ", or ', you might not be able to log in to the customized virtual machine. The virtual machine might not be able to join a domain, and your user account is locked out from the active directory.

    This issue is resolved in this release.

Licensing

  • Licensing Reporting Manager might display incorrect values for average license usage
    The average usage of the license key that is reported by the Licensing Reporting Manager might sometimes be incorrect. If you export the licensing report, you notice that there might be multiple records for a few timestamps and records might be missing for a few reporting intervals.

    This issue is resolved in this release.

Miscellaneous

  • Enabling lockdown mode on ESXi hosts results in excessive messages in the logs file and no permission messages in the Event tab of vSphere Client
    If you enable lockdown mode on an ESXi host and restart the host, excessive messages similar to the following are logged in the /var/log/messages file:
    Cannot login user @127.0.0.1: no permission
    Repeated messages similar to the following are logged in the hostd log file:
    Throw vim.fault.NoPermission

    This issue is resolved in this release.
  • Browsing the VMFS datastore with NFS share might cause the ESX/ESXi host to stop responding
    If directories and files in the VMFS datastore are not owned by valid users or groups that exist on both ESX and the NFS server, and you browse the VMFS datastore with NFS share, the vpxa agent might fail and cause the ESX/ESXi host to stop responding for a short while.

    This issue is resolved in this release.
  • Tomcat updated to version 6.0.32 from Tomcat 6.0.28 to take the latest bug fixes from the Apache Software Foundation
  • Message of the day text box does not allow more than 1024 characters
    In vCenter Server 4.1, the Message of the day text box does not allow you to type more than 1024 characters.

    This issue is resolved in this release. The length for the Message of the day text box is now increased to 3072 characters.

Security

Server Configuration

  • vCenter Server might fail to apply host profiles on host if the vSphere Distributed Switch name of the profiled host has special characters
    After creating a host profile of a host connected to a vSphere Distributed Switch that has special characters such as & in its name, if you apply the host profile to another host, vCenter Server is unable to apply the profile and displays an error message similar to the following:
    a general system error occurred: not well-formed (invalid token)

    This issue is resolved in this release.
  • Host profile compliance check might fail on a clusters when one or more links are down in NICs of vNetwork Distributed Switches (VDS)
    When you run the host profile compliance check on a cluster that has vMotion and Fault Tolerance logging enabled on the VMkernel port in the port group of a VDS, if one or more links are down in NICs of the VDS, the compliance check might fail. An error message similar to the following might be displayed in the Host Compliance Failures pane:

    Failures against Clusters Requirements
    vMotion NIC speed is not at least 1000 Mbps.
    FTlogging NIC speed is not at least 1000 Mbps.


    This issue is resolved in this release.
  • Applying a host profile that configures an ESX/ESXi 4.1 host to join a domain fails when you apply the profile to a host from the host's context menu
    After applying a host profile that configures a host to join an Active Directory domain by right-clicking the host and selecting Host Profile > Apply Profile in the Host and Clusters view, if you enter the credentials to make the host join the domain, the Apply Profile window does not display any information. Clicking Finish has no response, and when you click Cancel the window closes.

    This issue is resolved in this release.
  • vSwitches and port groups might get recreated on hosts when a host profile is applied
    When you apply a host profile to a host that is network compliant, vSwitches and port groups on the host might be removed and recreated, affecting the vSwitch and port group settings of the host.

    This issue is resolved in this release.

Upgrade and Installation

  • vCenter Orchestrator is upgraded to vCenter Orchestrator 4.1.2 build 27 when vCenter Server is upgraded to vCenter Server 4.1 Update 2
    vCenter Orchestrator is automatically upgraded to vCenter Orchestrator 4.1.2 build 27 in the following situations:
    • vCenter Server 4.1 or vCenter Server 4.1 Update 1 is upgraded to vCenter Server 4.1 Update 2.
    • vCenter Server 4.0, vCenter Server 4.0 Update 1, vCenter Server 4.0 Update 2, or vCenter Server 4.0 Update 3 is upgraded to vCenter Server 4.1 Update 2 by using the data migration tool.
      Note: vCenter Orchestrator is not upgraded if you perform an in-place upgrade from vCenter Server 4.0.x.

Storage

  • vCenter Server might select hosts that are in standby mode for datastore browser operations
    When a host in the vSphere Client inventory is put in standby mode and vCenter Server is restarted, you might be able to browse the local datastore of the host. However, the contents of the datastore cannot be viewed. Sometimes shared datastore cannot be browsed if vCenter server has selected hosts in standby mode.

    This issue is resolved in this release. Starting with this release, vSphere Client does not allow you to browse local datastores of hosts in standby mode. vCenter Server does not pick hosts in standby mode to browse a shared datastore.
  • tempdb might grow excessively in size when vCenter Server 4.1 is running in a large SAN environment
    When you are running vCenter Server 4.1 in a large SAN environment with many volumes or luns and adapters, if the VMware VirtualCenter Management Webservices starts, it initializes VMware vCenter Storage Monitoring Service (SMS), which runs the queries on vCenter Server database causing tempdb to grow excessively in size and fill up the hard disk. For example, tempdb might grow up to 70GB within an hour. SQL Server disk space fills up as a result of the query running constantly on tempdb, which might cause the VirtualCenter service to fail.

    This issue is resolved in this release.

vCenter Server, vSphere Client, and vSphere Web Access

  • Renaming virtual machine folder might change the virtual machine name
    When you try to rename a folder in the VMs and Templates view of vSphere Client on a VMware HA/DRS enabled system that has large number of users logged in, then some virtual machines might incorrectly get renamed instead of the target folder. The Recent Tasks panel indicates that the Rename virtual machine task was recently run.
    This issue occurs on VMware HA/DRS enabled systems that generate too many events causing the vSphere Client to refresh its inventory view while you are trying to rename a folder.

    This issue is resolved in this release.
  • The Storage Views tab page for an ESX/ESXi host displays error messages
    In the vSphere Client, if you select the Storage Views tab for an ESX/ESXi host, the following error message might be displayed:
    An internal error was encountered while initializing the storage service
    The sms.log file might contain entries similar to the following:
    org.h2.jdbc.JdbcSQLException: Unique index or primary key violation: ENTITYID_SCSIPATH_INDEX_1 ON PUBLIC.SCSIPATH(ENTITYID) [23001-64]

    This issue is resolved in this release.
  • The Recent Tasks pane might get filled with entries of a task scheduled to export virtual machines if the interval set for the task is more than 999
    If the interval period of a task scheduled to export virtual machines is more than 999 and the task is run for the first time or when the VMware Virtual Center Server service is restarted, the Recent Tasks pane gets filled with entries of the scheduled task. Removing the queued tasks might result in an Invalid argument error.

    This issue is resolved in this release. When using the vSphere Client to schedule a task, you cannot set the interval value to more than 99. When using the RecurrentTaskScheduler data object through vSphere API/SDK to schedule a task, you cannot set the interval value to more than 999. Setting the interval value to more than 999 results in the specific parameter was not correct error.
  • Virtual machine memory resource limits that are set as unlimited in vCenter Server appear to be set to a value when vSphere Client is connected directly to a host
    After you set the limits of memory resources as unlimited for a virtual machine by using the vCenter Server, if you view these limits on individual virtual machines by connecting the vSphere client directly to the hosts, the limits appear to be set to a value.

    This issue is resolved in this release.
  • vCenter Server with multiple Distributed Resource Scheduler-enabled clusters might fail
    The Windows System Up Time counter is reset to zero when the system runs continuously for 49.7 days. If you have more than one DRS cluster where one or more cluster is created or enabled before the counter resets and one or more cluster is created or enabled after the counter resets, then when DRS is started to provide recommendations for tasks such as powering on a virtual machine, but it has not collected enough statistics from the newly created clusters, vCenter Server might fail. In such a situation, the following error message is recorded in the vpxd.log file:
    ASSERT d:/build/ob/bora-258902/bora/vpx/public\vpxDrmStats.h:674


    This issue is resolved in this release.
  • Opening more than two virtual machine consoles in vSphere Client fails with an internal error
    When more than two virtual machine consoles are opened simultaneously, and one of them is minimized, accessing and switching between the other opened virtual machine consoles fails. vSphere Client displays an error message similar to the following:
    Result:- Error: An internal error occurred in the vSphere Client.
    Details: An item with the same key has already been added.

    The viclient.log file contains entries similar to the following:
    [viclient:SoapTran:M: 7] 2010-06-14 16:22:12.138 Invoke 1230 Finish Vmomi.Core.PropertyCollector.RetrieveContents(VirtualMachine:32 [10.112.185.104]::Vmomi.VirtualMachine.snapshot) on PropertyCollector:ha-property-collector [10.112.185.104] - Serial:0.000, Server:000.009 [ :ShowExcp:M: 7] 2010-06-14 16:22:12.138 Error: An internal error occurred in the vSphere Client.
    Details: An item with the same key has already been added.


    This issue is resolved with this release.
  • Performance overview charts are not displayed for disks of virtual machines that use NFS storage
    Disk Rate and Disk Requests performance overview charts might not be displayed for virtual machines that use NFS storage. A message similar to the following might appear on the charts:
    No data available.

    This issue is resolved in this release by the addition of virtual disk rate and virtual disk requests performance overview charts.
  • Editing settings of a virtual machine that is deployed or converted from a template might result in PropertyCollector error
    After you convert a virtual machine to a template and restart the vCenter Server, if you edit the settings of the virtual machine that is converted from this template, vCenter Server might display an error message similar to the following:
    Call "PropertyCollector.RetrieveContents" for object "propertyCollector" on vCenter Server "<vCenter_Server_Name>" failed

    This issue is resolved in this release.

  • When a remote vSphere Client system that uses IPv4 embedded IPv6 address connects to vCenter Server 4.1 the VMware VirtualCenter Server service stops abruptly
    When you log in to vCenter Server using a remote vSphere Client system that uses IPv4 embedded IPv6 address with a text representation is more than 41 bytes (for example, an ISATAP address that combines an IPv6 address with an IPv4 address), an error message similar to the following might be displayed:
    The request failed because the server “name” closed the connection. (The underlying connection was closed: A connection was expected to be kept alive was closed by the server.) Call "ServiceInstance.RetrieveInternalContent" for object "ServiceInstance" on vCenter Server "name" failed.

    The VMware VirtualCenter Server service stops abruptly and messages similar to the following might be logged in the vpxd.log file:
    Panic: Win32 exception: Access Violation (0xc0000005)
    Read (0) at address ffffffffffffffff


    This issue is resolved in this release.
  • Performance of vSphere Client 4.1 is slow
    When desktop composition is enabled on the Windows systems running vSphere Client, all the panes in the vSphere Client are re-drawn when you minimize or maximize the client window, choose a different tab page, or select another virtual machine. This slows down the performance of the vSphere Client.

    This issue is resolved in this release.
  • The Datastore usage on disk alarm and the Datastore disk overallocation alarm might fail to trigger after vCenter Server is restarted
    The Datastore usage on disk alarm, the Datastore disk overallocation alarm, or an alarm that uses the Datastore Disk Usage (%) or Datastore Disk Overallocation (%) trigger type might fail to trigger if vCenter Server is restarted.

    This issue is resolved in this release.
  • Restarting the VMware VirtualCenter Server service generates a large number of vMotion tasks when DRS is set to automatic
    When DRS is set to automatic, restarting the VMware VirtualCenter Server service might generate a large number of vMotion tasks leading to unnecessary movement of virtual machines. The vMotion tasks are queued and make the management of virtual machines difficult until the tasks are completed.

    This issue is resolved in this release.
  • vSphere Client displays service console memory for ESXi 4.x hosts
    When you install ESXi 4.x on a system where ESX 4.x was installed earlier, while the ESX host is connected to vCenter Server, vSphere Client incorrectly displays service console memory in the Configuration tab for the ESXi host after reconnecting. The issue occurs because the vCenter Server retains a record of the previous ESX 4.x service console memory.

    This issue is resolved in this release.
  • vSphere Client 4.1 displays multiple windows with the error: A internal error occurred in the vSphere Client. Details: Object reference not set to an instant object

    After upgrading to vCenter Server 4.1 and vSphere Client 4.1, when vSphere Client is connected to vCenter Server, several windows might appear displaying an error message similar to the following:
    A internal error occurred in the vSphere Client. Details: Object reference not set to an instant object.

    The viclient.log file might contain error messages similar to the following:
    [viclient:Error :M: 6] 2010-09-23 10:21:53.272 UnhandledCallbackError in NotifyUpdates for server https://vcenter.usa-ed.net/sdk
    System.NullReferenceException: Object reference not set to an instance of an object.
    at VpxClient.VMList.UpdateCPUAndMemUsageForViewableItems()
    at VpxClient.VMList.OnUpdate(FilterUpdateArray fUpdates)
    at VirtualInfrastructure.Updates.PollerDispatcherImpl.NotifyUpdates(Map`2 handler2Updates)

    This issue is resolved in this release.
  • VMware Update manger plug-in might not get enabled if the VMware Webservices service is not running
    After you install the VMware Update Manager plug-in, if the VMware Webservices service is not running and you re-connect vSphere client to vCenter Server, you might not be able to enable the VMware Update Manager plug-in.

    The vminst.log file might contain entries similar to the following:
    VMware Update Manager-build-256596: 10/27/10 16:08:09 INFO: Reg/UnReg extn command: ["-v sfvctest90b.unitopr.unitint.test.statefarm.org -p 80 -U "untopr\svc_virtualcenter" -P *** -S "D:\APPS\VMware
    \Update Manager\Update Manager\extension.xml" -C "D:\APPS\VMware\Update Manager\Update Manager\\" -L "C:\Users\SVC_VI~1\AppData\Local\Temp\2\\" -O extupdate"]
    VMware Update Manager-build-256596: 10/27/10 16:08:09 AppendPath::done Path: D:\APPS\VMware\Update Manager\Update Manager\vciInstallUtils.exe
    VMware Update Manager-build-256596: 10/27/10 16:08:09 Found "D:\APPS\VMware\Update Manager\Update Manager\vciInstallUtils.exe"
    VMware Update Manager-build-256596: 10/27/10 16:08:15 Process returned 199
    VMware Update Manager-build-256596: 10/27/10 16:08:15 Error:: Unknown VC error
    VMware Update Manager-build-256596: 10/27/10 16:08:15 ERROR: VUM registration with VC failed
    VMware Update Manager-build-256596: 10/27/10 16:08:15 Posting error message 25085


    The vws.log file might contain repeated entries similar to the following:
    [2010-10-28 14:27:07,133 VwsInit INFO com.vmware.vim.vcstub.stub.ClientStub] Connection to VC at: localhost:8089 failed (com.vmware.vim.vcstub.exception.CommunicationException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target). Retrying in 15000ms.

    This issue is resolved in this release.
  • vCenter Server might fail with an access violation exception
    If the vCenter database has an entity created for a host, but vCenter Server is unable to connect to the host and retrieve the host's configuration information, vCenter Server might fail with a message similar to the following:
    Panic: Win32 exception: Access Violation (0xc0000005) Read (0) at address 0000000000000050

    This issue is resolved in this release.
  • vCenter Server reports incorrect value for provisioned space on datastores
    The vCenter Server reports incorrect value for provisioned space on datastores, and a few seconds later, displays the correct value. These changes in values might trigger the Datastore Disk Overallocation alarm. The alarm status changes from green to red and then back to green in a few seconds.

    This issue is resolved in this release.
  • Attempts to deploy an OVA/OVF template with the vSphere Client might fail
    When an OVA/OVF template's .cert file is a multiple of 1024 bytes, vSphere Client might fail to deploy the OVA/OVF template and displays an error message similar to the following:
    Failed to deploy OVF package: The request was aborted: The request was canceled

    This issue is resolved in this release.
  • Cloning operations using vSphere Client might fail with an error
    Using vSphere Client, if you clone a virtual machine or deploy one from a template while editing the virtual hardware settings, the clone operation might fail with the following error message:
    Number of virtual devices exceeds the maximum for a given controller

    This issue is resolved in this release.
  • Performance charts might display only the past day's data when viewing past week, month, and year charts
    After upgrading to vCenter Server 4.1 or later with Oracle Database, performance charts of past week, month, or year might not be displayed if the stored procedures for the vCenter Oracle Database do not populate the appropriate tables correctly. Performance charts for only a day's data are displayed.

    This issue is resolved with this release by modifying the index definitions in the vpx_sample_time table.
  • Changes made to customized advance performance charts might not get saved
    After creating a customized advance performance chart by specifying the objects to monitor or the counters to include or the time range, or the chart type, if you use the Switch to menu and view other charts, when you return to the chart you recently customized the changes made to the charts might not be retained.

    This issue is resolved in this release.
  • Statistics purge procedure might cause intermittent deadlocks in statistics roll up procedures
    A statistics purge procedure causes intermittent deadlocks when stored procedures that share database table resources are running concurrently.
    The vpxd.log file might contain errors similar to the following:
    Past Day stats rollupmaster
    1 2008-11-23 09:30:00.000 2008-11-23 09:30:00.000 Executed as user: VirtualCenter. Transaction (Process ID 88) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. [SQLSTATE 40001] (Error 1205). The step failed.
    vCenter Server might fail with a message similar to the following:
    Cannot obtain a LOCK resource at this time


    This issue is resolved in this release. If your upgrade to vCenter Server 4.1 Update 2 initiates the database upgrade process, the database upgrade process automatically replaces all of the purge scripts with the latest versions that are provided with the release installation.

    Note: The revised purge scripts have been released as attachments with KB 1009857 earlier to this release.
  • Memory-related issues with the STATs Report application might cause the tomcat service to stop with OutOfMemory errors
    When vCenter Server uses the STATs Report application, memory-related issues such as memory leaks in STATs Report might cause tomcat to consume huge amounts of memory and the tomcat service stops with OutofMemory errors.
    The stdout.log file of tomcat might contain entries similar to the following:
    java.lang.OutOfMemoryError: Java heap space
     at java.util.HashMap.newValueIterator(HashMap.java:843)
     at java.util.HashMap$Values.iterator(HashMap.java:910)
     at java.util.Collections$UnmodifiableCollection$1.<init>(Collections.java:1007)
     at java.util.Collections$UnmodifiableCollection.iterator(Collections.java:1006)
     at org.apache.commons.jci.monitor.FilesystemAlterationMonitor.run(FilesystemAlterationMonitor.java:120)
     at java.lang.Thread.run(Thread.java:619)
    Exception in thread "Thread-34" java.lang.OutOfMemoryError: Java heap space
    Exception in thread "Thread-1311" java.lang.OutOfMemoryError: Java heap space
    Exception in thread "Thread-1517" java.lang.OutOfMemoryError: Java heap space
    Exception in thread "Thread-2160" java.lang.OutOfMemoryError: Java heap space


    This issue is resolved in this release.
  • Alarms based on virtual machine snapshot size might not be triggered
    If an alarm is created to trigger when a virtual machine snapshot size exceeds a certain limit, vCenter Server might fail to trigger the alarm immediately after such a condition is detected. The alarm is triggered when you select Refresh Storage usage in the Summary tab for a virtual machine.

    With this release, alarms related to virtual machine snapshot size are triggered within two hours of reaching the size limit set for the alarm.
  • vSphere Client displays the error: Not enough storage is available to process this command
    When using Web plug-ins with vCenter Server, memory leaks might cause vSphere Client to displays out-of-memory error messages similar to the following in a dialog box:
    An internal error occurred in the vSphere Client.
    Details: Not enough storage is available to process this command.
    Contact VMware support if necessary.


    After you click Close, the dialog box reappears and you might not be able to perform any operations using the vSphere Client.

    This issue is resolved in this release.
  • vCenter Server with a DB2 database might fail when adding hosts
    When you add ESX/ESXi hosts to vCenter Server 4.1 connected to a DB2 database, the VMware VirtualCenter Server service might fail if vCenter's SQL query batch sizes exceed the supported limits of DB2.
    The vpxd.log file contains errors similar to the following:
    [02208 error 'App' opID=839EEBC3-00000264] [VdbStatement] Diagnostic data from driver is 40003:1:-30020:[IBM][CLI Driver][DB2/NT64] SQL30020N Execution of the command or SQL statement failed because of a syntax error in the communication data stream that will affect the successful execution of subsequent commands and SQL statements: Reason Code "0x220E"("
      
    [02208 error 'App' opID=839EEBC3-00000264] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) "ODBC error: (40003) - [IBM][CLI Driver][DB2/NT64] SQL30020N Execution of the command or SQL statement failed because of a syntax error in the communication data stream that will affect the successful execution of subsequent commands and SQL statements: Reason Code "0x220E"("0133")"". SQLSTATE=58009
        " is returned when executing SQL statement "INSERT INTO VPX_MULTIPATHINFO_TRANSPORT (HOST_ID, SCSI_LUN_ID, ENDPOINT_HBA_ID, VPX_TYPE, UPDATE_KEY, NODE_WWN, PORT_WWN, ISCSI_NAME, ISCSI_ALIAS, ARRAY_ID) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)"
         
    [02208 info 'App' opID=839EEBC3-00000264] Forcing shutdown of VMware VirtualCenter now


    This issue is resolved in this release.
  • Hardware Status tab, vCenter Service Status, and the search function in vCenter Server 4.1 might fail to display any results
    After upgrading to vCenter Server 4.1, you might observe the following issues:
    • When you use the search function in vCenter Server, error messages similar to the following are displayed:
      Unable to connect to web services to execute query.
      Verify that the "VMware VirtualCenter Management Webservices" service is running on https://<server name>:8443/vws
    • The vCenter Service status might fail to display the health status of vCenter Services. Error messages similar to the following are displayed:
      Cannot access the health service
      Login to the query service failed
      Do not have permission for this command
    • When you access the Hardware Status tab for an ESX host, error messages similar to the following are displayed:
      Communication error with the server.
    • The log files vim-tomcat-shared.log, stdout.log, or localhost.log located in C:\ProgramData\VMware\VMware VirtualCenter\Logs\ might contain entries similar to the following:
      ERROR com.vmware.vim.xhive.XhiveLifecycleListener] Unable to start xhive:com.vmware.vim.xhive.exception.InitializationException: com.xhive.error.XhiveException: IO_ERROR, Original message: C:\Program Files\VMware\Infrastructure\tomcat\lib\xhiveConfig\data\VcCache-default-0.XhiveDatabase.DB (The system cannot find the file specified)
      ERROR com.vmware.vim.xhive.InstanceImpl] Error starting Xhive internal server using bootstrap: C:\Program Files\VMware\Infrastructure\tomcat/lib/xhiveConfig/data/xhiveDatabase.bootstrap.com.vmware.vim.xhive.exception.InitializationException: com.xhive.error.XhiveException: INTERNAL_ERROR: Corrupt log record at lsn 7813022, Original message: Page 11 in extent queue contains incorrect magic number


      This issue is resolved in this release.
  • vCenter Server contains gaps in performance data for some ESX/ESXi hosts
    During periods of intermittent network connectivity between ESX/ESXi hosts and vCenter Server, if vCenter Server attempts to collect performance statistics from a host that is not accessible, the statistics collection task remains in the pending state and no further statistics are collected for that host. This causes vCenter Server to show gaps in performance data for the inaccessible ESX/ESXi hosts. The vpxd.log files might contain entries similar to the following:
    [VpxdMoHost::CollectRemote] Attempt to collect stats on <Host_Name> [VpxdMoHost::CollectRemote] Not collecting stats this time on host <Host_Name> because collection pending Had to drop performance data coming from host <Host_Name> because it has error (The specified network name is no longer available.)

    This issue is resolved in this release.
  • vCenter Server might become slow or unresponsive when used with certain third-party applications
    When vCenter Server is installed with Oracle database and used along with certain third-party applications such as nworks Management Pack, vCenter Server might perform slowly or become unresponsive due to issues with queries that are run on vpx_event table.

    This issue is resolved in this release. The queries that run on vpx_event table are optimized for better execution on Oracle databases, preventing performance issues on vCenter Server.
  • vCenter plug-ins might not load if the value of the Path environment variable has non-ASCII characters
    If the value of the Path environment variable is set to have non-ASCII characters such as " in the vSphere Client system, vSphere Client might fail to load the vCenter plug-ins.

    This issue is resolved in this release.
  • A task scheduled to create a snapshot of the virtual machine succeeds even though the CreateSnapshot_Task ()method is disabled for a virtual machine
    Even after the CreateSnapshot_Task () method is disabled for a virtual machine by using an API, if a task is scheduled to create a snapshot of the virtual machine, vCenter Server succeeds in creating the snapshot of the virtual machine at the scheduled time.

    This issue is resolved in this release. Starting with this release, a snapshot is not created, and an error message is displayed when an attempt to run the scheduled task is made.

Virtual Machine Management

  • Reverting a virtual machine to a snapshot might fail
    When a virtual machine with snapshots is migrated to another ESX/ESXi host, a mismatch of the snapshot object ID in the vCenter database might cause vCenter to fail in reverting the virtual machine to the states of the snapshot, and vSphere Client displays a message similar to the following:

    This object has already been deleted or has not been completely created.

    vCenter Server logs might contain entries similar to the following:
    13421:[2011-03-08 09:50:53.257 02580 info 'App' opID=3DB842F7-0000013A] [VpxLRO] -- ERROR task-489263 -- vm-9273 -- vim.vm.Snapshot.revert: vmodl.fault.ManagedObjectNotFound:
    13422-Result:
    13423-(vmodl.fault.ManagedObjectNotFound) {
    13424- dynamicType = <unset>,
    13425- faultCause = (vmodl.MethodFault) null,
    13426: obj = 'vim.vm.Snapshot:snapshot-133808',
    13427- msg = "",


    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

IPv6 Disabled by Default. IPv6 is disabled by default when installing ESX 4.1 Update 1.

Hardware iSCSI. Broadcom Hardware iSCSI does not support Jumbo Frames or IPv6. Dependent hardware iSCSI does not support iSCSI access to the same LUN when a host uses dependent and independent hardware iSCSI adapters simultaneously.

List of Known Issues

The following issues are known to occur. The following list of issues pertains to vCenter Server 4.1 Update 2. Known issues not previously documented are marked with the * symbol. The known issues are grouped as follows:

Internationalization

  •  Drop-down menu items for DRS Rules UI screen improperly translated
    When you create a VM/Host DRS rule using a non-English UI, the drop-down menu options are incomprehensible.

    Workaround: None.

  • Help files of Performance Overview charts in the French localized vCenter Server are displayed in English *
    When using the French localized vCenter Server, if you click the help icons of the Performance overview charts, the help files are displayed in English.

    Workaround: Change the URL of the help file from .../help/en/... to .../help/fr/....

Miscellaneous

  •  VM/Host DRS Rules are still enforced if DRS is disabled
    If you specify a VM/Hosts DRS rule for a DRS cluster, and if DRS is disabled, this rule is still in effect. Accordingly, if you manually power on a virtual machine specified in this type of rule, an error might occur if this operation violates the rule.

    Workaround: Manually disable the rule in the cluster Settings dialog box.

  • Group ID length in vSphere Client shorter than group ID length in vCLI
    When you specify a group ID using the vSphere Client, only nine characters are allowed. In contrast, you can specify up to ten characters when you specify the group ID using the vicfg-user vCLI.

    Workaround: None.

Networking

  •  Clone operation fails on a virtual machine with invalid vDS backing
    If any of a virtual machine's network adapters are connected to an invalid or missing vDS or dvPort group, that virtual machine cannot be cloned.

    Workaround: Make sure that all of a virtual machine's network adapters have valid backing before cloning the virtual machine.

  • Newly added users with read-only role can add VMkernel NICs to ESX/ESXi hosts
    Newly added users with a read-only role should not be able to make changes to the ESX/ESXi host setup with the exception of adding VMkernel NICs, but are able to.

    Workaround: None. Do not rely on this behavior because read-only users will not be able to add VMkernel NICs in the future.

  • Memory problems occur when a host uses more than 1016 dvPorts on a vDS
    The maximum number of dvPorts allowed per host on vDS is 4096, but memory problems can start occurring when the number of dvPorts for a host approaches 1600. When this occurs, you cannot add virtual machines or virtual adapters to the vDS.

    Workaround: Configure a maximum of 1016 dvPorts per host on a vDS.

  •  Destroy operation fails on virtual machines with invalid vDS backing
    If any of a virtual machine's devices are connected to an invalid vDS, a destroy operation might not be completed successfully. The virtual machine is destroyed on the host, but remains visible in the vSphere Client inventory.

    Workaround: To remove the virtual machine from the vCenter inventory, right-click the virtual machine and select Remove from inventory.

  • Reconfiguring a VMXNET3 NIC while Wake-on-LAN is enabled and the virtual machine is asleep causes the virtual machine to resume

    Workaround: Put the virtual machine back into sleep mode manually after reconfiguring a VMXNET3 vNIC (for example, after performing a hot-add or hot-remove).

  •  Adding multiple hosts to a Cisco Nexus 1000v switch in one batch might fail
    If you try to add multiple hosts with different patch or update levels to a Cisco Nexus 1000v switch, the add hosts operation fails.

    Workaround: Add hosts with different patch or update levels to the switch individually.

  •  Virtual machine MAC address conflicts
    Each vCenter Server system has a vCenter Server instance ID. This ID is a number between 0 and 63 that is randomly generated at installation time but can be reconfigured after installation.
    vCenter Server uses the vCenter instance ID to generate MAC addresses and UUIDs for virtual machines. If two vCenter Server systems have the same vCenter instance ID, they might generate identical MAC addresses for virtual machines. This can cause conflicts if the virtual machines are on the same network, leading to packet loss and other problems.

    Workaround: If you deploy virtual machines from multiple vCenter Server systems to the same network, you must ensure that these vCenter Server systems have unique instance IDs.

    To view or change the vCenter Server instance ID:

    1. Log in to vCenter Server using the vSphere Client, and select Administration > vCenter Server Settings.
    2. Select Runtime Settings.
      The vCenter Server Unique ID text box displays the current vCenter Server instance ID.
    3. If this ID is not unique, type a new unique value between 0 and 63 in the vCenter Unique ID text box and click OK.
    4. If you changed the vCenter Server instance ID, restart vCenter Server for the change to take effect.

    If you have existing virtual machines with conflicting MAC addresses, edit the MAC addresses to make them unique:

    1. Ensure that the virtual machine is powered off.
    2. In the vSphere Client inventory, right-click the virtual machine and select Edit Settings.
    3. On the Hardware tab, select the virtual network adapter for the virtual machine.
    4. Under MAC Address, select Manual and specify a unique MAC address.
    5. Click OK.

    Alternatively, you can force vCenter Server to generate a new MAC address for the virtual network adapter by configuring the virtual network adapter to use a Manual MAC address, and then reconfiguring it to Automatic.

Server Configuration

  • Applying host profiles on hosts can swap the order of vmk numbers *
    Applying a host profile might result in vmk numbers to be swapped between portgroups, if the portgroup order on the host is different than the order in the host profile. This issue occurs because vCenter creates portgroups in the order they are listed in the host profile, and vmk number assignments are done according to portgroup creation order.
    For example, if the port profile of a profiled host lists vMotion before Management and you apply this profile to a host, vmk number is assigned to vMotion first and then to Management.
    If the network configuration of the ESX/ESXi host is similar to the following:
    vSwitch0:
    vmk0: Management
    vmk1: VMotion

    After applying the host profile, the network configuration of the ESX/ESXi host looks similar to the following:
    vSwitch0:
    vmk0: VMotion
    vmk1: Management


    The IP address of the host changes to the IP address that is associated with vmk0 (for example, the vMotion IP address) and the the host appears to have the wrong IP address after applying the host profile.

    Workaround: To resolve the issue described in the example scenario, do either of the following:
    • Delete vMotion from the host profile list, and then re-add it so that it comes after Management.
    • Create a host profile from an ESXi/ESX host that lists the Management portgroup before the vMotion portgroup.
  • Host Profiles compliance check displays non compliant when host is configured to join an organizational unit within a domain *
    After you apply a host profile that configures a host to join an organizational unit (OU) in a domain, if you perform the host profile compliance check on the host with the same host profile, the result shows the host as non compliant.

    Workaround: Disable compliance check for directory services in the host profile.
  • Applying a host profile to an ESX host sometimes fails, resulting in an error about operation not being supported
    For this issue, the following error appears in the vSphere Client:

    Operation not supported: Operation not supported


    This problem occurs because the host profile attempts to configure settings on a pseudo physical NIC vusb0 on the ESX host. However, the pseudo NIC does not allow changes to the configuration settings.

    Workaround:
    1. Right-click the profile and select Edit Profile.
    2. Navigate to the Physical NIC configuration of the Network configuration.
    3. Find the physical NIC configuration profile for vusb0 by checking the name of the physical NIC.
    4. Right-click that physical NIC configuration profile and click Remove Profile.
  • Operations that involve applying profiles and checking profile compliance fail for host profiles after you update PnicsByName policy within DvsProfile
    After updating the PnicsByName policy of DvsProfile, the host profile application and compliance check fails. This failure occurs when multiple physical NICs are entered. While the user interface allows multiple physical NICs, only one physical NIC can be added for the PnicsByName policy within DvsProfile.

    Workaround: Ensure that only one physical NIC is added for this policy.

  • Host profile compliance checks fail to detect non-compliance when a host has different portgroups or NAS datastores
    When a host profile is checked for compliance against a host that has different portgroups or NAS datastores than the ones specified in the host profile configuration settings, the compliance check incorrectly displays the result as Compliant.
    Workaround: User can still apply the host profile by using the Apply Profile option, which detects the differences and applies the configurations correctly.

Storage

  • Newly created virtual hard disks are incorrectly placed at the same location as an existing virtual hard disk located in a different directory
    For a virtual machine whose virtual hard disk is in the same datastore as its .vmx files but is in a directory different from that of the .vmx files, when you create a virtual hard disk, the new virtual hard disk is placed in the directory where the existing virtual hard disk is placed and not in the default .vmx directory.

    Workaround: Move the newly added virtual hard disk to the same desired location as the virtual machine's .vmx file by using Data Browser, then remove the virtual disk by using the Edit Settings option for the virtual machine and then re-add the virtual hard disk selecting the Use an existing virtual disk option.

    Note: When an existing virtual disk is located on a different datastore/LUN, any newly created disk drive is created in the same directory as the .vmx file.
  •  After you upgrade a storage array, the hardware acceleration status in the vSphere Client changes to Supported after a short delay
    When you upgrade a storage array's firmware to a version that supports VAAI functionality, vSphere 4.1 does not immediately register the change. The vSphere Client temporarily displays Unknown as the status for Hardware Acceleration.

    Workaround: This delay is harmless. The hardware acceleration status changes to Supported after a short period of time.

Upgrade and Installation

  • Microsoft SQL Server 2008 Express (x32 and x64) and Microsoft SQL Server 2008 R2 Express (x32 and x64) databases are compatible with vCenter Server 4.1 Update 2 for a maximum of 5 hosts and 50 virtual machines *
  • vCenter Server 4.1 database upgrade might fail if the default schema is not dbo *
    If you do not use the default dbo schema when using Microsoft SQL database for your vCenter Server repository, attempts to upgrade to vCenter Server 4.1 might fail with a message similar to the following:
    Exception thrown while executing SQL script

    The vcdatabaseupgrade.log file might display errors messages similar to the following:
    SET IDENTITY_INSERT dbo.vpx_device_tmp ON
    [11/5/2010 11:51:50 AM] Error: Failed to execute command: SET IDENTITY_INSERT dbo.vpx_device_tmp ON
    [11/5/2010 11:51:50 AM] Got exception: ERROR [42000] [Microsoft][SQL Native Client][SQL Server]Cannot find the object "dbo.vpx_device_tmp" because it does not exist or you do not have permissions.


    Workaround: Restore the backed up database, change the default schema for the SQL login to dbo, and then upgrade the vCenter database.
  • Cannot uninstall vCenter Server running on Windows Server 2008 Release 2 by using the All Programs menu *
    When you uninstall vCenter Server running on Windows Server 2008 Release 2 by selecting Start > All Programs > VMware > vCenter Server Linked Mode Configuration, an error similar to the following might be displayed:
    Error 280135: setup failed to copy LDIFDE.EXE from system folder to '%windr%\ADAM' folder

    Workaround: To uninstall vCenter Server, use Add/Remove Programs.
  •  Installation of vCenter Server 4.1 using an existing IBM DB2 database sometimes fails with a DB2 error message
    When you install vCenter Server 4.1 using an existing vCenter Server DB2 database, you might see an error message similar to the following:
    A database error occurred: "ODBC error: (5UA01) - [IBM][CLI Driver][DB2/NT64] SQL20453N The task "RULE_TOPN1_DB2USER1" cannot be removed because it is currently executing. SQLSTATE=5UA01" is returned when executing SQL statement "CALL CREATE_TOPN_JOB1_PROC()"

    This message appears when DB2 encounters an known IBM issue. This issue indicates that a DB2 task is running and the vCenter Server installer cannot initialize the vCenter database.

    Workaround: To eliminate the conflict so you can install vCenter Server, perform the following steps:
    1. If vCenter Server is running, shut it down.
    2. Use the Services control panel to stop and restart the db2 service.
    3. Restart the installation process, being sure to select the option to overwrite the existing database.
  •  Installation of the vSphere Client might fail with the error, The Microsoft Visual J# 2.0 Second Edition installer returned error code '4113'
    When you install the vSphere Client, the installer might attempt to upgrade an out-of-date Microsoft Visual J# runtime. The upgrade will be unsuccessful and the vSphere Client installation fails.

    Workaround: Uninstall all previous versions of Microsoft Visual J# and install the vSphere Client. The installation includes an updated Microsoft Visual J# package.

  •  After you install or upgrade to vCenter Server 4.1 with an Oracle database using an Oracle 64-bit ODBC driver, vCenter Server might fail to start
    When you perform a new installation or upgrade to vCenter Server 4.1 with an Oracle database using an Oracle 64-bit ODBC driver, you might see the error message, Database version id '0' is incompatible with this release of VirtualCenter, and the vCenter Server service fails to start.

    Workaround: Upgrade to the 10.2.0.4 or 11.1 Oracle 64-bit ODBC driver.

  •  When you uninstall vCenter Server 4.1 without stopping the vCenter Server service, the local ADAM instance might not be removed
    You must stop the vCenter Server service before you uninstall vCenter Server 4.1. Otherwise, the ADAM instance might remain on the system. This applies to both vCenter Server 4.1 installations and upgrades, and to standalone or linked vCenter Server systems.

    Workaround: Stop the VMware VirtualCenter Server service before you uninstall vCenter Server 4.1.

  •  vCenter Server installation or upgrade silently changes Microsoft SQL Server settings to enable named pipes
    When you install vCenter Server 4.1 or upgrade vCenter Server 4.0.x to vCenter Server 4.1 on a host that uses Microsoft SQL Server with a setting of "Using TCP/IP only," the installer changes that setting to "Using TCP/IP and named pipes" and does not present a notification of the change.

    Workaround: The change in setting to Using TCP/IP and named pipes does not interfere with the correct operation of vCenter Server. However, you can use the following steps to restore the setting to the default of Using TCP/IP only.

    1. Select Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration.
    2. Select Surface Area Configuration for Services and Connections.
    3. Under the SQL Server instance that you are using for vCenter Server, select Remote Connections.
    4. Change the option under Local and Remote Connections and click Apply.
  •  Cannot create vCenter Server directory services during vCenter Server or vSphere Client installation
    When you select a compressed folder as the installation path for vCenter Server or vSphere Client, vCenter Server Directory Services is not created.

    Workaround: Perform one of the following tasks:

    • Uncompress the disk and retry the installation.
    • Run the installation on an uncompressed disk.
  •  vCenter Server installation fails with the error, Setup cannot create vCenter Directory Services instance
    If you remove the Everyone permission from the HKLM registry, vCenter Server installation fails with the error Setup cannot create vCenter Directory Services instance.

    Workaround: Add the Everyone permission to the HKLM registry:

    1. From the Windows command line, type regedit and press Enter.
    2. In the Registry Editor, right-click HKEY_LOCAL_MACHINE and select Permissions.
    3. Click Add.
    4. Click Advanced.
    5. Select Everyone from the list and click OK.
    6. Click Apply and click OK.
  • vCenter Server instances that use a DB2 9.5.0 database does not allow for addition of hosts
    If you are using a vCenter Server system with an IBM DB2 9.5.0 64-bit ODBC driver, you cannot manage hosts for that vCenter Server.

    Workaround: Apply DB2 9.5 Fix Pack 5.

  • Upgrading from vCenter Server 4.0 to 4.1 unregisters vCenter Guided Consolidation service (GCS)
    This issue only occurs when GCS is a registered extension (plug-in).

    Workaround: To establish the registration information with vCenter Server 4.1, reinstall GCS.
  •  vCenter Server upgrade proceeds despite changing Web Services HTTP or HTTPS port using established port
    When changing the Web Services HTTP or HTTPS port by using an established port on the Configure Ports page, the vCenter Server upgrade proceeds and does not produce an error.

    Workaround: None.

  • Install process fails when you uninstall and reinstall vCenter Server
    Installation fails with the error Cannot create vCenter Server Directory Services when you uninstall and reinstall vCenter Server on the same system.

    Workaround: After you uninstall vCenter Server, reboot the system before you reinstall vCenter Server.

  • Upgrading vCenter Server with the VM Total Disk Latency (ms) trigger set might lead to error messages
    This issue occurs after upgrading vCenter Server when the VM Total Disk Latency(ms) trigger and at least one other trigger are set at the same time. In such a scenario, using vSphere Client to edit the Alarm in Trigger section causes the following error message to appear in vSphere Client:

    The triggers for this alarm cannot be displayed or changed through the vSphere Client. Use the vSphere API to modify these alarm triggers.

    Workaround:

    1. Before upgrading vCenter Server, delete the VM Total Disk Latency(ms) trigger.
    2. Upgrade both vCenter Server and vSphere Client.
    3. Add the VM Max Total Disk Latency(ms) trigger.
  •  vCenter Server installation fails if the user account used to install vCenter Server and overwrite an existing DB2 database is not member of the db2user group or the db2admin group
    Error 25003: Cannot create repository is displayed when the user account used to install vCenter Server and overwrite an existing DB2 database is not a member of the db2user group or the db2admin group. Clicking OK in the error message dialog box closes the dialog box and rolls back the installation.

    Workaround: Add the database user to the db2user or db2admin group. Consult your database administrator.

  • Installation of vCenter Server 4.1 Update 2 with IBM DB2 9.7.2 Express C database might fail
    When installing vCenter Server 4.1 Update 2 with IBM DB2 9.7.2 Express C database, a warning message error similar to the following might be displayed:
    Warning 25205 : Error loading licensekey to LDAP server

    When you click OK, vCenter Server is installed successfully, but the VMware VirtualCenter Server service is not started. If you manually start the VMware VirtualCenter Server service, a message similar to the following is displayed:
    Windows could not start the VMWare VirtualCenter Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 2.

    Workaround: Create DB2USERS and DBSYSMON groups and assign to DB2 user. Restart the VMware VirtualCenter Server service.

vCenter Server, vSphere Client, and vSphere Web Access

  • Hardware Status tab might not display the health status *
    vCenter Server might fail to display the health status in the Hardware Status tab.
    The vws.log file contains entries similar to the following:
    [2010-08-19 13:43:36,128 pool-8-thread-7 ERROR com.vmware.vim.security.vcauthorize.AuthorizeMgr] Parent chain incomplete or: group-d1

    When you check the vCenter database and run the following query, the resulting ID should be 1:
    select ID from VPX_ENTITY where TYPE_ID=7

    If the resulting ID is of any value other than 1, then Hardware Status does not display the status.

    Workaround: None
  • Event related to the accounts event category might not trigger alarms *
    Alarms created in the vCenter Server with any of the following event triggers do not generate an alarm, when the trigger conditions are met:
    • Account created
    • Account removed
    • Account updated

    Workaround: None.

  • Hardware Status tab does not refresh automatically *
    The hardware health status properties for a host that are displayed in the Hardware Status tab are not refreshed automatically, because such refreshes caused performance issues.

    Workaround: Click Update in the Hardware Status tab to view the latest hardware health status properties of hosts.
  • vCenter Server reports incorrect value for provisioned space on datastores *
    The vCenter Server reports incorrect value for provisioned space on a datastore if you refresh the datastore immediately after powering on or powering off a virtual machine.

    Workaround: None
  • License key might not get migrated after vCenter Server is upgrade to vCenter Server 4.1 *
    After installing vCenter Server 4.0 in the evaluation mode, if you assign a license to the vCenter Server system after the evaluation period expires and you then upgrade to vCenter Server 4.1, the vCenter Server license key is not migrated after the upgrade. All hosts might get disconnected from the vCenter Server system. This issue occurs when the vCenter Server license key that is assigned after the evaluation period expires does not reflect in the database registry when backup operations are run.

    Workaround:
    • Before upgrading to vCenter Server 4.1, ensure that the vCenter Server license key is assigned correctly to vCenter Server by clicking Home > Licensing.
    • When upgrading to vCenter Server 4.1, enter the vCenter Server license key in the license screen of the installation wizard.
  • Advanced performance chart views does not display data for virtual machines if data counters not applicable to virtual machines are selected *
    When customizing advanced performance chart views, if you use the per-virtual-machine stacked graph chart type for virtual machines and select data counters that are not applicable for virtual machines, the resulting chart does not display any performance data for the virtual machine. The Performance Chart Legend pane also does not show any data for the virtual machine.

    Workaround: When customizing advanced performance chart views, do not select data counter that are not applicable for virtual machines. To know the list of counters applicable for virtual machines, select a virtual machine in the vCenter Server inventory, click the Performance tab, and navigate to Advanced > Chart Options.
  • Users with Administrator privileges might not be able to obtain complete logs by running the Generate vCenter Server log bundle utility if vCenter Server is installed on Windows Server 2008 Release 2
    If vCenter Server is installed on Windows Server 2008 Release 2 and a vCenter Server system user with Administrator privileges runs the Generate vCenter Server log bundle utility, the complete logs are not obtained in the vcsupport folder. This issue is dose not occur for built-in Administrator user accounts.

    Workaround: As a user with administrator privileges, log into the Windows Server 2008 Release 2 vCenter Server System, navigate to Start -> All Programs -> VMware, right-click Generate vCenter Server log bundle and select Run as Administrator
  • ESX/ESXi hosts stop responding to vCenter Server if they are added using IPv6 link local address
    If ESX/ESXi hosts are added to vCenter Server using IPv6 link local address, the hosts enter a nonresponsinve state a few seconds after they are added.
    Workaround: None
  •  In Windows Vista, all Help buttons in the Update Manager Client open the default Update Manager help page
    If you are using Internet Explorer 7 browsers on Windows Vista machines, the vCenter Update Manager context-sensitive help does not display the required help pages. Instead, the help displays the Introducing Update Manager help page.

    Workaround: Apply Service Pack 2 to Windows Vista. For more details, see the following Microsoft knowledge base article http://support.microsoft.com/kb/942172.

  • Error occurs while trying to restart the VMware VirtualCenter service or the VMware Web service from Windows services panel
    While you are trying to restart the VMware VirtualCenter service or the VMware Web service from Windows Control Panel, you see the following message:
    Error 1053: The service did not respond it the start or control request in a timely fashion.

    Workaround: Modify two registry keys on the affected vCenter Server host as follows:

    1. Start regedit and locate the following key in the registry:
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\
      vctomcat\Parameters
    2. Add the following (DWORD) registry values:
      Value Name: WaitHintStart
      Value: <Time to wait for service to start in milliseconds>
      Value Name: WaitHintStop
      Value: <Time to wait for service to stop in milliseconds>
      In both cases, the wait time should be greater than 40 seconds.
    3. Locate the following key in the registry:
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\
      vpxd\Parameters
    4. Add the following (DWORD) registry values:
      Value Name: WaitHintStart
      Value: <Time to wait for service to start in milliseconds>
      Value Name: WaitHintStop
      Value: <Time to wait for service to stop in milliseconds>
      In both cases, the wait time should be greater than 40 seconds.
  •  Problems installing or running vCenter Server, VMware Update Manager, or VMware Converter on an operating system using the Czech locale
    If you attempt to install vCenter Server, Update Manager, or VMware Converter on an operating system that is using the Czech locale, you either cannot install the product or might experience functional problems when trying to use the product.

    Workaround: No workaround exists for Czech locale operating systems. Use English locale operating systems to evaluate the product.

  • Changing the network settings of an ESXi host prevents some hardware health monitoring software from auto-discovering it
    After you change the network settings of an ESXi host, third-party management tools that rely on the CIM interface (typically hardware health monitoring tools) are unable to automatically and dynamically discover the host through the Service Location Protocol (SLP) service.

    Workaround: Manually type the hostname or IP address of the host in the third-party management tool. Alternatively, restart slpd and sfcbd-watchdog using one of the following methods:

    • Log in to Technical Support Mode and run the following commands:

    • /etc/init.d/slpd restart
      /etc/init.d/sfcbd-watchdog restart

    • Restart management agents on the Direct Console User Interface (DCUI). This restarts other agents on the host in addition to the agents affected by this defect and may be more disruptive.
  • When using DB2, the vCenter Server service does not restart automatically after network connectivity is restored
    If you lose network connectivity to a vCenter Server system that is configured to use an IBM DB2 database, you will be unable to start the vCenter Server service after network connectivity is restored.

    Workaround:

    1. Close all existing connections from the vCenter Server machine to the IBM DB2 database using the Application List utility.
    2. Log in to the DB2 UDB database as dbadm, as the instance owner, or as the database owner.
    3. Run the following command to obtain information about the user you want to disconnect from the database: db2 list applications

      An output similar to the following appears:
      Auth Id   Application     Appl.       Application Id
                Name            Handle
      --------  --------------  ----------  --------------------------
      VPX       db2bp.exe       3428        *LOCAL.DB2.100225221240
    4. Note the application handle number and use it to run the following disconnect command:

      force application <application_handle_number>
  • Performance data older than one day is not available for some entities when vCenter Server is configured to use DB2
    Performance data older than one day is not available for some entities when vCenter Server is configured to use DB2.

    Note: The UTIL_HEAP_SZ parameter allocates memory. This parameter can be tuned to increase memory allocation to DB2. Reduce diaglevel to 3 to reduce diag.log size and excessive log generation. This allows DB2 to process jobs in the background. Refer to the following IBM Infocenter page for DB2 specific parameters.

    Workaround: If you are using DB2 9.5, upgrade to DB2 9.5 Fix Pack 5.

  •  Hot-plug operations fail after the swapfile is relocated
    Hot-plug operations will fail for powered-on virtual machines in a DRS cluster, or on a standalone host, with an error failed to resume destination; VM not found after the swap file location is changed.

    Workaround: Do one of the following:

    • Reboot the affected virtual machines to register the new swap file location with them, then perform the hot-plug operations.
    • Migrate the affected virtual machines using vMotion.
    • Suspend the affected virtual machines.
  • Accented and composite characters are not displayed in the index of French-language Help
    Accented and composite characters, such as Æ and Œ are not displayed in the indexes of French-language versions of the vSphere Client Help, DRS Troubleshooting Help, Overview Performance Charts Help, and Web Access Help.

    Workaround: None.

  • Failure when attempting to join a vCenter Server instance that is hosted on a system running Windows Server 2008 with User Account Control enabled with Linked Group
    If you are joining or isolating a Windows Server 2008 system that has User Account Control (UAC) to a Linked Mode group, the operation fails without an error message.

    Workaround: Perform the following steps:

    1. Turn off User Account Control (UAC) before joining the system to a Linked Mode group as follows:

      1. Open Windows Control Panel.
      2. Select Start > Setting > Control Panel > User Accounts.
      3. Select Turn User Account control on or off.
      4. Deselect User Account Control (UAC) to help protect your computer and click OK.
      5. Restart the machine.

    2. Start the Linked Mode configuration as follows:
      1. Select Start > All Programs > VMware > vCenter Server Linked Mode Configuration and click Next.
      2. Select Modify Linked-Mode configuration and click Next.
      3. Click Join this vCenter Server instance to an existing Linked-Mode group or another instance and click Next.
      4. Type the server name and LDAP port information and click Next.
      5. Click Finish.
      6. Click Continue and follow the installation prompts.

    3. Log in to one of the vCenter Servers and verify that the servers are linked together.

    4. After the vCenter Servers are linked, turn on UAC.
      1. Select Start > Settings > Control Panel > User Accounts.
      2. Select Turn User Account control on or off.
      3. Select User Account Control (UAC) to help protect your computer and click OK.
      4. Restart the machine.
  •  Datastore performance chart shows incorrect data
    If you open the Performance tab from the the vSphere Client Datastore inventory view, the tab shows four graphs. The titles of these graphs are not correct and should read as follows:

    • Max Latency per Host
    • Max Queue Depth per Host
    • Number of Reads per Host
    • Number of Writes per Host

    In some cases the graphs might not show all the hosts, which is a known problem.

    Workaround: To view the correct information for each host associated with a datastore, switch to the Host and Clusters inventory view, select the Performance tab, and look at the corresponding counter.

  • Upgrading vCenter Server that is running with Oracle 10g or Oracle 11g database might cause the vCenter Server to stop responding


    If vCenter Server that is running with Oracle 10g database or Oracle 11g database (version 10.2.0.4 to 11.2.01), is upgraded to vCenter Server 4.1 or later, vCenter Server stops responding with an error message similar to the following:
    Got exception: Arithmetic operation resulted in an overflow.
    This issue is caused by Oracle ODBC client bug 9793452.

    Workaround: None. To fix the issue, upgrade Oracle client. Contact Oracle support to acquire the patch.
  • vCenter Service Status displays error citing exception in locale detection
    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 appears 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.
  • Connecting vSphere Client 4.0 or 4.1 to a Linked Mode vCenter Server fails and results in an error message
    If you put three or more vCenter Servers with mixed versions, such as 4.0 update with 4.1, into a Linked Mode group, then connecting vSphere Client 4.0 or 4.1 to the vCenter Server might fail. The following error message appears in vSphere Client:
    There are issues communicating with the following vCenter Server(s) xyz.servername.com: Failure to authenticate with the server

    Workaround: Use vSphere Client 4.1 Update 2 to connect to a vCenter Server 4.1 Update 2 system that is a part of the Linked Mode group to view and manage the inventories of all the vCenter Server systems that are linked.

Virtual Machine Management

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

    If you have completed the migration of the virtual machine, you might see the following error message when you attempt to power on the virtual machine:
    File was not found

    Workaround: See KB 1020709.

VMotion and Storage VMotion

  • Virtual machine directory is not removed from the destination datastore when the advanced storage vMotion task is cancelled
    When you choose to migrate the hard disk file of a virtual machine to another datastore by using the advanced storage vMotion option and cancel the storage vMotion task before it is complete, the virtual machine directory remains on the destination datastore. The next time you choose to migrate the virtual machine's storage to the datastore, another directory with the virtual machine's name suffixed by _1 is created on the destination datastore.

    Workaround: None

VMware High Availability and Fault Tolerance

  • Custom VM Monitoring Settings are applied incorrectly to virtual machines if you sort the VirtualMachine column by clicking the heading
    If VM Monitoring is enabled on a VMware HA cluster and custom VM Monitoring settings are applied to the virtual machines, the virtual machines might not be assigned the values set for them if the Virtual Machine column is sorted.

    Workaround: Do not sort the VirtualMachine column before applying the custom VM monitoring settings.