VMware

VMware vSphere® 5.0 Release Notes

VMware ESXi™ 5.0 | 24 Aug 2011 | Build 469512

VMware vCenter Server™ 5.0 | 24 Aug 2011 | Build 456005

vCenter Server Appliance 5.0 | 24 Aug 2011 | Build 472350

Last updated: 2 JAN 2013

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

This release of vSphere 5.0 includes ESXi 5.0 and vCenter Server 5.0. Read about the new and enhanced features in this release in What's New in VMware vSphere 5.0.

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

Compatibility and Installation

ESXi, vCenter Server, and vSphere Client Version Compatibility

The VMware Product Interoperability Matrix provides details about the compatibility of current and previous versions of VMware vSphere components, including ESXi, VMware vCenter Server, the vSphere Client, and optional VMware products. In addition, check this site for 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.

Hardware Compatibility for ESXi

To determine which processors, storage devices, SAN arrays, and I/O devices are compatible with vSphere 5.0, use the ESXi 5.0 information in the VMware Compatibility Guide.

Upgrades and Installations for supported CPUs. vSphere 5.0 supports only CPUs that have LAHF and SAHF CPU instruction sets. During an installation or upgrade, the installer checks the compatibility of the host CPU with vSphere 5.0. For CPU support, see the VMware Compatibility Guide.

Guest Operating System Compatibility for ESXi

To determine which guest operating systems are compatible with vSphere 5.0, use the ESXi 5.0 information in the VMware Compatibility Guide.

Virtual Machine Compatibility for ESXi

Virtual machines with virtual hardware versions 4.0 and later are supported with ESXi 5.0. Hardware version 3 is no longer supported. To use hardware version 3 virtual machines on ESXi 5.0, upgrade virtual hardware. See the vSphere Upgrade documentation.

Updated 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 are not supported.

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

Migrating Third-Party Solutions

ESX/ESXi hosts might contain third-party software, such as Cisco Nexus 1000V VEMs or EMC PowerPath modules. The ESXi 5.0 architecture is changed from ESX/ESXi 4.x so that customized third-party software packages (VIBs) cannot be migrated when you upgrade from ESX/ESXi 4.x to ESXi 5.0. When you upgrade a 4.x host with custom VIBs that are not in the upgrade ISO, you can proceed with the upgrade but will receive an error message listing the missing VIBs. To upgrade or migrate such hosts successfully, you must use Image Builder to create a custom ESXi ISO image that includes the missing VIBs. To upgrade without including the third-party software, use the ForceMigrate option or select the option to remove third-party software modules during the remediation process in vSphere Update Manager. For information about how to use Image Builder to make a custom ISO, see the vSphere Installation and Setup documentation. For information about upgrading with third-party customizations, see the vSphere Upgrade and Installing and Administering VMware vSphere Update Manager documentation. For information about upgrading with vSphere Update Manager, see the vSphere Upgrade and Installing and Administering VMware vSphere Update Manager documentation.

Upgrades for This Release

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

vCenter Server Upgrades

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 VirtualCenter 2.5 Update 6 and 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 it possible to upgrade from a 32-bit system to a 64-bit system.

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

ESX/ESXi Upgrades

vSphere 5.0 provides the following tools for upgrading ESX/ESXi hosts.

  • vSphere Update Manager. If your site uses vCenter Server, use vSphere Update Manager to perform an orchestrated host upgrade or an orchestrated virtual machine upgrade. See the instructions in the vSphere Upgrade documentation, or for complete documentation about vSphere Update Manager, see the Installing and Administering VMware vSphere Update Manager documentation.

  • Upgrade interactively using an ESXi installer ISO image on CD-ROM or DVD. You can run the ESXi 5.0 installer from a CD-ROM or DVD drive to perform an interactive upgrade. This method is appropriate for upgrading a small number of hosts.

  • Perform a scripted upgrade. You can upgrade or migrate from ESXi/ESX 4.x hosts to ESXi 5.0 by running an update script, which provides an efficient, unattended upgrade. Scripted upgrades also provide an efficient way to deploy multiple hosts. You can use a script to upgrade ESXi from a CD-ROM or DVD drive, or by PXE-booting the installer.

Test Releases of vSphere 5.0

Upgrades from the vSphere 5.0 Beta and the vSphere 5.0 Release Candidate releases to vSphere 5.0 are not supported. Uninstall ESXi 5.0 Beta or Release Candidate and vCenter Server 5.0 Beta or Release Candidate, and perform fresh installations of vCenter Server 5.0 and ESXi 5.0. If you were testing Beta or Release Candidate versions of vSphere 5.0, VMware recommends that you recreate data you want to preserve from those setups on vSphere 5.0.

VMware vSphere SDKs

VMware vSphere provides a set of SDKs for vSphere server and guest operating system environments.

  • vSphere Management SDK. A collection of software development kits for the vSphere management programming environment. The vSphere Management SDK contains the following vSphere SDKs:

    • vSphere Web Services SDK. Includes support for new features available in ESXi 5.0 and vCenter Server 5.0 server systems. You can also use this SDK with previous versions of ESX/ESXi and vCenter Server. For more information, see the VMware vSphere Web Services SDK Documentation.

    • vSphere vCenter Storage Monitoring Service (SMS) SDK. SMS 2.0 is supported on vCenter Server 5.0. For more information, see vCenter SMS SDK Documentation.

    • vSphere ESX Agent Manager (EAM) SDK. EAM 1.0 is supported on ESXi 5.0. For more information, see vSphere ESX Agent Manager.

  • vSphere Guest SDK. The VMware vSphere Guest SDK 4.0 is supported on ESXi 5.0. For more information, see the VMware vSphere Guest SDK Documentation.

  • VMware vSphere SDK for Perl. The SDK for Perl 5.0 is supported on vSphere 5.0. For more information, see the vSphere SDK for Perl Documentation.

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 will continue 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. Using VMCI sockets to communicate between ESXi and virtual machines will continue 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.

Known Issues

The following known issues have been discovered through rigorous testing and will help you understand some behavior you might encounter in this release. This list of issues pertains to this release of vSphere 5.0 only. Some known issues from previous releases might also apply to this release. If you encounter an issue that is not listed in this known issues list, you can review the known issues from previous releases, search the VMware Knowledge Base, or let us know by providing feedback.

Known Issues List

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

Installation Issues
  • Updated In scripted installations, the ESXi installer does not apply the --fstype option for the part command in the ks file
    The --fstype option for the part command is deprecated in ESXi 5.0. The installer accepts the --fstype option without displaying an error message, but the installer does not create the partition type specified by the --fstype option. By default, the installer always creates VMFS5 partitions in ESXi 5.0. You cannot specify a different partition type with the --fstype option for the part command.

  • Rules information missing when running Image Builder cmdlet to display modified image profile in PowerShell 1.0
    You install vSphere PowerCLI on Microsoft PowerShell 1.0. You then add an OEM software package to an image profile. When you list the image profile, information about the Rules property is missing.

    Workaround: Access the rules information by displaying the Rules property of the image profile object.

  • 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.
       
  • Scripted ESXi installation or upgrade from CD or DVD fails unless the boot line command uses uppercase characters for the script file name
    When you perform a scripted installation or upgrade from an ESXi 5.0 installer ISO burned to CD or DVD along with the installation or upgrade script (kickstart file), the installer recognizes the kickstart file name only in uppercase, even if the file was named in lowercase. For example, if the kickstart file is named ks.cfg, and you use the ks=cdrom:/ks.cfg boot line command to specify the kickstart file location, the installation fails with an error message similar to HandledError: Error (see log for more info): cannot find kickstart file on cd-rom with path -- /ks.cfg.

    Workaround: Use uppercase for the kickstart file name in the boot line command to specify the kickstart file, for example: ks=cdrom:/KS.CFG

  • Misleading error message when you attempt to install VIBs and you use a relative path
    When you attempt to install a depot, VIB, or profile by using the esxcli software vib command, and you specify a relative path, the operation fails with the error No such file or directory: '/var/log/vmware/a.vib'

    Workaround: Specify the absolute path when you perform the installation.

  • 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
  • A live update with ESXCLI fails with a VibDownloadError message
    When you perform the following tasks, in sequence, the reboot required transaction fails and a VibDownloadError message appears.

    1. A live install update using the esxcli software profile update or esxcli vib update command.
    2. Before reboot, you perform a transaction that requires a reboot, and the transaction does not complete successfully. One common possible failure is signature verification, which can only be checked after the VIB is downloaded.
    3. Without rebooting the host, you attempt to perform another transaction that requires a reboot. The transaction fails with a VibDownloadError message.

    Workaround: Resolving the issue is a two-step process.

    1. Reboot the ESXi host to clean up its state.
    2. Repeat the live install.
       
  • Updated ESXi 4.0 Update 2 hosts might crash after vCenter Server upgrade to version 5.0
    This crash is accompanied by the following message, displayed on the purple screen: NOT_IMPLEMENTED bora/vmkernel/filesystems/visorfs/visorfsObj.c:3391.

    Workaround: Before you upgrade to vCenter Server 5.0, upgrade all ESXi 4.0 Update 2 hosts that are managed by the vCenter Server to ESXi 4.0 Update 3.

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

  • During scripted upgrades from ESX/ESXi 4.x to ESXi 5.0, MPX and VML disk device names change, which might cause the upgrade to fail
    MPX and VML disk device names might not persist after a host reboot. If the names change after reboot in a scripted upgrade, the upgrade might be interrupted.

    Workaround: When possible, use Network Address Authority Identifiers (NAA IDs) for disk devices. For machines that do not have disks with NAA IDS, such as Hewlett Packard machines with CCISS controllers, perform the upgrade from a CD or DVD containing the ESXi installer ISO. Alternatively, in a scripted upgrade, you can specify the ESX or ESXi instance to upgrade by using the upgrade command with the --firstdisk= parameter. Installation and upgrade script commands are documented in the vSphere Installation and Setup and vSphere Upgrade documentation.

  • ESX console and esxi_install.log report fails to acquire a DHCP address during upgrade when the ESX system uses manually assigned IP addresses on a subnet without DHCP service
    This situation occurs when an ESX system that has manually assigned IP addresses is run on a subnet that does not have a DHCP server or when the DHCP server is out of capacity. In either case, when the ESX system is upgraded, the system will pause for up to one minute attempting to fetch an IPv4 address from a DHCP server.

    Workaround: None. After the system pauses for up to one minute, it will continue to the successful completion of the upgrade. The system might display a prompt to press Enter to continue. You can either press Enter or ignore the prompt. In either case, the system will proceed with the upgrade after the pause.

  • Upgrade from ESX 4.x to ESXi 5.0 halts in a failed state with the message possibly corrupt file
    When you upgrade to ESXi 5.0 from an ESX 4.x system that has extraneous or unrecognized lines in /etc/sysconfig/network, the upgrade installer is unable to parse those lines, and halts with this error.

    Workaround: Before you upgrade, ensure that there are no extraneous lines in the ESX configuration files in /etc/sysconfig/network. In particular, look for the line encoding=UTF-8, which can be added to a file without user intervention.

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

  • Ensure secure access to the vCenter Server Appliance
    When the vCenter Server Appliance is configured to use a directory service such as Active Directory or NIS (Network Information Service), all users have local shell log in privileges. The local shell can only be accessed using the remote console in the vCenter Client. You must lock down access rights to the vCenter Server Appliance using vCenter Server or hostd privileges to only include appropriate administrators.

    Workaround: Limit virtual machine operations on the vCenter Server Appliance to administrators only, which includes access to the virtual machine console and the ability to power a virtual machine on or off.

    • For the vCenter Server system that manages the vCenter Server Appliance: Do not assign any virtual machine privileges on the vCenter Server Appliance to any user without administrator privileges.
    • For the hostd process of any ESXi system that hosts the vCenter Server Appliance: Do not assign any virtual machine privileges on the vCenter Server Appliance to any user without administrator privileges.
    With these access rights in place, no user without administrator privileges can gain access to the vCenter Server Appliance through the vSphere Client.

Networking Issues
  • Service Console details do not appear in Add Host to vSphere distributed wizard and Manage Hosts wizard
    When adding a 4.x ESX host to a distributed switch, the details of the Service Console network adapters do not appear in the Add Host wizard on the Network Connectivity page in the Virtual Adapter details section. Typically the MAC address, IP address, and Subnet Mask should appear here.

    Workaround: To view the details of a Service Console network adapter, exit the Add Hosts or Manage Hosts wizard, then navigate to Host > Configuration > Networking in the vSphere client.

    If the Service Console network adapter is deployed on a standard switch:

    1. Locate the switch.
    2. Click the "Properties..." button.
    3. Select the Service Console network adapter.
      Make a note of the name of the adapter, which appears in the VSS diagram.

    If the Service Console network adapter is deployed on a distributed switch:

    1. Navigate to the vSphere Distributed Switch tab.
    2. Locate the distributed switch and select "Manage Virtual Adapter...".
    3. Locate and select the Service Console Network adapter.

  • The ESXi Dump Collector server silently exits
    When the ESXi Dump Collector server's port is configured with an invalid value, it exits silently without an error message. Because this port is the port through which the ESXi Dump Collector server receives core dumps from ESXi hosts, these silent exits prevent ESXi host core dumps from being collected. Because error messages are not sent by ESXi Dump Collector to vCenter Server, the vSphere administrator is unaware of this problem. If not resolved, this affects supportability when failures occur on an ESXi host.

    Workaround: Select a port only from within the recommended port range to configure the ESXi Dump Collector server to avoid this failure. Using the default port is recommended.

  • Use of a 10G QLogic NIC, version QLE3142, with a nx_nic driver causes servers to stop functioning during gPXE boot
    If a 10G QLogic NIC, version QLE3142, with a nx_nic driver is used to gPXE boot into the ESXi Stateless boot configuration, the ESXi server stops functioning and fails to boot.

    Workaround: Use other NICs for gPXE boot.

  • Enabling more than 16 VMkernel network adapters causes vSphere vMotion to fail
    vSphere 5.0 has a limit of 16 VMkernel network adapters enabled for vMotion per host. If you enable more than 16 VMkernel network adapters for vMotion on a given host, vMotion to or from that host might fail. The error message says refusing request to initialize 17 stream ip entries, where the number indicates how many VMkernel network adapters you have enabled for vMotion.

    Workaround: Disable vMotion VMkernel network adapters until only 16, at most, are enabled for vMotion.

  • Network I/O control overrides 802.1p tags in outgoing packets in ESXi 5.0
    In ESXi 5.0, the network I/O control bridges the gap between virtual networking Quality of Service (QoS) and physical networking QoS, allowing you to specify an 802.1p tag on a per-resource pool basis.
    A side effect of this functionality is that each resource pool is tagged with a default 802.1p tag (0), even if the tag has not been explicitly set. Class of Service (CoS) bit tagging inside a virtual machine is overridden when leaving the ESXi host if network I/O control is enabled.

    Workaround: None. You can choose to not use network I/O control.

  • IPv6-only VMkernel network adapter configurations not supported in the host profile
    When you use the vSphere Client to set IP configurations for a host profile, you are allowed to set IPv4-only, IPv6-only, or a mix of IPv4 and IPv6 settings for VMkernel network adapters. IPv6-only settings, however, are not supported in host profiles. If you configure VMkernel network adapters with IPv6-only settings, you are asked to provide IPv4 configurations in the host profile answer file.

    Workaround: Perform one of the following tasks:

    • Use only IPv6 settings to configure your VMkernel network adapters through the vSphere Client, and do not use a host profile.
    • Include both IPv6 and IPv4 configurations for VMkernel network adapters when creating and applying the host profile, then disable the IPv4 configurations for the VMkernel network adapters after applying the profile.

  • Some Cisco switches drop packets with priority bit set
    VMware vSphere Network I/O Control allows you to tag outgoing traffic with 802.1p tags. However, some Cisco switches (4948 and 6509) drop the packets if the tagged packets are sent on the native VLAN (VLAN 0).

    Workaround: None.

  • Significant delay in the ESXi boot process during VLAN configuration and driver loading
    ESXi hosts with BE2 or BE3 interfaces encounter a significant delay during driver loading and VLAN configuration. The length of the delay increases with the number of BE2 and BE3 interfaces on the host and can last for several minutes.

    Workaround: None.

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

  • Adding a network resource pool to a vSphere Distributed Switch fails with the error vim.fault.LimitExceeded
    This error message indicates that the distributed switch already has the maximum number of network resource pools. The maximum number for network resource pools on a vSphere Distributed Switch is 56.

    Workaround: None.

  • LLDP does not display system names for extreme switches
    By default, system names on extreme switches are not advertised. Unless a system name is explicitly set to advertise on the extreme switch, LLDP cannot display this information.

    Workaround: Run the configure lldp ports <port ID> advertise system-name command to advertise the system name on the extreme switch.

  • Truncating mirrored packets causes ESXi to fail
    When a mirrored packet is longer than the mirrored packet length set for the port mirroring session, ESXi fails. Other operations that truncate packets might also cause ESXi to fail.

    Workaround: Do not set a mirrored packet length for a port mirroring session.

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

  • vSphere DirectPath I/O With vSphere vMotion is disabled by VMCI-based applications
    When you use any VMCI-based application on a Cisco UCS system, DirectPath becomes inactive on all virtual machine network adapters.

    Workaround: Stop using all VMCI-based applications and reboot the virtual machine to restore vSphere DirectPath I/O.

  • Using the bundled Emulex BE2/BE2 NICs (be2net driver)
    When using vSphere 5.0 with Emulex BE2/BE3 NICs (be2net driver) in a HP FlexFabric/Flex-10 or IBM Virtual Fabric Adapter (VFA) environment, connectivity may not work properly on Windows VMs or the server when VLANs are configured.

    Workaround: Do not use the driver bundled with vSphere 5.0. Before upgrading to vSphere 5.0, please obtain an updated driver from Emulex, HP, or IBM that should be used on HP FlexFabric/Flex-10 or IBM VFA systems.

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

  • ESXi cannot distinguish between thick provision lazy zeroed and thick provision eager zeroed virtual disks on NFS datastores with Hardware Acceleration support
    When you use NFS datastores that support Hardware Acceleration, the vSphere Client allows you to create virtual disks in Thick Provision Lazy Zeroed (zeroedthick) or Thick Provision Eager Zeroed (eagerzeroedthick) format. However, when you check the disk type on the Virtual Machine Properties dialog box, the Disk Provisioning section always shows Thick Provision Eager Zeroed as the disk format no matter which format you selected during the disk creation. ESXi does not distinguish between lazy zeroed and eager zeroed virtual disks on NFS datastores.

    Workaround: None.

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

  • An NFS datastore with adequate space displays out of space errors
    This problem happens only when you use Remote Procedure Calls (RPC) client sharing and mount multiple NFS volumes from the same NFS server IP address. In this configuration, when one of the NFS volumes runs out of space, other NFS volumes that share the same RPC client might also report no space errors.

    Workaround: Disable RPC client sharing on your host by performing this task:

    1. In the vSphere Client inventory panel, select the host.
    2. Click the Configuration tab, and click Advanced Settings under Software.
    3. Click NFS in the left panel and scroll down to NFS.MaxConnPerIP on the right.
    4. Change the default value to 128.

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

  • After reboot, stateless host cannot detect iSCSI datastores
    If a stateless host is added to the Cisco Nexus 1000V Series Switch and configured with MTU of 9000, then after reboot, the host cannot detect iSCSI datastores even though it is able to discover the corresponding devices.

    Workaround: To make the datastores visible, click Refresh on the Configuration > Storage screen of the vSphere Client.

Server Configuration Issues
  • A change SATP-PSP to rule for host profiles applied to ESXi host is not reflected in the host after reboot
    After the SAN Array Type Plugin Path Selection Policy (SATP PSP) rule and applying the change and rebooting a host provisioned with Auto Deploy, this new change is not reflected in the SATP PSP for each of the devices. For ESXi hosts not provisioned with Auto Deploy, the SATP PSP change is correctly updated in the host. However, a compliance check of the ESXi host fails compliance check with the host profile.

    Workaround: After applying the host profile to the ESXi host, delete the host profile and extract a new host profile from the ESXi host, then attach it to the host before rebooting. To do this, use the Update from Reference Host feature in the Host Profiles UI. This task deletes the host profile and extracts a new profile from the host while maintaining all the current attachments.

    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.

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

  • A host profile fails to apply if syslog logdir set to datastore without a path
    If the esxcli command or vSphere Client is used to set the syslog directory to a datastore without an additional path, a host profile extracted from that system fails to apply to other hosts.

    For example, the following configures the system in a way that triggers this condition:
    esxcli system syslog config set --logdir /vmfs/volumes/datastore1

    Similarly, setting the Syslog.global.logDir to datastore1 in the Advanced Settings dialog of the host's Configuration tab also triggers this condition.

    Workaround:Perform one of the following:

    • Modify Syslog.global.logDir in the Advanced Settings dialog to have a value of "DATASTORE_NAME /" instead of "DATASTORE_NAME" before extracting the host profile.
    • Edit the host profile such that the Advanced configuration option for Syslog.global.logDir has a value of "DATASTORE_NAME /" instead of "DATASTORE_NAME".

  • Applying a host profile might recreate vSwitches and portgroups
    The vSwitches and portgroups of a host might be recreated when a host profile is applied. This can occur even if the host is compliant with the host profile.

    This occurs when the portgroupprofile policy options are set to use the default values. This setting leads to an issue where the comparison between the profile and the host configuration might incorrectly fail when the profile is applied. At this time, the compliance check passes. The comparison failure causes the apply profile action to recreate the vSwitches and portgroups. This affects all subprofiles in portgroupprofile.

    Workaround: Change the profile settings to match the desired settings instead of selecting to use the default.

  • VMware embedded SNMP agent reports incorrect software installed date through hrSWInstalledTable from HOST-RESOURCES-MIB
    When you poll for installed software (hrSWInstalledTable RFC 2790) by using the VMware embedded SNMP agent, the installation date shown for user-installed software is not correct, because the hrSWInstalledTable from HOST-RESOURCES-MIB reports hrSWInstalledDate incorrectly.

    Workaround: To retrieve the correct installation date, use the esxcli command esxcli software vib list.

vCenter Server and vSphere Client Issues
  • New The embedded database provided with the vCenter Server Appliance supports an inventory with a maximum of 5 hosts and 50 virtual machines
    The embedded database is not configured to manage an inventory that contains more than 5 hosts and 50 virtual machines. If you use the embedded database with the vCenter Server Appliance, exceeding these limits can cause numerous problems, including causing vCenter Server to stop responding.

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

    1. Open the Global Storage Settings panel by opening the following URL in your Web browser: http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager03.html
    2. Set the slider to Unlimited.
    3. Open the Website Storage Settings panel by opening the following URL in your Web browser: http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager07.html
    4. Select the URL for the vSphere Web Client in the Visited Websites list.
    5. Set the slider to Unlimited.

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

  • The snmpwalk command returns an error message when you run it without using -t option
    When the snmpwalk command is run without using the -t and -r options for polling SNMP data, the VMware embedded SNMP agent does not show complete data and displays the error message, No response from host.

    Workaround: When you run the snmpwalk command, use the -t option to specify the timeout interval and the -r option to set the number of retries. For example: snmpwalk -m all -c public -v1 host-name -r 2 -t 10 variable-name.

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

  • An error occurs when backing up inventory services data in the vCenter Server Appliance
    When you run the /usr/lib/vmware-vpx/inventoryservice/scripts/backup.sh script to back up inventory services data in the vCenter Server Appliance, it might fail with the error message, Java HotSpot(TM) 64-bit Server VM warning: Attempt to allocate stack guard pages failed. This error occurs when the vCenter Server Appliance is low on memory and JVM cannot allocate enough memory to start the process.

    Workaround: Increase system RAM for the vCenter Server Appliance.

  • Restarting vpxd in the vCenter Server Appliance fails with a database error
    On a vCenter Server Appliance with an embedded database, restarting vpxd might fail. An error message similar to the following appears in the vpxd.log file:
    Alert:false@ /build/mts/release/bora-336896/bora/vpx/vpxd/util/vpxdVdb.cpp:403

    This error occurs if the system clock on the vCenter Server Appliance is reset to a time earlier than the time at which the database was created. This results in the database objects created by the vCenter Server Appliance having time stamps that appear to be in the future. This causes queries for database objects to fail.

    You might encounter this error during Active Directory configuration if the clock on the Active Directory domain controller is set to an earlier time than the clock on the vCenter Server Appliance, because during the configuration, the vCenter Server Appliance clock is synchronized to the clock on the Active Directory domain controller.

    Workaround: After configuring the embedded database, do not set the system clock on the vCenter Server Appliance to an earlier time. When configuring Active Directory, ensure that the clock on the Active Directory domain controller is not set to a time earlier than the clock on the vCenter Server Appliance.

  • The vCLI command to clear the embedded SNMP agent configuration resets the source of indications and clears trap filters
    The vicfg-snmp -r vCLI command to clear the embedded SNMP agent configuration resets the source of events or traps to the default, indications, and clears all trap filters.

    Workaround: None.

  • Enabling the embedded SNMP agent fails with Address already in use error
    When you configure a port other than udp/161 for the embedded SNMP agent while the agent is not enabled, the agent does not check whether the port is in use. This might result in a port conflict when you enable the agent, producing an Address already in use error message.

    Workaround: Enable the embedded SNMP agent before configuring the port.

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

    1. Select Start > Programs > Administrative Tools > Services.
    2. 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.

  • The VMware vCenter Server Appliance Web console has options for configuring IPv6 even though IPv6 is not supported
    Although the VMware vCenter Server Appliance does not support IPv6, the Network tab of the VMware vCenter Server Appliance Web console has a configuration option for IPv6 and will, by default, assign an IPv6 address to the appliance if a DHCPv6 server is on the network.

    Workaround: Enter an invalid static IPv6 address for the VMware vCenter Server Appliance to prevent the appliance from obtaining an IPv6 address through DHCP.

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

    1. Go to http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager07.html and ensure that the amount of storage is set to a value other than None.
    2. If you are using the Firefox browser, set the browser history settings:
      1. Select Tools > Options.
      2. Click Privacy.
      3. Select an option other than Never remember history.

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

    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 Windows TEMP 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 the TEMP 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.

  • Search in the vSphere Client or vSphere Web Client shows out-of-date results or times out
    When you search the inventory in the vSphere Client or vSphere Web Client, the search might show out-of-date information, or, in the case of the vSphere Web Client, might time out.

    The following error message indicating an unexpected runtime error appears in the Inventory Service log file, ds.log:
    [2011-06-27 18:04:25,367 pool-14-thread-5 ERROR
    com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl] Unexpected runtime exception:
    com.xhive.error.XhiveInterruptedException: INTERRUPTED

    Workaround: Restart the Inventory Service.

    For a vCenter Server system running on Windows, perform the following steps:

    1. Start the Windows Service Manager:
      1. Select Start > Run.
      2. Type services.msc.
    2. Right-click vCenter Inventory Service and select Restart.

    For the vCenter Server Appliance, perform the following steps:
    1. Log in to the VMware vCenter Server Appliance Web console.
    2. On the vCenter Server tab, select Status.
    3. Click Stop vCenter.
    4. Click Start vCenter.

Virtual Machine Management Issues
  • Driver availability for xHCI controller for USB 3.0 devices
    Virtual hardware version 8 includes support for the xHCI controller and USB 3.0 devices. However, an xHCI driver might not be available for many operating systems. Without a driver installed in the guest operating system, you cannot use USB 3.0 devices. No drivers are known to be available for the Windows operating system at this time. Contact the operating system vendor for availability of a driver. When you create or upgrade virtual machines with Windows guest operating systems, you can continue using the existing EHCI+UHCI controller, which supports USB 1.1 and 2.0 devices for USB configuration from an ESXi host or a client computer to a virtual machine. If your Windows virtual machine has xHCI and EHCI+UHCI USB controllers, newly added USB 1.1 and USB 2.0 devices will be connected to xHCI and will not be detected by the guest.

    Workaround: Remove the xHCI controller from the virtual machine's configuration to connect USB devices to EHCI+UHCI.

  • Linux kernels earlier than 2.6.27 do not report nonpowers of 2 cores per socket
    Beginning with ESXi 5.0, multicore virtual CPU support allows nonpowers of 2 cores per socket values. Linux kernels earlier than 2.6.27 report only powers of 2 values for cores per socket correctly. For example, some Linux Guest operating systems might not report any physical ID information when you set numvcpus = 6 and cpuid.coresPerSocket = 3 in the .vmx file. Linux kernels 2.6.28 and later report the CPU and core topology correctly.

    Workaround: None

  • When you hot add memory to virtual machines with Linux 64 bit or Windows 7, 32-bit guest operating systems, you cannot increase existing virtual memory to more than 3GB
    The following conditions apply to hot adding memory to virtual machines with Linux 64 bit or Windows 7 32 bit guest operating systems.

    • If the powered-on virtual machine has less than 3GB of memory, you cannot hot add memory in excess of 3GB.
    • If the virtual machine has 1GB, you can add 2GBs.
    • If the virtual machine has 2GB, you can add 1GB.
    • If the virtual machine has 3444MB of memory, you can add 128MB.
    • If the powered-on virtual machine has exactly 3GB memory, you cannot hot add any memory.

    If the powered-on virtual machine has more than 3GB of memory, you can increase the virtual machine memory to 16 times the initial virtual machine power-on size or to the hardware version limit, whichever is smaller. The hardware version limit is 255GB for hardware version 7 and 1011GB for hardware version 8.

    Linux 64 bit and 32 bit Windows 7 guest operating systems freeze when memory grows from less than or equal to 3GB to greater than 3GB while the virtual machine is powered on. This vSphere restriction ensures that you do not trigger this bug in the guest operating system.

    Workaround: None.

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

  • Hot-adding memory to a Windows 2003 32-bit system that uses the November 20, 2007 LSISAS driver can cause the virtual machine to stop responding
    The November 20th, 2007 LSI-SAS driver cannot correctly address memory above 3GB if such memory is not present at system startup. When you hot-add memory to a system that has less than 3GB of memory before the hot-add, but more than 3GB of memory after hot-add, the Windows state is corrupted and eventually causes Windows to stop responding.

    Workaround: Use the latest LSI SAS driver available from the LSI website. Do not use the LSISAS1068 virtual adapter for Windows 2003 virtual machines.

  • Incorrect IPv6 address appears on the Summary tab on MacOS X Server 10.6.5 and later guest operating systems
    When you click View All on the Summary tab in the vSphere Client, the list of IPv6 addresses includes an incorrect address for the link local address. You see the incorrect address when you run the ifconfig file and compare the output of the command with the list of addresses in the vSphere Client. This incorrect information also appears when you run the vim-cmd command to get the GuestInfo data.

    Workaround: None

  • Creating a large number of virtual machines simultaneously causes file operations to fail
    When you create a large number of virtual machines simultaneously that reside within the same directory, the storage system becomes overwhelmed and some file operations fail. A vim.fault.CannotAccessFile error message appears and the create virtual machine operation fails.

    Workaround: Create additional virtual machines in smaller batches of, for example, 64, or try creating virtual machines in different datastores or within different directories on the same datastore.

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

  • The VMware Tools system tray icon might incorrectly show the status as Out of date
    If a virtual machine is using VMware Tools that was installed with vSphere 4.x, the system tray icon in the guest operating system incorrectly shows the status as Out-of-date. In the vSphere 5.0 Client and vSphere Web Client, the Summary tab for the virtual machine shows the status as Out-of-date (OK. This version is supported on the existing host, but upgrade if new functionality does not work). VMware Tools installed with vSphere 4.x is supported and does not strictly require an upgrade for vSphere 5.0.

    Workarounds: In vSphere 5.0, use the Summary tab for the virtual machine in the vSphere Client or the vSphere Web Client to determine the status of VMware Tools. If the status is Out-of-date and you do not want to upgrade, you can use the following settings to disable the upgrade prompts and warning icon in the guest operating system:

    • If the virtual machine is set to automatically upgrade VMware Tools but you want the virtual machine to remain at the lowest supported version, set the following property as an advanced configuration parameter: set tools.supportedOld.autoupgrade to FALSE. This setting also disables the exclamation point icon in the guest, which indicates that VMware Tools is unsupported.
    • If VMware Tools is out of date and you want to disable the exclamation mark icon that appears on the VMware Tools icon in the system tray, set the following property as an advanced configuration parameter: set tools.supportedOld.warn to FALSE.

    Neither of these settings affect the behavior of VMware Tools when the Summary tab shows the status as Unsupported or Error. In these situations, the exclamation mark icon appears and VMware Tools is automatically upgraded (if configured to do so), even when the advanced configuration settings are set to FALSE. You can set advanced configuration parameters either by editing the virtual machine's configuration file, .vmx or by using the vSphere client or the vSphere Web Client to edit the virtual machine settings. On the Options tab, select Advanced > General, and click Configuration Parameters.

  • Check and upgrade Tools during power cycling feature does not work in ESXi 5.0
    In ESX/ESXi 4.1, the Check and upgrade Tools during power cycling option was available to upgrade VMware Tools when the virtual machine shut down. This feature does not work in ESXi 5. Ignore any documentation procedures related to this feature.

    Workaround: Install VMware Tools manually.

  • Mac OS X guest operating systems with high CPU and memory usage might experience kernel panic during virtual machine suspend or resume or migration operations
    Following virtual machine suspend or resume operations or migration with vMotion on a host under a heavy CPU and memory load, the Translation Lookaside Buffer (TLB) invalidation request might time out. In such cases, the Mac OS X guest operating system stops responding and a variant of one of the following messages is written to the vmware.log file:
    The guest OS panicked. The first line of the panic report is: Panic(CPU 0): Unresponsive processor
    The guest OS panicked. The first line of the panic report is: panic(cpu 0 caller 0xffffff8000224a10): "pmap_flush_tlbs()timeout: " "cpu(s) failing to respond to interrupts,pmap=0xffffff800067d8a0 cpus_to_respond=0x4"@/SourceCache/xnu/xnu-1504.7.4/osfmk/x86_64/pmap.c:2710

    Workaround: Reduce the CPU and memory load on the host or reduce the virtual CPU count to 1.

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

  • Storage misconfigurations can prevent USB devices from connecting to virtual machines
    USB devices that connect from an ESXi host to a virtual machine might not be available to add to the virtual machine if you have storage misconfigurations. Misconfigurations on the host can cause long rescan times during startup, which make USB devices connected to the host appear to be unavailable for passthrough to the virtual machine. For example, if a SendTargets, or dynamic discovery, address on the system does not exist or isn't responding, a discovery timeout occurs. Also, an iSCSI misconfiguration can cause delays of between one and two minutes because of TCP timeouts.

    Workaround: Fix the misconfiguration, then use the service mgmt-vmware restart command to restart hostd.

  • Cannot set VMware Tools custom scripts through VMware-Toolbox UI in Linux guest operating system when the custom scripts contain non-ASCII characters in their path
    Non-ASCII characters appear as square boxes with an X in them in the VMware Tools Properties window in Linux guest operating systems when the system locale is zh_CN.gb18030, ja_JP.eucjp, or ko_KR.euckr. In such cases, you cannot set custom VMware Tools scripts .

    Workaround: Perform one of the following tasks:

    • Change the directory name where custom VMware Tools scripts are located so that it contains ASCII characters only.
    • Set custom VMware Tools scripts by entering the vmware-toolbox-cmd script command at a shell prompt.

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

  • Windows 7 SMP virtual machine with low memory limit stops responding and displays an error message on a blue screen
    If an SMP virtual machine with a Windows 7 guest operating system has a memory limit that is 50 percent less than the virtual machine RAM size, and is running on an ESXi host with overcommitted memory and CPU, the virtual machine might stop responding. When these conditions exist and you perform a migration with vMotion or a suspend or resume operation, a blue screen appears with the following or a similar STOP error message:
    *** STOP: 0x0000007E
    *** STOP: 0x0000008E

    Workaround: Disable memory limits for the virtual machine or set a higher memory limit.

  • VMware embedded SNMP agent reports incorrect status for processors in the hrDeviceStatus object of the HOST-RESOURCES-MIB module
    When reporting the system details, the VMware embedded SNMP agent shows an incorrect status for processors. The SNMP agent reports the processor status as Unknown for the hrDeviceStatus object in HOST-RESOURCES-MIB. The ESX/net-snmp implementation of HOST-RESOURCES-MIB does not return the hrDeviceStatus object, which is equivalent to reporting an unknown status.

    Workaround: Use either CIM APIs or SMBIOS data to check the processor status.

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

  • A virtual machine fails to power on after migrating from ESXi 5.0 to ESX/ESXi 3.5 when disk hot-add is used on ESXi 5.0
    When a disk device is hot-added to a hardware version 4 virtual machine on a ESXi 5.0 host, the virtual machine fails to power on after it is migrated to an ESX/ESXi 3.5 host. The ESX/ESXi 3.5 host logs an error similar to [msg.scsi.esx.filters] scsi0:1 device filters are not supported. The error occurs because the ESXi 5.0 host erroneously adds an empty SCSI filter setting to the virtual machine configuration.

    Workaround: Remove any disk filter lines from the virtual machine .vmx configuration file by performing the following actions:

    1. Unregister the virtual machine.
    2. Open the virtual machine config file in a text editor.
    3. Remove any lines containing scsiX:Y.filters.
    4. Save the virtual machine config file.
    5. Register the virtual machine.
    6. Power on the virtual machine.

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

  • After powering off an FT Primary VM, removing its Secondary VM's host from a vDS fails.
    If you power off an FT virtual machine, the shadow dvPorts used by its Secondary VM still exist in vmkernel. This prevents the host the Secondary VM was running on from being removed from the vDS.

    Workaround: To remove the host from the vDS, you can reboot the host. After the reboot, the shadow ports are removed.

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

Guest Operating System Issues
  • PXE boot or reboot of RHEL 6 results in a blank screen
    When you attempt to use the Red Hat boot loader to PXE boot into RHEL 6 in an EFI virtual machine, the screen becomes blank after the operating system is selected. This problem is also seen if you remove the splashscreen directive from the grub.conf file in a regular installation of RHEL 6 and reboot the virtual machine.

    Workaround: Verify that the splashscreen directive is present and references a file that is accessible to the boot loader.

  • Multiple vNICs randomly disconnect upon reboot for Mac OS X 10.6.x
    When rebooting the Mac OS X 10.6, an incorrect guest link state is shown for n >=3 e1000 vNICs.

    If n(e1000)=3, the guest link state is: 2(Connected), 1 (disconnected).
    If n(e1000)=5, the guest link state is: 3(Connected), 2(disconnected), and so on.

    Workaround: Manually activate and deactivate the adapters with the ifconfig utility. The manual activation and deactivation will not persist through the next reboot process.

Supported Hardware Issues
  • IBM x3550 M2 Force Legacy Video on Boot must be disabled
    The IBM x3550 M2 has a firmware option called Force Legacy Video on Boot that enables legacy INT10h video support when booting from the Unified Extensible Firmware Interface (UEFI). This option is not compatible with ESXi 5.0 and must be disabled.

    Workaround: When booting the IBM x3550 M2 from UEFI, press F1 to enter the firmware setup and select System Settings > Legacy Support > Force Legacy Video on Boot and click Disable.

Internationalization Issues
  • 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:

    1. Open the file vSphere_Web_Client_Installation_Directory\springsource-dm-server-2.0.4\config\tomcat-server.xml using a text editor.
    2. 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"/>
    3. 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"/>
    4. Save the file.

Miscellaneous Issues
  • Location of log files has changed from /var/log to /var/run/log
    ESXi 5.0 log files are located in /var/run/log. For backwards compatibility, the log file contains links from the previous location, /var/log, to the most recent log files in the current location, /var/run/log. The log file does not contain links to rotated log files.

    Workaround: None.

  • On Linux virtual machines, you cannot install OSPs after uninstalling VMware Tools with the tar installer
    After you uninstall VMware Tools that were installed with the tar installer on a Linux virtual machine, files are left on the system. In this situation, you cannot install OSPs.

    Workaround: Run the following command: rm -rf /usr/lib/vmware-tools /etc/vmware-tools

  • When proxy server is enabled in Internet Explorer LAN settings, PowerCLI sometimes fails to add an online depot
    An online depot can be added in PowerCLI using the Add-ESXSoftwareDepot cmdlet. Under certain conditions in which the proxy server is enabled for the machine being used, PowerCLI fails to add the online depot in its session.

    This failure can occur only if all the following conditions exist.

    • The customer's site requires an HTTP proxy for accessing the Web.
    • The customer hosts a depot on their internal network.
    • The customer's proxy cannot connect to the depot on the internal network.

    Workaround: Disable proxy server in the IE LAN settings. Add the online depot in PowerCLI.