VMware

VMware vCenter Server 4.1 Update 1 Release Notes

VMware Infrastructure Management Installer | 10 Feb 2011 (For all locales)
vCenter Server 4.1 Update 1| 10 Feb 2011 | Build 345043
vSphere Client 4.1 Update 1 | 10 Feb 2011 | Build 345043

Last Document Update: 24 Feb 2011

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of VMware vCenter Server 4.1 Update 1 offers the following improvements:

  • Additional Guest Operating System Customization Support: vCenter Server now supports customization of the following guest operating systems:
    • Windows 7 SP1 (x32 and x64)
    • Windows Server 2008 R2 SP1 (x32 and x64)
    • RHEL 6.0 (x32 and x64)
    • RHEL5.5 (x32 and x64)

  • Additional vCenter Server Database Support: vCenter Server now supports the following databases:
    • Microsoft SQL Server 2008 R2
    • Microsoft SQL Server 2005 SP3
    • Oracle 11g Standard/Enterprise Release 2, 11.2.0.1.0 or later,  (x32 and x64)
    • IBM DB2 9.7.2 Express C (x32 and x64)
    • IBM DB2 9.7.2 Enterprise (x32 and x64)
      For more information about using IBM DB2 - 9.7.2 database with vCenter Server 4.1 Update 1, see KB 1033201.

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

Features and known issues from prior releases of vSphere 4.1, are described in the release notes for each release. To view release notes for prior releases of vSphere 4.1 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 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 1, verify that the database parameter options are set. For more information, see KB 1024449.

Upgrading or Migrating to vCenter Server 4.1 Update 1

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, and vCenter Server 4.1 to vCenter Server 4.1 Update 1.

To upgrade, first confirm that your database is supported with vCenter Server 4.1 Update 1, 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.

Plug-Ins Updates

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

Documentation

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

Internationalization

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

  • English
  • French
  • German
  • Japanese
  • Simplified Chinese

vSphere Client Locale Forcing Mode

With vSphere 4.1 Update 1, 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 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.

Licensing

  • Cannot view the licensing usage reports with the Licensing Reporting Manager
    When you access the Licensing Reporting Manager to view the licensing usage reports in vCenter Server, the vSphere Client might display an error similar to the following:
    Authentication Required

    This issue is resolved in this release.

Miscellaneous

  • vCenter Orchestrator client executable file is not available in the vSphere 4.1 installation DVD or ISO image
    In the vSphere 4.1 installation DVD or ISO image, the vCenter Orchestrator client executable file is not available along with the vCenterOrchestrator.exe file.

    This issue is resolved in this release. vCenterOrchestratorClient-4.1.1-733.exe file is available in the vpx/vco folder of the installation directory.
  • Searching for Users and Groups in a large environment when using Add Permission wizard results in error or incomplete result
    When you search for Users and Groups in the Add Permissions window in the Active Directory, the search times out in large environments.
    With this release, the user search is optimized by grouping search attributes with their associated types. You can further optimize the search behavior by switching from substring matching to prefix matching. To enable prefix matching, in the vpxd.cfg file, add the following line before the </config> closing tag:
    <ads>
        <prefixMatching>true</prefixMatching>
    </ads>
  • VMware Update Manager logs are not collected when generating vCenter Server logs
    Starting with vCenter 4.1 Update 1, if VMware Update Manager and vCenter Server are installed on the same system, VMware Update Manager logs are also collected when vCenter Server logs are generated.
    Note: If VMware Update Manager and vCenter Server are installed on separate systems, VMware Update Manager logs are not collected when vCenter Server logs are generated.
  • vCenter Server 4.1 reports redundant errors when HA and DRS are enabled
    When Admission Control in HA, and DRS are enabled on a cluster in the vCenter Server, redundant error messages similar to the following might be logged in the vpxd.log file:
    [2010-10-09 19:25:14.200 04076 error 'App' opID=task-internal-1-30aac6d9-a2] [VpxdDrmInterface] Vm id -2147282016 not found.
    [2010-10-09 19:25:14.200 04076 error 'App' opID=task-internal-1-30aac6d9-a2] [VpxdDrmInterface] Vm id -2147282015 not found.


    This issue is resolved in this release.

Security

  • Updates the OpenSSL package to OpenSSL 0.9.8n
    This release of vCenter Server updates the OpenSSL package to OpenSSL 0.9.8n, which fixes multiple security issues.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2010-0740 and CVE-2010-0433 to the issues.
  • vCenter Tomcat Management Application Credential Disclosure
    The configuration file for Tomcat Manager application contains log on credentials that can be read by unprivileged local users. The issue is resolved by no longer installing the Manager application in vCenter 4.1 Update 1.
    In case vCenter is updated to vCenter 4.1 Update 1 from vCenter 4.1, the logon credentials are no longer present in the configuration file after the update.
    The Common Vulnerabilities and Exposures Project (cve.mitre.org) has assigned the name CVE-2010-2928 to this issue.
  • Updates to the Microsoft SQL Server 2005 Express Edition package
    The Microsoft SQL Server 2005 Express Edition package distributed with VMware vCenter Server 4.1 Update 1 is updated from Microsoft SQL Server 2005 Express Edition Service Pack 2 to Microsoft SQL Server 2005 Express Edition Service Pack 3, to address multiple security issues that exist in the earlier releases of Microsoft SQL Server 2005 Express Edition.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2008-5416, CVE-2008-0085, CVE-2008-0086, CVE-2008-0107, and CVE-2008-0106 to the issues addressed in Microsoft SQL Server 2005 Express Edition Service Pack 3.

Server Configuration

  • 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. Furthermore, after you apply the host profile to a host, the vSphere Client does not report the configuration changes that you make in Advanced configuration option, which incorrectly implies that no changes can be applied to the host.

    This issue is resolved in this release. However, when you upgrade vCenter Server, you must perform either of the following workarounds to make use of the fix for your existing host profiles:
    • Update existing profiles from their reference host by right-clicking the profile and selecting Update Profile From Reference Host.
    • Export host profiles out of vCenter Server, then import them back into vCenter Server.
      Use imported profiles for host profile functionality. Note that imported profiles do not have an association with any host, including the reference host. Therefore, you must re-establish the association.

    New profiles created using vCenter Server work properly without the above workarounds.

  • Alarms for the compliance or non-compliance of ESX host profiles are not triggered
    A custom alarm created in vCenter Server to monitor a host profile's compliance or non-compliance for ESX hosts is never triggered.

    This issue is resolved in this release.

Storage

  • Multipathing status for datastores that have fully redundant paths might be reported as having Partial/No Redundancy
    In the Storage View tab of vSphere Client, under certain conditions, volumes that are reported as Partial/No Redundancy actually have fully redundant paths. This type of misreporting occurs on iSCSI volumes with hardware initiators.

    As for software iSCSI initiators, the system cannot report full redundancy even if two software iSCSI initiators with multipathing exist, because physical redundancy is not available at the initiator level.

    This issue is resolved in this release.
  •  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

    This issue is resolved in this release.

Upgrade and Installation

  • Agent Pre-upgrade Check tool is unable to detect 64-bit ODBC DSNs
    When you run the Agent Pre-upgrade Check tool, the Agent Pre-check wizard does not detect the 64-bit ODBC DSNs that it can connect to.

    This issue is resolved in this release. The Agent Pre-check wizard detects both 32-bit and 64-bit ODBC DSNs.
  • vCenter 4.1 Data Migration Tool might fail to back up or restore a database
    Because vCenter Server 4.1 is supported only on 64-bit operating systems, the Data Migration Tool has been introduced to migrate data from 32-bit operating systems to a 64-bit operating systems. However, an issue occurs in the way the Data Migration Tool handles very specific information.

    This issue is related to registry keys, specifically the DbServerType registry key and the DbInstanceName registry key. The DbServerType registry key refers to the database type, Bundled or Custom, while DbInstanceName refers to the name of the database instance. This issue is specific to bundled databases and occurs when you install a fresh vCenter Server 4.0.x instance with a bundled database. As an example of such a situation, the registry key entries are as follows:

    DbServerType = Bundled
    DbInstanceName = SQLEXP_VIM


    When you perform a minor upgrade, for example from vCenter Server 4.0.x to vCenter Server 4.0.y, the registry keys change to the following:

    DbServerType = Custom
    DbInstanceName = Null


    Next, when you migrate the data to vCenter Server 4.1 using the Data Migration Tool, the operation fails because the instance name is Null and data is not completely migrated. The Data Migration Tool operates as if it is migrating custom data when in fact the data is bundled.

    This issue is resolved in this release. In this type of situation, the Data Migration Tool now interprets the data as bundled data and properly identifies the database instance name.
  • Using the Data Migration Tool to upgrade from VirtualCenter 2.5 Update 6 to vCenter Server 4.1 causes Mulitpathing Status to display blank
    After upgrading, when you log in to vCenter Server, Multipathing Status on the Storage Views tab is blank.

    This issue is resolved in this release.
  • After an upgrade to vCenter Server 4.1, vCenter Server fails to start and issues an error message

    When this issue occurs, the following error message is logged in the vpxd.log file:

    Failed to initialize: Not initialized: boolean storageIORMSupported

    This issue is resolved in this release.
  • Agent Pre-Upgrade check tool consistently reports insufficient disk space for ESXi 3.x hosts
    If your vCenter Server environment includes ESXi 3.x hosts and you run the the Agent Pre-upgrade Check tool to ensure that the hosts meet the prerequisites for upgrade, VMware AgentUpgrade Checker reports the following errors even when the / directory has enough disk space for vpxa installation:
    Insufficient Available Memory
    The ESXi host doesn't have enough available memory to install vCenter agent(s).
    For details please visit: http://kb.vmware.com/kb/1016262


    This issue is resolved in this release.
  • Upgrading a vCenter Server instance that is deployed with Microsoft SQL Server 2005 database might cause the transaction log file size to consume large amounts of disk storage space
    When you upgrade vCenter Server that is deployed with Microsoft SQL Server 2005 database to vCenter Server 4.1, the recovery model for Microsoft SQL Server 2005 is set to Bulk-Logged, irrespective of the user-defined setting before the upgrade. This change in the recovery model setting might cause an unexpected increase in transaction log file size and vCenter Server consumes large amounts of disk storage space.

    This issue is resolved in this release.
  • Upgrading to vCenter 4.1 might fail when you use the Do not overwrite existing Database option during vCenter Server installation
    When you upgrade to vCenter Server 4.1 or re-install vCenter Server 4.1 with an existing database and use the Do not overwrite existing Database option, vCenter Server might fail to recover LDAP data from the existing database and the installation fails with an error similar to the following:
    Setup cannot create vCenter Server Directory Services instance.

    This issue is resolved in this release.
  • vCenter Server stops responding when alarm modules fail to perform correctly during database recovery
    Alarm modules might fail to perform correctly during database recovery, and causes vCenter Server to stop responding with error messages similar to the following in the vpxd log files:
    Violation of PRIMARY KEY constraint 'PK_VPX_ALARM_REFRESH'. Cannot insert duplicate key in object 'dbo.VPX_ALARM_REFRESH'.

    This issue is resolved in this release.

vCenter Server, vSphere Client, and vSphere Web Access

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

    This issue is resolved in this release.
  • Performance chart data for networking displays incorrect information
    The stacked per-virtual-machine performance chart data for networking display incorrect information.You can access the chart from Chart Options in the Advanced Settings on the Performance tab. The network transmit and receive statistics of a virtual machine connected to the Distributed Virtual Switch (DVS) are reversed and incorrectly displayed in earlier releases. The fix ensures that the correct statistics are collected and passed on to the performance charts UI.
  • The locale subsystem repeatedly issues a warning message to the vpxd.log file when the correct localized string cannot be found
    Warning messages similar to the following are continuously written to the vpxd.log file:

    [2010-11-04 13:22:46.253 02620 warning 'Locale'] Resource module 'alarm' not found. Using from default locale...
    [2010-11-04 13:22:46.253 02620 warning 'Locale'] Resource module 'enum' not found. Using from default locale...
    [2010-11-04 13:22:46.253 03876 warning 'Locale'] Resource module 'vm' not found. Using from default locale...
    [2010-11-04 13:22:48.269 02620 warning 'Locale'] Resource module 'perf' not found. Using from default locale...

    This repetitive issuance of warning messages occurs when the locale subsystem fails to find a matching localized string for a catalog message lookup and therefore uses the default locale.

    This issue is resolved in this release. Now, the warning message is issued at the first occurrence only.
  • In vSphere Client, the percentage values displayed for memory usage counters of cluster entities are incorrect
    On the Performance tab of vSphere Client, a graph displays memory usage counters (for example, Average, Minimum, and Maximum). For cluster entities, the percentage values displayed for these memory usage counters are incorrect.
    Translation logic is missing for converting the metric value from kilobytes (KB) to bytes (B). The result is that the same metric unit is not used for the numerator and denominator when calculating the memory usage counters in percentage units at the cluster-entity level.

    This issue is resolved in this release.
  • When vCenter Server Linked Mode is configured and you log in using a domain account, hardware statuses of hosts are not displayed
    This issue occurs in Linked Mode when you log in using a domain account (without using Windows session credentials). When you use vSphere Client in such a situation, clicking the Hardware Status tab of the host works the first time only.
    However, clicking the Hardware Status tab for a host on a different vCenter Server instance results in the following error:
    An error occurred, please try again in another vSphere session
    Thereafter, clicking the Hardware Status tab on any host results in the same error.

    This issue is resolved in this release.
  • Storage Monitoring Service synchronization fails when the data source name of the vCenter Server host ends with a space
    The Storage Monitoring Service cache periodically synchronizes its data with the database that provides the storage information (the vCenter Server database). However, the synchronization process fails if the last character of the data source name (DSN) is a space.

    This issue is resolved in this release.
  • Search functionality might not display results if you use vSphere Client 4.1 to access vCenter Server 4.0
    If you use vSphere Client 4.1 to connect to a vCenter Server 4.0 system that is using vCenter Linked Mode, and you then perform a search function, the search results might not appear and might seem that the search function does not complete.

    This issue is resolved in this release.
  • A missing database index causes performance problems in vCenter Server
    When you use Oracle or IBM DB2 database, a missing index in the vCenter Server database might cause the vCenter Server to slow down.

    This issue is resolved in this release.
  • Using Remote Desktop Connections causes vSphere Client to fail on subsequent logins
    The first user login to vSphere Client using Remote Desktop Connections is successful. However, when another user logs in to vSphere Client from a second Remote Desktop Connection, vSphere Client fails in the second session. vSphere Client reports an error in two ways:
    • The following error appears in a dialog box:

      VMware Infrastructure Client unrecoverable error:(app)

    • The following message is written to the vSphere Client logs:

      system.Runtime.Remoting.RemotingException: Failed to create an IPC Port: Access is denied

    This issue is resolved in this release.

  • Messages for Datastore usage on disk or Datastore Disk Overallocation alarms display metrics in kilobytes instead of percent
    The text in SNMP traps or email messages for Datastore usage on disk or Datastore Disk Overallocation alarms is inaccurate. The message displays the disk usage value in kilobytes when the value correlates to disk usage in percent.

    This issue is resolved in this release.
  • Attempts to use vSphere Client to set the memory size in MB for a virtual machine that supports hot-addition fail
    When you use vSphere Client to change the memory size for a virtual machine that supports hot add, the new value can only be larger than the old value. An aspect of this issue is that attempts to change the units to MB fail.
  • 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

    This issue is resolved in this release.
  • vCenter Server might fail when Distributed Power Management tries to put a host into standby mode
    When this issue occurs, a message similar to the following is logged in the vpxd.log file:
    ASSERT d:/build/ob/bora-258902/bora/vpx/drm/vpxDrmAction.cpp:1247


    This issue is resolved in this release.
  • Replacing SSL certificates in vCenter Server with custom certificates generated using OpenSSL 1.0.0 or later causes Storage Monitoring Service to fail

    For this issue, the following error is recorded in the sms.log files:
    Error constructing private key

    This issue is resolved in this release.
  • Storage Monitoring Service synchronizations are erroneously sent as health status changed alarms
    Storage Monitoring Service synchronizes its data every 30 minutes. When a synchronization occurs, the health status of Storage Monitoring Service changes to yellow. This synchronization operation is reported as a warning, which is not the intended behavior. These false warnings are delivered using the action that is set for the health status changed alarm. Therefore, the alarm can cause commands to run, or cause warnings to be sent as notification emails or SNMP notification traps.

    This issue is resolved in this release. Warnings are no longer sent for this synchronization operation.
  • Virtual disk provisioning with scheduled Storage vMotion task fails
    When you perform a Storage vMotion operation using a scheduled Storage vMotion task, virtual-machine-disk provisioning from thick to thin format or vice versa might fail.

    This issue is resolved in this release.
  • When vSphere Client 4.0 and 4.1 coexist on the same machine, modification of existing Enhanced vMotion Compatibility clusters by using vSphere Client 4.0 fails
    Modifying an Enhanced vMotion Compatibility (EVC) cluster causes a dialog box to appear with the following error message:
    Method not found: 'Vmomi.HostSystemArray EVCState.get_BadSoftwareHostsBlockingEVC()'

    This issue is resolved in this release.
  • When vCenter Server and vCenter Converter are installed on the same or different hosts, vCenter Server Status reports inaccurate health status (Red alert) for vCenter Converter
    For this issue, vCenter Converter health status is reported inaccurately on the vCenter Service Status page of vSphere Client. Also, the VMware Web services log file (VWS.log) reports the following error message:
    Unable to retrieve health for com.vmware.converter from any of its health URLs
    This issue occurs because the vCenter Health Status service fails to retrieve health information for vCenter Converter.

    This issue is resolved in this release.
  • vCenter alarms are not triggered if another alarm on the same object is disabled
    If multiple alarms are defined on an object in vCenter Server and some of those alarms are disabled, vCenter does not trigger an alarm for that object.

    This issue is resolved in this release.
  • vCenter Server takes longer than expected to connect to a remote Oracle Database
    This issue occurs because the process for loading schema metadata is not optimized. A lot of unnecessary data is loaded during the initial connection to the remote Oracle Database.

    This issue is resolved in this release. The amount of time for the initial connection to a remote Oracle database has been reduced dramatically.
  • After an upgrade to vCenter Server 4.1, vCenter Server fails in certain environments when you click Edit Settings on a virtual machine
    If the environment has ESX/ESXi 3.5 hosts and those hosts use certain iSCSI storage devices, this issue might occur because of a bug in the vCenter Server 4.1 vpxa (also referred to as VirtualCenter Agent or vmware-vpxa service). This issue might also occur if certain paths to the storage device are indicated as dead by an ESX/ESXi host.

    This issue is resolved in this release.
  • vCenter Storage Monitoring plug-in might not get enabled if vSphere Client 4.1 is connected to vCenter Server 4.0
    If you use vSphere Client 4.1 to connect to vCenter Server 4.0, and you then enable the vCenter Storage Monitoring plug-in, the Plug-in Manager Window might display an error similar to the following:
    The plug-in failed to load on server(s) vmvc38 due to the following error:
    Could not load file or assembly 'VpxClientCommon, Version=4.1.0.0, Culture=neutral, PublicKeyToken=7c8-0a434483c7c50' or one of its dependencies. The system cannot find the file specified.


    This issue is resolved in this release.
  • Storage Monitoring Service does not start when a LUN is visible to an ESX host over multiple protocols
    Storage Monitoring Service fails to start when a LUN is visible through Fibre Channel and through iSCSI protocols.

    This issue is resolved in this release.
  • On a virtual machine running in full-screen mode, the mouse does not function properly in the lower portion of the screen
    This issue is not specific to a guest operating system or to any specific hardware. When this issue is encountered, the lower portion of the screen appears to be accessible with the mouse pointer. However, clicks do not result in any response.

    This issue is resolved in this release.
  • Deploying large number of virtual machine by using Lab Manager API scripts might cause the VMware Agent Service to stop responding
    If a large number of virtual machines are deployed at the rate of one virtual machine every one or two minutes by using Lab Manager API scripts, the VMware Agent Service stops responding after about twenty virtual machine deployments. The ESX host too stops responding. The deployment of the rest of the virtual machines might fail with the message:
    error in deploying

    This issue is resolved in this release.
  • Performance Overview charts fail to display data after change of time due to Daylight Saving
    After daylight saving time settings are applied, the Performance Overview data for the past day, week, and month might not be displayed and an error message similar to the following might be displayed:
    The chart could not be loaded
    The stats.log file displays messages similar to the following:
    [2010-11-18 10:35:15,034 http-8443-1 ERROR com.vmware.vim.stats.webui.chart.StatsChartServlet] Unable to generate performance chart image. Details: You are attempting to add an observation for t he time period Sun Oct 31 02:00:00 CET 2010 but the series already contains an observation for that time period. Duplicates are not permitted. Try using the addOrUpdate() method. org.jfree.data.general.SeriesException: You are attempting to add an observation for the time period Sun Oct 31 02:00:00 CET 2010 but the series already contains an observation for that time period. Duplicates are not permitted. Try using the addOrUpdate() method.

    This issue is resolved in this release.
  • Performance Overview data might not display after upgrading to vCenter Server 4.1
    Performance Overview data for the past day, week, and month might not be displayed after upgrading to vCenter Server 4.1.

    This issue is resolved in this release.
  • Performance data might be missing for certain intervals after upgrading to vCenter Server 4.1
    After upgrading to vCenter Server 4.1 or every time that vCenter Server restarts, multiple threads might invoke the same stored procedure to process statistics in temporary tables (VPX_TEMPTABLE[1,2,3]) at the same time causing certain operations to not complete. This might lead to failure in collection of statistics. The performance data in the performance overview charts might be missing for certain intervals.

    This issue is resolved in this release.

Virtual Machine Management

  • The default vCenter Server alarm for virtual machine total disk latency does not function on vCenter Server 4.0 and vCenter Server 4.1
    This issue is resolved in this release. This alarm is disabled on upgrade and on new installations is no longer created by default. Additionally, any custom alarms utilizing VM Total Disk Latency (ms) are disabled after an upgrade. The new trigger now available is VM Max Total Disk latency (ms). For more information, see KB 1025176.
  • Reconfiguring a virtual machine after adding a virtual hard disk might cause vCenter Server to stop responding
    For this issue, vCenter Server stops responding when the vCenter Server daemon (vpxd.exe) stops unexpectedly as observed by a variety of errors listed in the vpxd.log file. This problem has been observed in vSphere Client when both a virtual hard disk and a configuration parameter are added to the same wizard while reconfiguring the virtual machine.

    This issue is resolved in this release.
  • On vCenter Server, guest heartbeat status of a powered-on virtual machine fluctuates from green to either yellow or red
    A green heartbeat status indicates that the guest operating system is responding normally, while red and yellow indicate problems with the guest operating system. A virtual machine's guest heartbeat is calculated in multiple locations. These calculations might be negatively affected by timing issues, which result in an inaccurate guest heartbeat status.

    This issue is resolved in this release. Aspects of the timing issues that cause this condition were fixed in vSphere 4.1. This release resolves the remaining faulty calculations.

VMware High Availability and Fault Tolerance

  • When configuring high availability (HA) on a cluster, an error appears and HA does not configure on ESXi 4.0 and later hosts
    With vCenter Server 4.1, the memory pool reservation for VMware High Availability (HA) on an ESXi host is increased when HA is being enabled or reconfigured. If you modify any of the system resource allocations before the upgrade, then the configuration operation might fail and the following error appears in the status bar:
    A general system error occurred: Invalid fault

    Furthermore, when this issue occurs, the following string is logged in the vpxd.log file:
    vim.fault.InsufficientMemoryResourcesFault

    This issue is resolved in this release. The fix sets the initial VIM memory allocation to unlimited, ensuring the availability of the necessary amount of memory for the new VMware High Availability cluster memory setting.

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 1. Known issues not previously documented are marked with the * symbol.

The known issues are grouped as follows:

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.

    Workaround: Edit he configuration file of the source virtual machine:
    1.Power off the virtual machine.
    2.Right-click the virtual machine and select Edit Settings.
    3.In the Options tab, select General and click Configuration Parameters.
    4.For the disk.EnableUUID parameter, set the value as false.
    5.Power on the virtual machine
    6.Clone and customize the virtual machine using the customization wizard.

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.

Miscellaneous

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

Supported Hardware

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

Upgrade and Installation

  • 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 1 with IBM DB2 9.7.2 Express C database might fail *
    When installing vCenter Server 4.1 Update 1 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

  • 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


    Workaround: vCenter Server recovers by itself after failing because all the clusters receive a consistent view of the system up time after vCenter Server restarts. However, to prevent vCenter Server from failing in this manner, enable or create all DRS clusters either before or after the counter resets, but do not create some clusters before and some clusters after the counter is reset.
  • 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.

  • The Datastore usage on disk alarm might not be triggered after vCenter Server is restarted *
    The Datastore usage on disk alarm or an alarm that uses the Datastore Disk Usage (%) trigger type might not be triggered if vCenter Server is restarted.

    Workaround: Edit the alarms making trivial changes such as changing the alarm description, everytime vCenter Server is restarted.
  •  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 loading performance chart data when vCenter Server uses a custom SQL Server database configured with a custom JDBC port
    If a custom SQL Server instance is installed with vCenter Server and configured to use a custom JDBC port, the system displays the error Perf Charts service experienced an internal error instead of chart data.

    Workaround:

    1. On the vCenter Server system, navigate to C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter.
    2. Open the vcdb.properties file.
    3. Comment out the string usevcdb = true.
    4. Ensure that the values for url, driver, and dbtype are as follows:
      url = jdbc:sqlserver:// : ;integratedSecurity=true
      driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
      dbtype = mssql
    5. Set the integratedSecurity parameter to true if the database resides on the local machine, or to false if the database is remote.
    6. Restart the VMware VirtualCenter Management WebServices service.

    Note: This problem does not occur with Oracle or DB2 databases that are configured with custom JDBC ports.

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

  • Performance charts displays only the past day's data when viewing past week, month, and year charts (KB 1032755) *
  • 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 1 to connect to a vCenter Server 4.1 Update 1 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.