VMware

VMware vCenter Server 5.0 Update 1 (for Windows) Release Notes

vCenter Server 5.0 Update 1 | 15 March 2012 | Build 623373

vSphere Client 5.0 Update 1 | 15 March 2012 | Build 623373

vCenter Server 5.0 Update 1 Installation Package | 15 March 2012 | Build 639890

Note: vCenter Server Appliance 5.0 Update 1 will be available later this year.

Last updated: 13 March 2014

Check for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

What's New

The VMware vCenter Server 5.0 Update 1 (for Windows) delivers a number of bug fixes that have been documented in the Resolved Issues section.

Internationalization

VMware vSphere 5.0 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese

vSphere Client Locale Forcing Mode

With vSphere 5.0, you can configure the VMware vSphere Client™ to provide the interface text in English even when the machine on which it is running is not English. You can set this configuration 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 and time or numeric formatting.

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

Features added in this release

  • vCenter Essentials is incorporated with hard enforce vRAM limits
    In vSphere Essential edition, a hard enforcement is added to limit vRAM usage (192GB). Once the limit is met, additional operations (such as powerOnVM) that lead to license over usage will be prevented. This enforcement is only added to Essential editions, other editions do not have this.

  • vCenter now enforces restrictions on which vSphere editions can be managed by vCenter
    With this feature, vCenter Standard and Foundation is disallowed from managing vSphere Essentials and Essentials Plus host editions. This is disallowed per the EULA already, but was not programmatically enforced until now. The exception to this rule is the ‘Essentials for ROBO’ edition. This is still allowed per the EULA and as per the programmatic enforcement. Furthermore, it is also enforced that vCenter Essentials can only manage Essentials and Essentials Plus hosts.

  • License use reporting does not cap per-VM vRAM consumption reporting at 96GB per VM
    When viewing vSphere 5.0 vRAM usage reporting, VMs configured to use greater than 96GB of configured RAM reported the full configured RAM value, regardless of the vRAM license policy which states that greater than 96GB per VM usage is not counted against your vRAM entitlement.

  • Support for Database Pre-Upgrade Checker 1.0
    Before you upgrade vCenter Server, you can run the VMware vCenter Database Pre-Upgrade Checker on your current vCenter Server database to reveal problems that could prevent the upgrade. You can use the Pre-Upgrade Checker for the following upgrades:

    • On a vCenter Server 2.5 Update 6 or later database before you upgrade to vCenter Server 4.x
    • On a vCenter Server 4.0.x database before you upgrade to vCenter Server 4.1 or 5.0
    • On a vCenter Server 4.1.x database before you upgrade to vCenter Server 5.0

Compatibility and Installation

ESXi, vCenter Server, and vSphere Client Version Compatibility

The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, VMware vCenter Server, the vSphere Client, and optional VMware products. In addition, this site provides information about supported management and backup agents before installing ESXi or vCenter Server.

The vSphere Web Client and the vSphere Client are packaged with the vCenter Server and modules ZIP file. You can install one or both clients from the VMware vCenter Installer wizard.

Inventory Service Database

The Inventory Service database does not have a scheduled backup. You should back up the Inventory Service database as part of your regular vCenter Server database administration. To move the Inventory Service database to a different host machine, back up the database on the source machine and restore the database on the destination machine as described in the vSphere Installation and Setup documentation.

Guest Operating System Customization Support

The Guest OS Customization Support Matrix provides details about the guest operating systems supported for customization.

vSphere Client Connections to Linked Mode Environments

vCenter Server 5.0 can exist in Linked Mode only with other instances of vCenter Server 5.0. Linked Mode groups that contain both vCenter Server 5.0 and earlier versions of vCenter Server (such as vCenter Server 4.0 and vCenter Server 4.1) are not supported. In this release, you can manage Linked Mode groups that contain both vCenter Server 5.0 and vCenter Server 5.0 Update 1 instances.

vSphere 5.0 and VMware View Compatibility

To learn about vSphere configurations supported with VMware View, see the VMware Product Interoperability Matrix.

Installation Notes for This Release

Read the vSphere Installation and Setup documentation for step-by-step guidance on installing and configuring ESXi and vCenter Server.

After successful installation, you must perform some licensing, networking, and security configuration. For information about these configuration tasks, see the following guides in the vSphere documentation.

vCenter Server 5.0 supports installation on Windows 64-bit platforms only. You can upgrade from vCenter Server 4.1 to vCenter Server 5.0 on the same system if it is 64 bit. If you have VMware vCenter Server 2.5 or vCenter Server 4.0 on 32-bit systems installed, see the vSphere Upgrade documentation for instructions on installing vCenter Server on a 64-bit operating system and preserving your vCenter Server database.

vCenter Server 5.0 includes Management Information Base (MIB) files related to vCenter Server. You can download MIB files related to ESXi from the VMware Web site at http://www.vmware.com/download/vsphere/drivers_tools.html.

Upgrades for This Release

For instructions about how to upgrade vCenter Server and ESXi hosts, see the vSphere Upgrade documentation.

vSphere 5.0 supports the following upgrade scenarios:

  • You can perform in-place upgrades on 64-bit systems from vCenter Server 4.x to vCenter Server 5.0.
    You cannot upgrade an instance of vCenter Server 4.0.x that is running on Windows XP Professional x64 Edition.
  • You can upgrade vCenter Server 2.5 Update 6 or later and vCenter Server 4.x to vCenter Server 5.0 by installing vCenter Server 5.0 on a new 64-bit operating system and migrating the existing database.
    This upgrade method makes an upgrade from a 32-bit system to a 64-bit system possible.
  • vCenter Server 5.0 can manage ESXi 5.0 hosts in the same cluster with ESX/ESXi 4.x and ESX/ESXi 3.5 hosts. It can also manage ESX/ESXi 3.5 hosts in the same cluster with ESX/ESXi 4.x hosts. vCenter Server 5.0 cannot manage ESX 2.x or 3.0.x hosts.

Test Releases of vSphere 5.0

Upgrades from the vCenter Server 5.0 Update 1 Release Candidate release to vCenter Server 5.0 Update 1 is not supported. Uninstall vCenter Server 5.0 Update 1 Release Candidate, and perform fresh installations of vCenter Server 5.0 Update 1. If you were testing Release Candidate versions of vCenter Server 5.0 Update 1, VMware recommends that you recreate data you want to preserve from those setups on vCenter Server 5.0 Update 1.

Open Source Components for VMware vSphere

The copyright statements and licenses applicable to the open source software components distributed in vSphere 5.0 are available at http://www.vmware.com/download/vsphere/open_source.html, on the Open Source tab. You can also download the source files for any GPL, 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.

Product Support Notices

VMware vSphere 5.0 is the last release for the following management features and platforms. VMware continues to provide technical support for these features and platforms through the end of their support lifecycles.

  • VMware Toolbox: vSphere 5.0 is the last release to include support for the VMware Tools graphical user interface, VMware Toolbox. VMware will continue to update and support the Toolbox command-line interface (CLI) to perform all VMware Tools functions.

  • VMI Paravirtualization: vSphere 4.1 was the last release to support the VMI guest operating system paravirtualization interface. For information about migrating virtual machines that are enabled for VMI so that they can run on later vSphere releases, see Knowledge Base article 1013842.

  • VMCI Sockets: vSphere 5.0 is the last major release to support using Virtual Machine Communication Interface (VMCI) sockets to communicate between virtual machines. Use of VMCI sockets to communicate between ESXi and virtual machines continues to be supported.

  • Prebuilt modules for Unsupported Linux Guests: vSphere 5.0 is the last release to ship prebuilt modules (PBMs) for unsupported Linux guest operating systems. To use an unsupported Linux guest, you must compile Linux kernel modules from source code during VMware Tools installation.

  • Tape drives: VMware does not support tape drives that are connected to ESX/ESXi hosts. For additional information, see Knowledge Base article 1016407.

  • vSphere 5.0 and its subsequent update and patch releases are the last vSphere versions to support VMware ESX/ESXi 3.5 and VMware Virtual Center 2.5: Future versions of vSphere, which includes VMware ESXi, VMware vCenter Server, VMware vSphere Client and VMware vCenter extensions and plug-ins, such as vCenter Update Manager, will not operate with VMware ESX/ESXi 3.5 or VMware Virtual Center 2.5. VMware ESX/ESXi 3.5 and VMware Virtual Center 2.5 will continue to be supported until their originally published end-of-support dates.

Resolved Issues

This release resolves issues in the following subject areas.

Upgrade and Installation

  • Configuring HA after upgrading to vCenter Server 5.0 fails with errors when using the default self-signed SSL certificates
    When you upgrade vCenter Server to 5.0, you cannot complete the configuration of the vSphere HA agent on the host and the configuration fails with following error messages.
    Cannot complete the configuration of the vSphere HA agent on the host.
    Misconfiguration in the host setup
    Operation timed out.
    This can occur when you use the default self-signed SSL certificates.
    This issue is resolved in this release.

  • vSphere Web Client fails to start after Web Client installation is complete
    In vCenter Server, vSphere Web Client might fail to start after Web Client installation is complete.
    This issue is resolved in this release.

  • Upgrade to vCenter Server 5.0 fails with the error
    After you upgrade a vCenter Server 4.1 instance to vCenter Server 5.0, vCenter Server does not start, and produces a win32 exception error and backtrace.
    When this issue occurs, the following error message is written to vpxd logs.
    Found both stateful stateless event expressions in the same alarm
    This issue is resolved in this release.

  • vCenter Server 5.0 U1 is shipped with Microsoft SQL Server 2008 R2 SP1 Express database
    When upgrading vCenter Server 5.0 GA (installed with Microsoft SQL Server 2008 R2 Express database) to vCenter Server 5.0 U1 , Microsoft SQL Server 2008 R2 Express database is upgraded to Microsoft SQL Server 2008 R2 SP1 express database.
    Note: A restart is required when a vCenter Server is upgraded to vCenter Server 5.0 U1.
    This issue is resolved in this release.

Storage Issues

  • tempdb might grow excessively in size when vCenter Server 5.0 is running with SQL Server in a large SAN environment
    When you are running vCenter Server 5.0 in a large SAN environment with many volumes/luns and adapters, the VMware Virtual Center Management webservices starts and 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.
    This issue is resolved in this release.

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

  • When you use storage providers, the vCenter Server might not display some of the system-defined storage capabilities provided by a storage system
    This issue might occur when a label or description of a capability communicated by a storage provider component contains symbols not supported by the vCenter Server. This issue might also occur if the amount of capability information exceeds the currently imposed limit.
    This issue is resolved in this release.

Server Configuration

  • Storage Profile Driven (SPS) services is unable to handle NFS and VMFS datastores storage capability
    In vCenter Server, Storage Profile Driven (SPS) services is unable to handle the scenario when a storage capability is associated with NFS and VMFS datastores.
    This issue is resolved in this release.

  • HA and DRS appear disabled when VM Storage profiles feature is enabled or disabled for a cluster
    When virtual machine storage profiles feature is enabled or disabled for a cluster, it causes a discrepancy in HA and DRS cluster configuration.
    This issue is resolved in this release.

  • Host Profiles reports error: Hosts do not have shared datastores
    Clicking on the vCenter 5.0 profile compliance tab for a HA/DRS cluster (that consists of only ESX or ESXi 4.x hosts ), the cluster appears as non-compliant with the following error message
    Hosts do not have shared datastores
    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.

vCenter Server and vSphere Client Issues

  • SMS logs might show Read time out exceptions, when the VASA provider supports very large inventory
    In vCenter Server, SMS logs might show Read time out exceptions, when the VASA provider supports huge inventory and SMS might be unable to sync the data from the provider, because certain VASA API calls take a long time to complete for a huge inventory and timeout happens.
    This issue is resolved in this release by increasing the timeout value for vasa axis2 client to 15 minutes.

  • InvalidArgument exception is seen in the SMS log when the VASA provider is restarted
    In vCenter Server, when the VASA provider is restarted, the variables latestEventID and latestAlarmId are reset to -1. However SMS continues to call with the same lastReturnedEventId and lastReturnedAlarmId. This might cause invalidArgument exception in the VASA provider. As a result SMS does not get any further events or alarms from the VASA provider.
    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 host
    The vpxd.log files might contain entries similar to the following:
    [VpxdMoHost::CollectRemote] Attempt to collect stats on
    [VpxdMoHost::CollectRemote] Not collecting stats this time on host because collection pending Had to drop performance data coming from host because it has error (The specified network name is no longer available).
    This issue is resolved in this release.

  • vCenter Server fails when querying disk or datastore counters
    When querying a disk or datastore counter, the vCenter server might fail if the value returned is larger than 32-bit.
    This issue is resolved in this release.

  • SMS (Storage Management Service) fails to load providers that report more than one supportedVendorModel combinations
    As per the VASA specification ( vSphere Storage APIs - Storage Awareness ) and SMS VMODL, supportedVendorModelMapping is an array where each entry contains vendorId and modelId property.Currently if the provider reports more than one vendorId/modelId combinations, all of those are getting persisted within a single supportedVendorModelMapping tag instead of putting each combination under a separate supportedVendorModelMapping tag in the document. This leads to deserialization failure for VendorProviderInfo document and provider cannot get loaded by SMS.
    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 becomes 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.

  • Hosts randomly disconnect from vCenter server but immediately reconnect itself to vCenter Server
    If the system time is set forward by more than one minute on the vCenter server, for example, due to adjustment by the time sync software installed on the vCenter server machine, hosts may appear disconnected from vCenter server for a very short period of time, but the hosts will immediately reconnect itself back to vCenter server.
    This issue is resolved in this release.

  • Adding an ESX/ESXi 4.1 host task in VMware vCenter Server 5.0.x fails with an internal error
    When you add an ESX/ESXi 4.1 host task in VMware vCenter Server 5.0.x it fails with the error message similar to following.
    Alert:false@ d:/build/ob/bora-455964/bora/vim/lib/vdb/vdb.cpp:3253
    This issue is resolved in this release.

  • Virtual Machines are displayed even if the view option is unchecked
    When connected to vCenter Server in the Host and Clusters view, if you select View from the menu bar, the menu includes a selected option to display the virtual machines. If you deselect this option and leave the Host and Clusters view and then return to it, the virtual machines are displayed again, and the Show virtual machines in Inventory option remains selected.
    This issue is resolved in this release.

  • vCenter Server might fail to add ESX hosts with SSL certificates, an error message is logged in vpxa.log
    If an SSL certificate (rui.crt) with DOS style CRLF line terminators is installed on an ESX, vpxa fails to load it. With this issue the following error message is logged in vpxa.log :
    Failed: unrecognized file format: /etc/vmware/ssl/rui.crt.
    This issue is resolved in this release.

  • vCenter Server fails to display accurate memory usage
    In vCenter Server, the MB column in host memory is limited to five digits, because of this limit, if the memory usage goes over five digits, only the first five digits are displayed and as a result, vCenter Server might fail to display the accurate memory usage.
    This issue is resolved in this release.

  • Host Profile compliance check might fail on 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 NICs are down, 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.

  • 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-455964/bora/vpx/public\vpxDrmStats.h:732
    This issue is resolved in this release.

  • In vCenter Server the VPX_TASK table contains entries older than the VC database retention policy
    After changing the database retention policy in vCenter Server, you might see that the VPX_TASK table entries older than [x] days are still retained. This might cause undesired growth of the VPX_TASK table inside the vCenter Server database.
    For more information, see KB 2005293.
    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 displays multiple windows with the error: A internal error occurred in the vSphere Client. Details: Object reference not set to an instance of an object
    When vSphere Client is connected to vCenter Server, several windows might appear displaying an error message: A internal error occurred in the vSphere Client. Details: Object reference not set to an instance of an object
    The viclient.log file contains error messages similar to the following:
    System.NullReferenceException: Object reference not set to an instance of an object.
    at VpxClient.VMList.UpdateCPUAndMemUsageForViewableItems()
    at VirtualInfrastructure.Updates.PollerDispatcherImpl.NotifyUpdates(Map`2 handler2Updates)
    This issue is resolved in this release.

  • VirtualMachine.Config.Rename privilege splits into Rename and Annotation
    In vCenter Server VirtualMachine.Config.Rename privilege was required to edit the annotations for a virtual machine, this allows the user to both rename as well as edit the annotations. This fix uses the appropriate privilege VirtualMachine.Config.Annotation for editing virtual machines annotation after the Rename privilege was split into Rename and Annotation.
    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 executed for the first time or when the VMware vCenter 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 are not allowed you to set the interval value to more than 999. When using the RecurrentTaskScheduler data object through vSphere API/SDk to schedule a task, you are not allowed to 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.

  • Customization specification does not configure the gateway for Red Hat Enterprise Linux 5.
    Earlier, image customization of Red Hat Enterprise Linux 5.x virtual machines did not configure the gateway properly if a gateway was previously set in route-ethX. Consequently, if users assigned a new gateway to the RHEL 5.x virtual machine during customization, the new gateway entry is appended to the /etc/sysconfig/network-scripts/route-ethX file. The RHEL network service picks up the first entry (the old gateway setting) in that file, and does not pick up the gateway changes specified by the user during customization.
    This issue is resolved in this release.

  • Upgrade to vCenter Server 5.0, fails with an error message: Failed to execute DBUHelper.exe an error occurred in VCDatabaseUpgrade.log.
    After an upgrade to vCenter Server 5.0, vCenter Server fails to start and issues the following error message.
    Failed to execute DBUHelper.exe an error occurred, in VCDatabaseUpgrade.log.
    This issue is resolved in this release.

  • Changes made to customized advanced performance charts might not get saved
    After creating and saving a customized advanced performance chart, when you switch to another graph and return to this chart again, all the individual changes made in the customized chart including selection of multiple >objects (like VMs) might not be retained.
    This issue is resolved in 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 will 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.

  • vCenter Server takes a long time to start
    If the vCenter inventory is large, numerous ESX host syncs upon vCenter service restart. This can cause significant delay in vCenter service startup.
    This issue is resolved in this release.

  • Performance charts in the webclient fail to load completely
    When you open the performance tab in webclient, performance charts are unable to load. This issue might occur every time, the user clicks on the performance tab.
    This issue is resolved in this release.

  • Gaps are seen on the historical performance chart of several hosts in vCenter Server inventory
    In vCenter Server, historical performance data might be lost. vCenter might log the following event:
    Stats insertion failed for entity due to ODBC error
    vCenter vpxd logs show message such as Failed to get a table to insert raw stats. Performance data will be lost
    For more information, see KB 2011523.
    This issue is resolved in this release.

  • Database is inflated by performance stats that are not purged
    On vCenter Server configuration, collecting historical data such as past day, week, month, year might cause the related VPX_HIST_STAT table to fill up and not be purged correctly.
    This issue is resolved in this release.

  • Unable to retrieve health status for vCenter inventory service and vSphere Profile-Driven storage service
    When vCenter Server is uninstalled from a host, and installed on a different host, while it still uses the old vCenter database, the user is unable to retrieve health status for vCenter inventory service and vSphere Profile-Driven storage service. This issue might occur because of erroneous information in vCenter Server for inventory service.
    This issue is resolved in this release.

  • Automatic virtual machine startup and shutdown option is disabled when host is part of a HA (High Availability) cluster
    In vCenter Server the ESX host setting Allow virtual machines to start and stop automatically with the system should be disabled when the host is added to a HA cluster, as this feature is not supported with HA. The option to re-enable the setting should be greyed out when the host is in the HA cluster.
    This issue is resolved in this release.

  • Unable to power on virtual machines in a DRS enabled cluster
    When you attempt to power on virtual machines in a DRS enabled cluster vCenter Service fails.
    This issue is resolved in this release.

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

  • vCenter Server generates a security error when accessing the console of a virtual machine in Linked Mode
    When you have two (or more) vCenter Server 5.0 instances in Linked Mode with the vSphere Web Client installed on the first vCenter Server and have registered all vCenter Server instances on the Web Clients. If you log in the first vCenter Server and open the Web Client, you can see both vCenter Servers, and when you open a console to a virtual machine in the second vCenter Server, the console does not display and you see the following error:
    SSL Verification failure for "hostname" due to a host thumbprint mismatch
    An error occurred that affected the security of the connection
    You can see the console successfully through the vSphere Client. This issue only affects the Web Clients.
    This issue is resolved in this release.

  • Importing an OVA into vCenter 5.0 results in an unable to load DLL error
    The vSphere 5.0 Client fails to copy the zlib.dll into the correct directory location, which prevents OVA imports.
    This issue is resolved in this release.

  • Moving SDRS/SIOC stats from level 1 to a higher stats level mitigates the slow down caused by these stats
    In vCenter Server, having SDRS and SIOC stats at level 1 results in slower vCenter performance due to the high amount of rows being inserted into the vCenter database and then being rolled up. Moving the SDRS/SIOC stats to a higher stats level reduces the database usage significantly and hence improves vCenter performance. However, this change effectively disables the non-realtime POD and datastore performance charts.
    This issue is resolved in this release.

  • vCenter Server VM clonetask operation fails with the error: vim.fault.InvalidDeviceSpec
    In vCenter Server, a virtual machine clone operation may fail with error: vim.fault.InvalidDeviceSpec.This may occur where the VM is on Host-1 and where Host-1 and Host-2 are both on the same DVS. The issue occurs because of an erroneous calculation by vCenter on DVport reservations.
    This issue is resolved in this release.

  • Unable to open VM console in vSphere Client (5.0 and earlier) using IPv6 DNS name
    In vCenter Server (5.0 and earlier), vSphere Client users are unable to open a virtual machine console where hosts are using an IPv6 DNS name.
    This issue is resolved in this release.

  • vCenter Server does not pair NHM and WSM CPU hosts for FT in an HA enabled cluster
    In an HA enabled cluster, if the cluster has a mix and match of servers with Nehalem CPU and Westmere CPU ,FT pairing between these CPU servers will not occur. If the primary virtual machine is running on Nehalem CPU, then at any point of time its secondary virtual machine will not run on Westmere CPU host and conversely.
    This issue is resolved in this release.

  • ResetCounterLevelMapping API might throw exceptions for 187,188,193,203,138,139,245 counters
    In vCenter Server ResetCounterLevelMapping API would throw exceptions for 187,188,193,203,138,139,245 counters.
    This issue is resolved in this release.

  • ESX 4.0 hosts with certain build numbers cannot be managed by vCenter 5.0
    A purple screen of death (PSOD) may occur on hosts running ESXi 4.0 releases between Patch03 (build 219382) and Patch09 (build 360236).This occurs when the host is being managed by vCenter 5.0 in a cluster with HA enabled and VPXA agent gets reinstalled on the host e.g. if the host was removed and re-added into the vCenter inventory. With this fix, hosts are allowed to be managed by vCenter and the ESX 4.0 hosts does not PSOD.
    This issue is resolved in this release.

  • Poweroff Scheduled Tasks may occur two days earlier than planned
    In vCenter Server, while creating scheduled Poweroff tasks, when vSphere Client is running on the end of month, vCenter Server makes an incorrect calculation which causes the task to run two days earlier. For example, when the scheduled Poweroff task is set on a weekly schedule and the target day is a Sunday, the task is scheduled to run 2 days earlier, on a Friday. The problem occurs if you do not specify the AM/PM field or specify it as AM . It does not occur if you select PM.
    This issue is resolved in this release.

  • Deploying a VM from template to an HA DRS cluster fails when deployed to a HA failover host
    When the user attempts to deploy a virtual machine from the template and selects the option Power On the Virtual Machine After Creation an attempt may be made to deploy the virtual machine on the Failover Host and to power on the virtual machine, which consequently fails. However if you uncheck the Power On the Virtual Machine After Creation option, the virtual machine creation is successful and the VM may get deployed on the failover host without error, as there is no attempt to power on the virtual machine.
    This issue is resolved in this release.

  • After upgrade to vCenter Server 5.0, vMotions may fail with a general system error
    vCenter Server 5.0 vMotion might fail with an error A general system error occurred: Not initialized and Call EnvironmentBrowser.QueryConfigTarget for object envbrowser-xxx on vCenter Server xxxxxxxx failed.This issue may occur if stale entry of an inaccessible or inactive datastore on the ESX/ESXi host resides in the vCenter Server database. The inaccessible datastore may have been present before the upgrade to vCenter Server 5.0
    This issue is resolved in this release.

  • Permissions set on a datastore cluster are lost after vCenter Server is restarted
    A permission that is set directly on a datastore cluster in vCenter Server 5.0 is lost after vCenter Server is restarted, only setting the same permission at a higher level in the datastore view and having it propagate down to the datastore cluster will allow the permission to persist.
    This issue is resolved in this release.

  • vCenter service is unable to connect through vSphere Client although Service is up
    In vCenter Server, after vpxd hits an unrecoverable database error and fails . On restarting VC database it is noticed that db has corrupted (which prevents vpxd from restarting). The user can only restore it from a earlier backup.
    This issue is resolved in this release.

Virtual Machine Management Issues

  • 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 =
    13425- faultCause = (vmodl.MethodFault) null,
    13426: obj = 'vim.vm.Snapshot:snapshot-133808',
    13427- msg = "",
    Use the esxcli command to edit the SATP PSP on the host itself before you extract the host profile. Do not use the host profile editor to edit the SATP PSP.
    This issue is resolved in this release.

  • vCenter Server fails to export VM with dynamic property referring to a dvPortgroup
    vCenter Server fails to export VM with dynamic property referring to a dvPortgroup This export fails because the OVF manager erroneously exports the network name using the mo-ref of the portgroup, while using the logical name for the dynamic properties.
    This issue is resolved in this release.

  • A task scheduled to create a snapshot of a 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 you attempt to run the scheduled task.

VMware HA and Fault Tolerance Issues

  • FDM goes into an uninitialized state when a Nessus scan is run against an ESXi 5 host
    In vCenter Server, FDM goes into an uninitialized state when a Nessus security scan is run against an ESXi 5 server.
    This issue is resolved in this release.

  • File-based FDM logging can be enabled inadvertently for ESX 5.x hosts in a mixed cluster with ESX 5.x and ESX 4.x hosts.
    The default FDM logging behavior for ESX 5.x hosts is to use syslog, file-based logging is disabled. In a HA cluster with mixed of 5.x and pre-5.x hosts using DAS advanced option das.config.log.maxFileNum to increase number of log files on the pre-5.0 hosts will inadvertently enable file-based logging for ESX 5.x hosts. This can lead to ESX scratch partition to run out of space.
    This issue is resolved in this release by introducing HA cluster advanced parameter "das.config.log.outputToFiles". To enable file-based logging for ESX 5.x hosts, both "das.config.log.maxFileNum" need to configure to a value greater than 2 and "das.config.log.outputToFiles" is equal to "true".

  • During HA failover some VMs might seem invalid and unable to powered on from some particular host
    During HA failover, some VMs might seem invalid from some hosts after hostd reboot as the view of VMX file from those hosts might be reported as corrupted.
    This issue is resolved in this release.

  • HA cannot be configured when using CA-signed SSL certificates
    Earlier in vCenter 5.0, using CA-signed SSL certificates resulted in HA failing to configure on hosts with error messages such as vSphere HA cannot be configured on this host because it's SSL thumbprint has not been verified. This was because the database was unable to update the SSL thumbprint in the database.
    This issue is resolved in this release.

  • Secondary VMs will get powered off due to blocked FT ports after disabling HA
    When HA is disabled for troubleshooting or for any reason in a cluster with FT, all the secondary VMs will get powered off due to blocked FT ports. This issue occurs because the firewall disables FT port ruleset.
    This issue is resolved in this release.

  • HA configuration does not succeed for hosts in lockdown mode
    In an HA cluster, ESX hosts (with lockdown mode enabled) may display a HA agent error: vSphere HA agent for this host has an error
    If you try to configure HA manually, the following error appears:
    Cannot Install the vCenter agent service. Unknown installer error.
    This issue is resolved in this release.

  • HA fails to configure on host with general error A general system error occurred: Failed to increase memory reservation and limit for host/vim/vmvisor from -1 to xxx
    In vCenter Server, FDM does not take proper account for hosts with host/vim/visor memory resources set to unlimited (-1).It considers that all hosts have real memory limits set, and attempts to increase the host's limit by the aam-required delta and fails with this error.
    In this release HA might configure even when the host memory limit is set to unlimitedp
    This issue is resolved in this release.

Guest Operating System Issues

  • Attempts to customize a Windows virtual machine fail during the clone or deployment process
    In vCenter Server, guest customization of a Windows 2008, Windows 2008 R2, or Windows 7 virtual machine fails with error: Windows Setup encountered an internal error while loading or searching for an unattended answer file
    This issue occurs because the customization specification contains any of the following characters
    &, <, >, ", or ' in the following fields:
    Computer Name , Registered Owner Name, or Registered Organization Name field.
    This issue is resolved in this release.

Performance Charts

  • vSphere Client stops responding when you attempt to view custom performance charts
    When you view custom performance charts with a custom time range, that starts at any hour:00 minutes, the vSphere Client session connected to vCenter server stops responding and consumes 100% of the client CPU. To workaround this issue, delete the client process from the task manager and restart the client. However even then the performance chart may be unusable because it will try to load the previous configuration and stop responding.
    This issue is resolved in this release.

Licensing Issues

  • vSphere Enterprise edition does not list VAAI feature
    In vCenter Server, the vStorage APIs - Array Integration (VAAI) feature is not listed under Configuration > Licensed Features on the vSphere Client for vSphere Enterprise edition.
    This issue is resolved in this release.

Miscellaneous Issues

  • Error when attempting to connect client CD-ROM device to a VM via Passthrough IDE mode
    Attempting to connect client CD-ROM device to a VM via Passthrough IDE mode, the following error appears Failed to get the state of the lock on the CD-ROM. When the VM is powered off, the host operating system might not know about the state of the drive.
    This issue is resolved in this release.

  • Message of the day text box does not allow more than 1024 characters
    In vCenter 5.0 the Message of the day text field does not allow you to enter 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.

Localization

  • Attempt to add a host to a 5.0 or earlier vCenter results in a failure
    This issue occurs when the operating systems regional settings are changed. The Digit Grouping setting is changed, such that the number comma-separator distances are uneven. (for example: 1,23,34,5657,345).
    This issue is resolved in this release.

OVF Customization

  • Storage vMotion of a vCloud Director virtual machine fails with an error: A specified parameter was not correct
    When performing Storage vMotion of a vCloud Director (vCD) virtual machine, Storage vMotion fails and following error message is displayed. A specified parameter was not correct. This occurs when the VM settings has the VMware Tools checkbox is enabled under vApp Options - OVF Settings.
    This issue is resolved in this release.

Security

  • Using Datastore.FileManagement privilege to rename folder or file under datastore instead of Datastore.Rename privilege
    In vCenter Server, previously the Datastore.Rename permission is required for renaming files under datastore, but this permission, allowed users permission to rename the datastores themselves.However now in this release, the Datastore.FileManagement permission is needed for users to rename the files or folders present on the datastores. This permission is necessary for the users to rename the file or the folders, as well as deleting, read and write operations on files within the datastore.
    This issue is resolved in this release.

  • vCenter Client internal browser input validation vulnerability
    The vSphere Client has an internal browser that renders html pages from log file entries. This browser doesn’t properly sanitize input and may run script that is introduced into the log files. In order for the script to run, the user would need to open an individual, malicious log file entry.
    In order to remediate the issue, the vSphere Client of the vSphere 5.0 Update 1 release or the vSphere 4.1 Update 2 release needs to be installed. The vSphere Client that comes with vSphere 4.0 and vCenter Server 2.5 is not affected.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-1512 to this issue.
    This issue is resolved in this release.

  • Update to Apache Tomcat 6.0.35 addresses multiple security issues
    Apache Tomcat is updated to version 6.0.35 to address multiple security issues. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2011-3190, CVE-2011-3375, and CVE-2012-0022 to these issues.
    This issue is resolved in this release.

Known Issues

Read through all of the Known Issues to find items that apply to you. The issues are grouped as follows.

Known issues not previously documented are marked with the * symbol.

Installation Issues

  • No error message when you install vSphere Authentication Proxy, vSphere ESXi Dump Collector, and vSphere Syslog Collector support tools for vCenter Server on earlier versions of vCenter Server
    vCenter Server tools (VMware ESXi Dump Collector, VMware Syslog collector, vSphere Auto Deploy, and vSphere Authentication Proxy) are included with the vSphere 5.0 installation media. If you attempt to install one or more of these tools on a system on which an earlier version of vCenter Server is installed, the installation fails without displaying an error message.
    Workaround: None

  • vSphere Authentication Proxy, vSphere ESXi Dump Collector, and vSphere Syslog Collector support tools for vCenter Server do not support IPv6
    The host machines for Authentication Proxy, ESXi Dump Collector, and Syslog Collector must each have a valid IPv4 address. You can install these support tools on machines in IPv4-only or IPv4/IPv6 mixed-mode network environments. You cannot install the tools on machines in IPv6-only environments. The Authentication Proxy, ESXi Dump Collector, and Syslog Collector services bind to an IPv4 address for communication with vCenter Server, and do not support IPv6. The vCenter Server can be on a host machine in an IPv4-only, IPv4/IPv6 mixed-mode, or IPv6-only network environment, but the machine that connects to the vCenter Server through the vSphere Client must have an IPv4 address for the Authentication Proxy, ESXi Dump Collector, and Syslog Collector services to work.
    Workaround: None.

  • vCenter Inventory Service does not support binding on IPv6 interfaces by default
    When you install vCenter Server, vCenter Inventory Service supports only IPv4 by default.

    Workaround: To enable IPv6 support for vCenter Inventory Service, take the following steps.

    1. Stop the vCenter Inventory Service.
      1. From the Administrative Tools control panel, select Services.
      2. Right-click vCenter Inventory Service and select Stop.
    2. In a text editor, open the following file:
      Inventory_Service_installation_directory/lib/server/config/dataservice.properties
    3. Change the value for dataservice.nio.enabled to false.
    4. Restart the vCenter Inventory Service.
  • Cannot install vSphere Client in folder whose name contains special characters
    When you install the vSphere Client into a folder or directory whose name contains any of the characters semicolon (;), left square bracket ([), right square bracket (]), equals sign (=), plus sign (+), comma (,), or pound sign (#), the following error message appears:
    The installation path contains a ';' character. Please select an installation directory with this character.
    Even if the folder name does not contain a semicolon (;), you cannot install the vSphere Client into the specified folder. In addition, if you install the vSphere Client into a customized folder with a name that contains a pound character (#), the client cannot connect to vCenter Server.
    Workaround: Do not install the vSphere Client into a customized folder with a folder name that contains any of the characters semicolon (;), left square bracket ([), right square bracket (]), equals sign (=), Plus sign (+), comma (,), or pound sign (#).

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

    Workaround: Turn off User Account Control (UAC) before joining a Linked Mode group after installation, then turn it back on.

    1. Turn off UAC.
      1. From the Start menu, select Control Panel > User Accounts.
      2. Select Turn User Account control on or off.
      3. Deselect User Account Control (UAC) to help protect your computer and click OK.
      4. Reboot the machine when prompted.
    2. Start the Linked mode configuration.
      1. Select Start > All Programs > VMware > vCenter Server Linked Mode Configuration.
      2. Click Next.
      3. Select Modify Linked-Mode configuration and click Next.
      4. Select Join this vCenter Server instance to an existing Linked-Mode group or another instance, and click Next.
      5. Enter the server name and LDAP port information and click Next.
      6. Click Continue to complete the installation.
      7. Click Finish to end the linking process.
    3. Log in to one of the vCenter Server systems and verify that the servers are linked.
    4. After the vCenter Server systems are linked, turn on UAC.
      1. From the Start menu, select 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. Reboot the machine when prompted.
  • After installing the vSphere Web Client, when the user clicks Finish in the installation wizard, a browser opens and displays a blank page
    After you install the vSphere Client, a browser opens and displays a blank page when you click Finish in the installation wizard. The page remains blank and the browser does not connect to the vSphere Administration application.
    Workaround: Close the browser and launch the vSphere Administration Application page from the Start menu.

Upgrade Issues

  • Upgrading to vCenter Server 5.0 the vcdb.properties may be incorrectly changed*
    After an upgrade to vCenter Server 5.0, the database type in vcdb.properties can be changed incorrectly affects vCenter functionality.This can occur if the DB Servers hostname contains the substrings "db2" or "oracle"
    Workaround:The database Server hosting the vCenter Database should not contain the string "db2" or "oracle".As an alternative change the vcdb.properties afterwards to the correct format.

  • vCenter Server upgrade fails with the error The system administrator has set policies to prevent this installation
    This problem can occur when the computer has insufficient contiguous memory for Windows Server 2003 or Windows XP to verify that the .msi package or the .msp package is correctly signed.

    Workaround:

    1. From the Windows Start menu, select Run, type control admintools, and click OK.
    2. Double-click Local Security Policy.
    3. Select Software Restriction Policies.
    4. If no software restrictions are listed, right-click Software Restriction Policies, and select Create New Policy.
    5. Under Object Type, double-click Enforcement.
    6. Select All users except local administrators, and click OK.
    7. Restart the computer, and retry the vCenter Server upgrade.
  • Data migration fails if the path to the vCenter Server installation media contains non-ASCII characters
    When this problem occurs, an error message similar to: 'ascii' codec can't decode byte 0xd0 in position 30: ordinal not in range(128) appears, and the installer quits unexpectedly during the data migration process.
    Workaround: Make sure the path to the vCenter Server installation media does not contain any non-ASCII characters.

Licensing

  • Automatic assignment of a vSphere license key to certain ESX/ESXi hosts in a host container might be unsuccessful and the hosts might remain in evaluation mode
    vCenter Server 5.0 supports the automatic assignment of license keys to ESX/ESXi hosts. You can associate a license key with a host container in vCenter Server, such as a datacenter or a cluster. vCenter Server assigns the license key to all unlicensed hosts that you add to this host container. You can associate only one license key to a host container. If the license that you associate with a host container is a different version than the hosts that you add to this host container, the license is not assigned to the hosts. For example, if you associate a vSphere 5.x license to a cluster and you add ESX/ESXi 4.x to the cluster, the license is not assigned to the ESX/ESXi 4.x hosts and they remain in evaluation mode.
    Workaround: Make sure that all hosts that you add to a host container are of the same version as the license that you associate with the same container. If a host from the same container requires a license of a different version, associate the license directly with the host. For example, you associate a vSphere 5.x license with a cluster. You add ESXi 5.x hosts to the cluster and they are assigned the vSphere 5.x license. You add ESX/ESXi 4.x hosts to the same cluster and associate a vSphere 4.x license with the hosts. You reconnect the ESX/ESXi 4.x hosts to vCenter Server and they are assigned the vSphere 4.x license.

Security issues

  • Datastore web interface sessions are not immediately terminated when you close the browser window
    When you close a web browser after accessing the datastore web interface, the session is not immediately terminated on the server side. VMware would like to thank Jason Jones of Inner Security for reporting this issue.
    Workaround: You must click Logout in the datastore web interface to terminate the session before you close the browser window.

Networking Issues

  • Adding a network resource pool to a vSphere Distributed Switch fails with the error Cannot complete a vSphere Distributed Switch operation for one or more host members
    This error message indicates that one or more of the hosts on the distributed switch is already associated with the maximum number of network resource pools. The maximum number of network resource pools allowed on a host is 56.
    Workaround: None.

  • Fault Tolerance is not compatible with vSphere DirectPath I/O with vSphere vMotion
    When Fault Tolerance is enabled on a virtual machine, DirectPath I/O with vMotion is inactive for all virtual adapters on the virtual machine.
    Workaround: Disable Fault Tolerance and reboot the virtual machine before enabling DirectPath I/O with vMotion.

  • vCenter Server Virtual Appliance does not support IPv6
    Although the vCenter Server Virtual Appliance Web console has an option to configure IPv6, vCenter Server Virtual Appliance does not support IPv6 configuration.
    Workaround: Do not set or change IPv6 configuration on the vCenter Server Virtual Appliance Web console.

Storage

  • Changes in the vCenter Server configuration might result in incorrect display of storage capabilities communicated by storage providers*
    In vCenter Server, when the user changes the vCenter Server configuration. For example: adding hosts, the vSphere Client display of the VASA-supplied information does not reflect the changes.
    Workaround: User must restart VMware VirtualCenter Management Webservices.

  • User-defined storage capabilities are not listed in the storage views tab for Datastores if no storage provider is registered*
    In vCenter Server, user-defined storage capabilities assigned to datastores will be reflected in a datastore's summary tab but will not be shown in the Storage View tab's Reports view unless a Storage Provider is registered.
    Workaround: None.

  • I/O latency threshold appears to be 15ms after you disable I/O metrics for a datastore cluster
    After you disable I/O metrics for a datastore cluster, the Summary page for the datastore cluster continues to display an I/O latency threshold value of 15ms (the default).
    Workaround: None. To view the correct value, select Datastore Cluster>Storage

  • Link to enter SDRS maintenance mode appears on Summary page of standalone datastore
    Only datastores that are a part of a datastore cluster can successfully enter Storage DRS maintenance mode. However, a link to enter Storage DRS maintenance mode appears on the Summary page for a datastore that is not in a datastore cluster. When you click Enter SDRS maintenance mode for a standalone datastore, the datastore attempts to enter maintenance mode and the task appears to be pending indefinitely.
    Workaround: Cancel the Enter SDRS Maintenance Mode task in the Recent Tasks pane of the vSphere Client.

  • An all paths down (APD) condition during Storage vMotion can result in communication failure between vCenter Server and ESXi host
    If an APD condition occurs when you migrate virtual machines using Storage vMotion, vCenter Server disconnects the host involved in Storage vMotion from the vCenter Server inventory. This condition persists until the background Storage vMotion operation completes. This action could take a few minutes or hours depending on the Storage vMotion operation time. During this time, no other operation can be performed for that particular host from vCenter Server.
    Workaround: None. After the Storage vMotion operation completes, vCenter Server reconnects the host back to the inventory. None of the running virtual machines on non-APD datastores are affected by this failure.

  • Symbolic links added to a datastore might cause the Datastore Browser to incorrectly display datastore contents
    When you add symbolic links at the top level of a datastore, either externally in an NFS server or by logging in to the host, you might not be able to see the correct datastore information, such as its files and folders, when you browse the datastore. Symbolic links referencing incorrect files and folders might cause this problem.
    Workaround: Remove the symbolic links. Do not use symbolic links in datastores.

  • Attempts to add an extent to an ATS-capable VMFS datastore fail
    You can only span an ATS-capable datastore over an ATS-capable device. If you select the device that does not support ATS to extend the ATS-capable datastore, the operation fails. The vSphere Client displays the An error occurred during host configuration message. In the log file, you might also find the following error message:
    Operation failed, unable to add extent to filesystem.
    Workaround: Before adding an extent to an ATS datastore, verify whether the extent device supports ATS by running the following command:
    esxcli storage core device vaai status get -d=device_ID
    The output must display the following information:
    ATS Status: supported

  • Storage DRS might not behave as expected when balancing I/O load
    When you use IOMeter software to generate I/O load to test Storage DRS, the IOMeter populates the files with only zeros by default. This data does not contain random patterns of ones and zeros, which are present in real data and which are required by Storage DRS to determine the I/O characteristics and performance of the datastore.
    Workaround: When you test Storage DRS load balancing, use real data to populate at least 20 percent of the storage space on the datastore. If you use IOMeter software to generate I/O load, choose a version that allows you to write random patterns of ones and zeros to your files.

  • Names of new virtual machine disks do not appear in Storage DRS initial placement recommendations
    When creating, cloning, or deploying from template a virtual machine on a Storage DRS-enabled datastore cluster, the placement recommendations or faults dialog box does not list the names of the new virtual machine hard disks. The dialog box displays
    Place new virtual machine hard disk on <datastore name>.
    Workaround: None. When virtual machines are being created, hard disk names are not assigned until the disks are placed. If the virtual machine hard disks are of different size and are placed on different datastores, you can use the Space Utilization before and after statistics to estimate which disk is placed on which datastore.

  • Storage DRS appears to be disabled when you use the Scheduled Task wizard to create or clone a virtual machine
    When you create a scheduled task to clone or create a virtual machine, and select a datastore cluster as the destination storage for the virtual machine files, the Disable Storage DRS check box is always selected. You cannot deselect the Disable Storage DRS check box for the virtual machine in the Scheduled Task wizard.
    Workaround: None. The Disable Storage DRS check box is always selected in the Scheduled Task wizard. However, after the Scheduled Task runs and the virtual machine is created, the automation level of the virtual machine is the same as the default automation level of the datastore cluster.

  • vSphere Client displays an error when you attempt to unmount an NFS datastore with Storage I/O Control enabled
    If you enable Storage I/O Control for an NFS datastore, you cannot unmount that datastore. The following error message appears:
    The resource is in use.
    Workaround: Before you attempt to unmount the datastore, disable Storage I/O Control.

  • After migration, the mode of an IDE RDM disk in physical compatibility does not change to Independent Persistent
    The mode of the IDE RDM disk in physical compatibility does not change to Independent Persistent after you migrate the virtual machine with the disk from the ESX/ESXi 4.x host to ESXi 5.0.
    Workaround: After migration, use the vSphere Client to change the disk's mode to Independent Persistent.

  • Attempts to add a virtual compatibility RDM with a child disk to an existing virtual machine fail
    If you try to add a virtual compatibility RDM that has a child disk to an existing virtual machine, the operation fails. The vSphere Client displays the following error message:
    Reconfigure failed: vim.fault.DeviceUnsupportedForVmPlatform.
    Workaround: Remove a child disk to be able to add a virtual compatibility RDM.

  • With software FCoE enabled, attempts to display Storage Maps fail with an error message
    This problem affects only those ESXi hosts that have been added to vCenter Server without any previous software FCoE configuration. After you enable software FCoE adapters on these hosts, attempts to display Storage Maps in the vSphere Client fail. The following error message appears:
    An internal error has occurred: Failed to serialize response.
    Workaround: Configure software FCoE on the ESXi host first, and then add the host to vCenter Server.

  • Attempts to unregister multiple storage vendor providers at the same time might fail with an error
    If you try to simultaneously unregister multiple vendor providers from vCenter Server, your attempts might fail. The following error message appears even though the failed vendor providers are present in vCenter Server:
    ManagedObjectNotFound.
    The sms.log file might display the following exception:
    ProviderUnregistrationFault.
    Workaround: Manually unregister one vendor provider at a time.

Server Issues

  • Applying a host profile with a service startup policy of off does not disable the service
    A host profile is created using as a reference host an ESXi host configured with some services disabled and is applied to a host with those services enabled. The host profile application process does not disable the services on the target ESXi host. This situation is commonly encountered by users who have enabled the ESXShell or SSH services on the target ESXi hosts through the Security Profile in the vSphere Client or Troubleshooting Options in the DCUI.

    Workaround: The reboot process disables the services. You can also manually stop the services in the vSphere Client by configuring the host. Perform this procedure for each service.

    1. Select the host in the inventory.
    2. Click the Configuration tab.
    3. Click Security Profile in the Software section.
    4. Click Properties and select the service.
    5. Click Options.
    6. Click Stop and click OK.

  • Host profile answer file status is not updated when switching the attached profile of the host
    When attaching a host profile to a host that was previously attached to another host profile, the answer file status is not updated. If the answer file status is Completed,after attaching another host profile to the host, the answer file status in the host profile view still appears as Completed. The actual status, however, might be changed to Incomplete.

    Workaround: Manually update the answer file status after attaching a host profile.

    1. In vSphere Client, select the newly attached profile in the Host Profiles inventory view.
    2. Click the Hosts and Clusters tab.
    3. Right-click the host from the Entity Name list and select Check Answer File.

    The host profile answer file status is updated.

  • Updated Manually applying a host profile containing a large configuration might timeout
    Applying a host profile that contains a large configuration, for example, a very large number of vSwitches and port groups, might timeout if the target host is either not configured or only partially configured. In such cases, the user sees the Cannot apply the host configuration error message in the vSphere Client, although the underlying process on ESXi that is applying the configuration might continue to run.

    In addition, syslog.log or other log files might have error messages such as the following message:
    Error interacting with configuration file /etc/vmware/esx.conf: Timeout while waiting for lock, /etc/vmware/esx.conf.LOCK, to be released. Another process has kept this file locked for more than 20 seconds. The process currently holding the lock is hostd-worker(5055). This is likely a temporary condition. Please try your operation again.

    This error is caused by contention on the system while multiple operations attempt to gather system configuration information while the host profiles apply operation sets configuration. Because of these errors and other timeout-related errors, even after the host profiles apply operation completes on the system, the configuration captured in the host profile might not be fully applied. Checking the host for compliance shows which parts of the configuration failed to apply, and perform an Apply operation to fix those remaining non-compliance issues.

    Workaround: Perform one of the following:

    • ESXi hosts not provisioned with Auto Deploy

      1. Increase the timeout value for the apply operation by adding the following entry in the /etc/vmware/hostd/cmdMo.xml file:

        <managedObject id="2">
        <type> vim.profile.host.profileEngine.HostProfileManager </type>
        <moId> ha-hostprofileengine-hostprofilemanager </moId>
        --> <timeOutInSeconds> xxxx </timeOutInSeconds> <--****
        <version> vim.version.dev </version>
        <cmd> /usr/bin/sh </cmd>
        <arg id="1"> -l </arg>
        <arg id="2"> -c </arg>
        <arg id="3"> /usr/lib/vmware/hostd/hmo/hostProfileEngine.py --cgi </arg>
        </managedObject>


        Where xxxx is the timeout value in seconds. By default, the apply operation times out in 10 minutes. This entry lets you set a longer timeout. For example, a value of 3600 increases the timeout to 1 hour. The value you enter might vary depending on the specific host profile configuration. After you set a high enough value, the apply operation timeout error no longer appears and the task is visible in the vSphere Client until it is complete.
      2. Restart hostd.
    • Hosts provisioned with Auto Deploy

      1. Reboot the ESXi host provisioned with Auto Deploy.
      2. For ESXi hosts provisioned with Auto Deploy, ensure that the answer file is complete by performing the Update Answer File operation on the ESXi host and then rebooting.

        The configuration in the host profile and answer file is applied on the system during initialization. Large configurations might take longer to boot, but it can be significantly faster than manually applying the host profile through the vSphere client.
  • Host Profiles compliance check fails for reference host with newly created profile
    A compliance check for a newly configured host profile for example, configured with iSCSI, might fail if the answer file is not updated before checking compliance.

    Workaround: Update the answer file for the profile before performing a compliance check.

vCenter Server and vSphere Client Issues

  • vCenter Server 5.0 virtual machines might display a red warning icon in the inventory*
    In vCenter Server 5.0, some VMs might display a red warning icon in the inventory, however the alarms tab for the VM does not indicate any alarm was triggered. This can appear for powered on and powered off VMs.
    Workaround: Possible workarounds. Note that these are all temporary solutions.
    Restart the management agents on the affected ESX/ESXi host
    Restart the vCenter Server Server service
    Remove the ESX/ESXi host from inventory, and register the host back with vCenteror
    Remove and re-register affected VMs.

  • Storage vMotion operations in a Linked mode environment may fail with error "The object has already been deleted or has not been completely created"*
    Attempting a Storage vMotion operation on a VM managed by a vCenter Server instance other than the vCenter that the user is logged into may produce an error similar to the following:"The object has already been deleted or has not been completely created." or " Call "PropertyCollector.RetrieveContents" or object "propertyCollector" on vCenter Server XXXXXXXX failed.
    Workaround: The error message does not occur if Storage vMotion operations are performed when the user logs into the vCenter instance that manages the VM.

  • Performance counters are shown to be at Stat-level 2 while they are actually moved to Stat-level3*
    In vCenter Server, some performance counters are actually moved to Stat-level 3, but appear to be available at Stat-level 2 in the vSphere Client.The vSphere Client is not updated correctly to reflect the changes to CPU and disk related information, which have been moved to stat-level 3.
    Workaround: Move to Stat-level 3 to use those counters.

  • Migrating virtual machine to another HA cluster changes the virtual machine state from protected to unprotected*
    Migrating a virtual machine from one HA cluster to another changes the virtual machine's protection state from protected to unprotected.HA status reports the virtual machine as Unprotected on the summary tab after it is migrated.Reconfiguring HA on the ESXi does not resolve the issue.
    Workaround: If the state of the migrated virtual machines has changed to unprotected, then disable and re-enable HA on the destination cluster.Alternatively, if you have not yet migrated the virtual machines to the destination HA cluster, you may disable HA on the source cluster before migrating the virtual machine to the destination HA cluster. Afterwards re-enable HA on the destination cluster.

  • Logging into vCenter (using SQL database) with certain third party applications can cause severe vCenter database performance issues*
    When applications like nWorks query the vCenter SQL database, the resultant SQL query can be very large which causes the database to run out of tempdb space and cause vCenter service to crash.
    Workaround: If the database performance issue is caused by a SQL query with a huge IN CLAUSE coming from vCenter Server, then the following config parameter can be used which alters the query produced from EventManagervia the vpxd.cfg configuration file.

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

  • The vSphere Web Client Alarms sidebar does not indicate the correct number of alarms present in the system
    When more than 100 alarms are present in the system, the vSphere Web Client Alarms sidebar falsely indicates only 100 alarms.
    Workaround: None.

  • Overview performance charts do not appear for datastore clusters or datastores in large environments
    In some large environments, overview performance charts might not appear for datastore clusters or datastores because vSphere Management WebServices, Tomcat, is out of memory.
    Workaround: Increase the amount of memory available to Tomcat.

  • When using the vSphere Web Client, you are repeatedly prompted to increase local storage available for Adobe Flash
    The vSphere Web Client uses local storage on the system that isused to access the client to store log files. The storage limits for the log files are determined by Adobe Flash Player settings. As the log files grow, a dialog box appears prompting you to increase the limit. You are prompted again periodically until the storage limit reaches Unlimited.
    Workaround: Set the storage limits for the Adobe Flash Player:

  • Cannot select multiple columns for sorting in the vSphere Web Client
    In tables in the vSphere Web Client, you can select the primary column for sorting by clicking on the column header. Clicking on a second column header changes that column to the primary sorting column rather than selecting it as the secondary sorting column.

    Workaround: To sort by multiple columns in vSphere Web Client tables, perform the following procedure:

    1. Select the primary column for sorting by clicking on the column header.
    2. Select the secondary and subsequent columns for sorting by Ctrl-clicking on the column headers.

  • Internet Explorer 7 cannot load vSphere Web Client pages
    If Internet Explorer 7 security settings do not include about:internet and https://localhost as trusted sites, the Web browser cannot open vSphere Web Client pages.

    Workaround: Add about:internet and https://localhost as trusted sites:

    1. In Internet Explorer 7, select Tools > Internet Options.
    2. Click the Security tab.
    3. Select Trusted Sites.
    4. Click Sites.
    5. In the Add this Web site to the zone text box, type about:internet and click Add.
    6. In the Add this Web site to the zone text box, type https://localhost and click Add.
    7. Click OK.
    8. Close and restart Internet Explorer.
  • Opening the vSphere Administration Application from a shortcut produces the error: Windows cannot find 'https://localhost:9443/admin-app'
    When Firefox is the default Web browser and is not running, launching the vSphere Administration Application from a shortcut might produce the error:
    Windows cannot find 'https://localhost:9443/admin-app'. Make sure you typed the name correctly, and then try again.

  • Workaround: This is a known issue with Firefox on some Windows systems. See http://kb.mozillazine.org/Windows_error_opening_Internet_shortcut_or_local_HTML_file_-_Firefox.

  • The vSphere Web Client does not load the vCenter Server inventory if the vCenter Server host name cannot be resolved
    If the vSphere Web Client cannot resolve the vCenter Server system's host name and the vCenter Server is registered with the vSphere Client using an IP address, the vSphere Web Client cannot load the inventory tree.
    Workaround: Ensure that the vCenter Server's host name can be resolved in one of the following ways:

    • Add the vCenter Server system to your name server.
    • Add the vCenter Server system to the C:\Windows\System32\drivers\etc\hosts file on the system that runs the vSphere Web Client
  • Flash plug-in crashes when logging in or out of vSphere Web Client on Linux
    When you log in or out of the vSphere Web Client on a Linux system, the Flash plug-in might crash.
    Workaround: Reload the page to restart the Flash plug-in.

  • Cannot access vSphere Web Client administration tool using a local IPv6 address
    If you attempt to access the vSphere Web Client administration tool using a local IPv6 address, the Web browser displays the error message
    vSphere Web Client administration tool cannot be accessed from a remote host.

  • Workaround: Use localhost instead of the IPv6 address to access the administration tool. For example, use https://localhost:9443/admin-app instead of an address like https://[fc00:10:20:123:355c:1744:1b82:6716]:9443/admin-app.

  • Internet Explorer 7 cannot access vSphere Client Web pages when the client is installed on a system that uses pure IPv6
    If the vSphere Web Client is installed on an operating system that uses pure IPv6, you cannot use Internet Explorer 7 to access the vSphere Web Client.
    Workaround: Use Firefox or Internet Explorer 8 to access the vSphere Web Client.

  • Internet Explorer might fail to download the Client Integration Plug-In
    When you use Internet Explorer to download the Client Integration Plug-In, you might see the error message,Internet Explorer cannot download the vmware-vmcr-win32-x86.exe from localhost. This happens when certain security settings in Internet Explorer prevent download of the Client Integration Plug-In.
    Workaround: Use an alternative method of downloading the Client Integration Plug-In.

    • Use Firefox to connect to the vSphere Web Client and download the Client Integration Plug-In.
    • Use Internet Explorer to connect to the Client Integration Plug-In file directly using the non-secure port http://ipaddress:portnumber/vsphere-client/vmrc/vmware-vmrc-win32-x86.exe. For example, http://localhost:9090/vsphere-client/vmrc/vmware-vmrc-win32-x86.exe.
  • The vSphere Web Client does not load or refresh data
    Sometimes the vSphere Web Client cannot load or refresh data. The loading spinner at the top right corner of the application continues to spin, and the requested information is not displayed.
    Workaround: Perform one or more of the following procedures:

    • Click the browser's Refresh button.
    • Select a different object from the inventory tree and click the browser's Refresh button.
    • Check the health status of vCenter Server and its services. Restart any services that have stopped.
  • The vSphere Web Client login page is not accessible from the vCenter Server Welcome page
    If you use a localhost URL to access the vCenter Server Welcome page, clicking the Log in to vSphere Web Client produces an error.
    Workaround: Use the IP address or host name of the vCenter Server system to access the Welcome page.

  • The Select Users and Groups dialog box in the vSphere Client shows truncated user and group names
    When you add a permission to an inventory object in the vSphere Client, the Select Users and Groups dialog box might display truncated names for users and groups. For example, Administrator might display as tor. Users and groups can be selected only by typing the correct complete name.
    This occurs when the Workstation service in Windows is stopped.

  • Workaround: Restart the Workstation service on the vCenter Server machine.

    Select Start > Programs > Administrative Tools > Services.

    Right-click Workstation and select Start.

  • The exported list of virtual machines might be incomplete
    When you select a datacenter, cluster, host, or other object in the vSphere Client inventory and export a list of its virtual machines, the list might not include all the virtual machines. This occurs because information in the list is not always populated for objects that are not visible.
    Workaround: Before exporting, scroll through the list to make sure that all virtual machines are displayed.

  • Spurious error messages appear in the vSphere Web Client log files
    Some spurious error messages appear in the vSphere Web Client log files because of the versions of Tomcat and dm Server used. These include a number of INFO messages as well as the message, SEVERE: No global context defined for server. You can ignore these messages.
    Workaround: None.

  • vSphere Web Client online Help incorrectly lists Firefox 3.5 as a supported browser
    The vSphere Web Client online Help incorrectly lists Firefox 3.5 as a supported Web browser for the vSphere Web Client and client integration plug-in.
    Workaround: For information about supported Web browsers, see the vSphere Installation and Setup documentation.

  • The vSphere Client shows an error message when attempting to view VM Storage Profiles
    When you connect the vSphere Client to vCenter Server and attempt to view a virtual machine's storage profile, you might see the error message, VC is unable to connect to Profile-driven storage service at http:///sps/sdk.
    A port conflict occurs when the Storage Profile Service and another service are configured to use port 31000. The vSphere Web Client and vCenter Orchestrator can cause this conflict.

    Workaround: Restart vSphere Web Client service and the vCenter Orchestrator configuration service. The services will pick the next available free port when they are restarted. If only one of the services is present or running on the machine, you need only restart that service.

  • Information in the Virtual Machines tab might not refresh
    Sometimes information in the Virtual Machines tab in the vSphere Client might not immediately refresh. For example, if you clone or register a large number of virtual machines, some virtual machines might not appear in the Virtual Machines tab, although they appear in the inventory tree. If you power on or power off a large number of virtual machines, the new power states might not be reflected on the Virtual Machines tab, although they are correctly displayed in the inventory tree.
    Workaround: Press F5 to refresh the information in the tab.

  • vSphere Web Client does not load in Internet Explorer 9 on Windows Server 2008
    When you attempt to load the vSphere Web Client in Internet Explorer 9 on a Windows Server 2008 system, you see a blue background in the Web browser window and no further activity.
    Workaround: On Windows Server 2008 systems, use Internet Explorer 7 or 8 or Mozilla Firefox 3.6 or later to access the vSphere Web Client.

  • vSphere Web Client state does not persist between sessions
    The state of the vSphere Web Client normally persists between sessions, so that when you log in with the vSphere Web Client again, the same objects and tabs are selected that were selected when you logged out of the previous session. However, if your Web browser preferences are set so that the browser does not remember history, or if the Flash player Website Storage settings do not allocate any storage for visited sites, the Flash player does not store data from the vSphere Web Client and the state does not persist from session to session.

    Workaround: Perform the following procedure:

  • The vSphere Web Client intermittently produces Error #2406: The loaded file did not have a valid signature
    When using Mozilla Firefox 3.6.x on SUSE Linux Enterprise Server 11 or Red Hat Enterprise Linux 5, the follow error message might occur intermittently:
    Error #2406: The loaded file did not have a valid signature.
    Workaround:Restart the Web browser and reconnect to the vSphere Web Client.

  • vCenter Server Crashes When Exporting System Logs
    When you export system logs from vCenter Server, vCenter Server uses the folder specified by the WindowsTEMP environment variable. By default, this variable is set of C:\Windows\Temp.
    If vCenter Server is configured to store a large amount of log data, or if you select a large number of hosts from which to download logs, the drive specified in theTEMP variable can run out of space. If this drive is the same drive on which vCenter Server is installed, the VMware VirtualCenter Server service might crash.
    Workaround: Ensure that the drive specified by the Windows TEMP environment variable has enough free space for exported logs. Consider specifying a drive other than C: in the TEMP variable to prevent disruption to system services.

Virtual Machine Management Issues

  • CPU hot add error on hardware version 7 virtual machines
    Virtual CPU hot add is supported with the multicore virtual CPU feature for hardware 8 virtual machines.
    For hardware version 7 virtual machines with cores per socket greater than 1, when you enable CPU hot add in the Virtual Machine Properties dialog box and try to hot add virtual CPUs, the operation fails and a CPU hot plug not supported for this virtual machine error message appears.
    Workaround: To use the CPU hot-add feature with hardware version 7 virtual machines, power off the virtual machine and set the number of cores per socket to 1.
    For best results, use hardware version 8 virtual machines.

  • USB devices passed through from an ESXi host to a virtual machine might disconnect during migration with vMotion
    When a USB device is passed through to a virtual machine from an ESXi host and the device is configured to remain connected during migration with vMotion, the device might disconnect during the vMotion operation. The devices can also disconnect if DRS triggers a migration. When the devices disconnect, they revert to the host and are no longer connected to the virtual machine. This problem occurs more often when you migrate virtual machines that have multiple USB devices connected, but occasionally happens when one or a small number of devices are connected.
    Workaround: Migrate the virtual machine back to the ESXI host to which the USB devices are physically attached and reconnect the devices to the virtual machine.

  • A virtual machine with an inaccessible SCSI passthrough device fails to power on
    If a SCSI passthrough device attached to a virtual machine has a device backing that is inaccessible from the virtual machine's host, the virtual machine fails to power on with the error, An unexpected error was received from the ESX host while powering on VM.
    Workaround: Perform one of the following procedures:

    • If the virtual machine's host has a physical SCSI device, change the device backing of the SCSI passthrough device to the host's physical SCSI device, and power on the virtual machine.
    • If the host does not have a physical SCSI device, remove the SCSI passthrough device from the virtual machine and power it on.
  • Virtual machine clone or relocation operations from ESXi 5.0 to ESX/ESXi 4.1 fail if replication is enabled
    If you use the hbr enablereplication command to enable replication on a virtual machine that resides on an ESXi 5.0 host and clone the virtual machine to an ESX/ESXi 4.1 or earlier host, validation fails with an operation is not supported error message. Cloning of ESXi 5.0 virtual machines on ESX/ESXi 4.1 hosts is not supported.
    Workaround: Select one of the following workarounds:

    • Clone the virtual machine onto an ESXi 5.0 host
    • Clone or relocate a new virtual machine on an ESX/ESXi 4.1 host.
  • vCenter Server 5.0 and ESX/ESXi host incompatibility cause migration operations for virtual machines with delta disks to fail
    If vCenter Server 5.0 manages a host earlier than ESX/ESXi 4.0 Update 3, you cannot migrate virtual machines with snapshots or delta disks to that host. Attempting such migrations results in the following system error message:
    Migration of VMs with snapshots or delta disks is not supported due to version incompatibility between vCenter Server and ESX. To continue this operation, please upgrade your ESX host(s) to ESX 4.0 Update 3 or later.
    The same restriction applies and a similar error message appears for ESX/ESXi 4.1. ESX/ESXi 4.1 does not support migration of virtual machines with delta disks if vCenter Server 5.0 manages the host.
    Workaround: Upgrade the ESX/ESXi host to ESX/ESXi 4.0 Update 3 or later or upgrade to ESX 4.1 Update 1 or later.

  • Non-ASCII DNS suffixes are not set correctly after customizing Windows XP and Windows 2003
    If you enter a non-ASCII DNS suffix in the Network Properties DNS tab when you use the Customization Specification Wizard to customize Windows XP or Windows 2003, the customization is reported as successful but the non-ASCII DNS suffix is not set correctly.
    Workaround: Set the DNS suffix manually in Windows XP and Windows 2003.

  • The snapshot disk path in the .vmsd snapshot database file and the parent path in the delta disk descriptor file are not updated after migration
    When snapshot.redoNotWithParent is set to TRUE and you change the
    snapshotDirectory setting from, for example, Database A to Database B, you might see an error message that says,
    Detected an invalid snapshot configuration. This problem occurs when both of the following conditions exist:

    • You revert to a previous snapshot in the snapshot tree and create new snapshots from that snapshot point. The result is a nonlinear snapshot tree hierarchy.
    • The disk links in a disk chain span multiple datastores and include both the source and destination datastores. This situation occurs if you change the snapshotDirectory settings to point to different datastores more than once and take snapshots of the virtual machine between the snapshotDirectory changes. For example, you take snapshots of a virtual machine with snapshotDirectory set to Datastore A, revert to a previous snapshot, then change the snapshotDirectory settings to Datastore B and take additional snapshots. Now you migrate the virtual disk from Datastore B to Datastore A.

    The best practice is to retain the default setting, which stores the parent and child snapshots together in the snapshot directory. Avoid changing the snapshotDirectory settings or taking snapshots between datastore changes. If you set snapshot.redoNotWithParent to TRUE, perform a full storage migration to a datastore that is currently not used by the virtual machine.

    Workaround: Manually update the disk path references to the correct datastore path in the snapshot database file and disk descriptor file.

Migration Issues

  • Cold migration of a virtual machine that has IDE virtual disk from an ESXi 5.0 host to ESX/ESXi 4.x host fails with the error The operation is not supported on the object
    When you use vCenter Server 5.0 to cold migrate a virtual machine that has one or more IDE virtual disks from an ESXi 5.0 host to a host running ESX/ESXi 4.x, the migration fails with the error The operation is not supported on the object.

    Workaround: Perform the following steps.

    1. On the ESXi 5.0 host, select the virtual machine.
    2. If the VM resides on a host-only datastore on the ESXi 5.0 host, move the virtual machine .vmx and .vmdk files to a shared LUN that is accessible to the ESXi 5.0 host and the ESX/ESXi 4.x host.
    3. Cold migrate the virtual machine to the ESX/ESXi 4.x host by using the Change host option in the Migrate Virtual Machine wizard.

  • During Daylight Saving Time (DST) transitions, the time axis on performance charts is not updated to reflect the DST time change.
    For example, local clocks in areas that observe DST were set forward 1 hour on Sunday, March 27, 2011 at 3am. The tick markers on the time axis of performance charts should have been labeled ..., 2:00, 2:20, 2:40, 4:00, 4:20, ..., omitting ticks for the hour starting at 3am. The labels actually displayed are ..., 2:00, 2:20, 2:40, 3:00, 3:20, 3:40, 4:00, 4:20, ....

    Workaround: None

  • Virtual machine disks retain their original format after a Storage vMotion operation in which the user specifies a disk format change
    When you attempt to convert the disk format to Thick Provision Eager Zeroed during a Storage vMotion operation of a powered-on virtual machine on an host running ESX/ESXi 4.1 or earlier, the conversion does not happen. The Storage vMotion operation succeeds, but the disks continue to retain their original disk format because of an inherent limitation of ESX/ESXi 4.1 and earlier. If the same operation is performed on a virtual machine on an ESXi 5.0 host, the conversion happens correctly.

    Workaround: None.

  • The vCenter Server support bundle tool cannot find log data that is stored in a custom location
    The vCenter Server support bundle tool cannot locate log files that are stored in custom, non-default, locations. The vCenter Server support bundle tool is different from the vSphere Client log gathering tool.

    Workaround: Connect a vSphere Client to a vCenter Server and use the Export System Logs function to retrieve log data. In the vSphere Client, select Administration > Export System Logs.

    When you cannot connect a vSphere Client to a vCenter Server, you must manually copy the files into the log bundle.

VMware HA and Fault Tolerance Issues

  • In vCenter Server 5.0 a number of advanced configuration options for vSphere HA are no longer supported
    The following options are no longer supported.

    das.consoleUser
    das.consoleNode
    das.consolePerm
    das.primaryCount
    das.checkVmStateDelay
    das.trace
    das.traceLevel
    das.traceOutput
    das.preferredPrimaries
    das.disableUWSwapRequirement
    das.sensorPollingFreq
    das.bypassNetCompatCheck
    das.defaultfailoverhost
    das.failureDetectionTime
    das.failureDetectionInterval

    If you attempt to set one of the unsupported options, vCenter Server 5.0 reports that the option is not valid. Also, if you upgrade to vCenter Server 5.0 from a previous version with any of these options defined, they are deleted and are no longer in effect.
    Workaround: None.

  • vSphere HA fails to restart a virtual machine that was being migrated using vMotion when a host failure occurred.
    While a virtual machine is being migrated from one host to another, the original host might fail, become unresponsive, or lose access to the datastore containing the configuration file of the virtual machine. If such a failure occurs and the vMotion subsequently also fails, vSphere HA might not restart the virtual machine and might unprotect it.
    Workaround: If the virtual machine fails and vSphere HA does not power it back on, power the virtual machine back on manually. vSphere HA then protects the virtual machine.

Internationalization Issues

  • Search does not find localized characters in Japanese, Chinese, Korean, German, French, and Spanish.
    Search for localized characters does not retrieve hits for Japanese, Chinese, Korean, and characters in German, French, and Spanish.
    Workaround: When searching for topics, use English interface.

  • Users with user names containing non-ASCII characters cannot log in to vCenter Server using the vSphere Web Client
    The vSphere Web Client does not accept user names containing non-ASCII characters. Users with user names containing non-ASCII characters cannot use the vSphere Web Client to connect to vCenter Server.
    Workaround: Use the vSphere Client to connect to vCenter Server.

  • Issues related to localized search and search scope in the vSphere Web Client Help
    Known issues with localized search in the vSphere Web Client Help include:
    Searches using localized characters for non-English languages do not retrieve results. If you create search scope names using non-ASCII characters, these characters do not display correctly.
    Workaround: Edit the tomcat-server.xml file to specify URI encoding as UTF-8:

    Open the file vSphere_Web_Client_Installation_Directory\springsource-dm-server-2.0.4\config\tomcat-server.xml using a text editor.

    Edit the following section of the file to add the parameter URIEncoding="UTF-8" at the end of the line connectionTimeout="20000":

    <Connector port="9090" protocol="HTTP/1.1"
    connectionTimeout="20000"
    redirectPort="9443" emptySessionPath="true"/>


    9090 is the default value for the Connector port. If you changed this value during installation, another port number appears. Do not change the port number.

    After the change, the section should read as follows:

    <Connector port="9090" protocol="HTTP/1.1"
    connectionTimeout="20000" URIEncoding="UTF-8"
    redirectPort="9443" emptySessionPath="true"/>

    Edit the following section of the file to add the line URIEncoding="UTF-8" at the end of the line keystoreFile="config/keystore":

    <Connector port="9443" protocol="HTTP/1.1" SSLEnabled="true"
    maxThreads="500" scheme="https" secure="true"
    clientAuth="false" sslProtocol="TLS"
    keystoreFile="config/keystore"
    keystorePass="changeit" emptySessionPath="true"/>


    9443 is the default value for the Connector port. If you changed this value during installation, another port number appears. Do not change the port number.

    After the change, the section should read as follows:

    <Connector port="9443" protocol="HTTP/1.1" SSLEnabled="true"
    maxThreads="500" scheme="https" secure="true"
    clientAuth="false" sslProtocol="TLS"
    keystoreFile="config/keystore" URIEncoding="UTF-8"
    keystorePass="changeit" emptySessionPath="true"/>

    Save the file.