Search the VMware Knowledge Base (KB)
View by Article ID

Issues known to occur after upgrading vSphere 5.0 Update 2 to vSphere 5.1 (2040662)

  • 19 Ratings


These issues are known to occur after you upgrade from ESXi 5.0 Update 2 to ESXi 5.1. These issues are resolved in vSphere 5.0 Update 2, but not in vSphere 5.1.
  • When upgrading to ESXi 5.1 using Update Manager, an error in understanding the disk partition type might cause the RDMs attached to Solaris virtual machines to be overwritten. This might result in loss of data on the RDMs.

  • When attempting to take a quiesced snapshot of a virtual machine, if the snapshot operation fails towards the end of its completion, the redo logs created as part of the snapshot are not consolidated. The redo logs might consume a lot of data store space.

  • When attempting to upgrade ESX 4.1 Classic to ESXi 5.1 which has extended partitions, the ESX host fails to detect the extended partitions and might not upgrade it.

  • When using the Multiple-NIC vMotion feature with vSphere 5, if vMotion operations continue for a long time, unicast flooding is observed on all interfaces of the physical switch. Approximately 5 minutes after vMotion starts, the source and destination host start receiving high amounts of network traffic.

  • If a file's metadata is corrupted on a VMFS-3 Volume, the ESXi host might fail with a purple diagnostic screen while trying to access such a file. VMFS file corruptions are extremely rare but can be caused by external storage issues.

  • If an independent disk is deleted from a virtual machine, attempts to create a quiesced snapshot of a virtual machine might fail as the disk mode data for a given SCSI node might be stale. An error message might be displayed similar to:

    Status: An error occurred while quiescing the virtual machine. See the virtual machine's event log for details.

    The log files may contain entries similar to:

    ToolsBackup: changing quiesce state: STARTED -> DONE
    SnapshotVMXTakeSnapshotComplete done with snapshot 'back': 0
    SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Failed to quiesce the virtual machine. (40).

  • Attempts to PXE boot virtual machines that use the VMXNet3 network adapter by using the Microsoft Windows Deployment Services (WDS) might fail with messages similar to:

    Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
    1. Insert your Windows installation disc and restart your computer.
    2. Choose your language setting, and then click "Next."
    3. Click "Repair your computer."
    If you do not have the disc, contact your system administrator or computer manufacturer for assistance.
    Status: 0xc0000001
    Info: The boot selection failed because a required device is inaccessible

    To work around this issue in the event you cannot upgrade, removing the VMXNet 3 network adapter from the virtual machine. Click OK to reconfigure the VM. This flushes the MAC address of the virtual machine. Once complete, add a VMXNET3 back to the virtual machine and click OK. Power on the virtual machine and it should be able to boot from PXE.

  • When you add a virtual disk to a virtual machine that resides on a Storage DRS enabled datastore and the size of the virtual disk is greater than the free space available in the datastore, SDRS might migrate another virtual machine out of the datastore to allow sufficient free space to add the virtual disk. The Storage vMotion operation completes but the subsequent addition of a virtual disk to the virtual machine might fail and you may see an error similar to:

    Insufficient Disk Space

These issues are known to occur after you upgrade from vCenter Server 5.0 Update 2 to vCenter Server 5.1. These issues are resolved in vSphere 5.0 Update 2, but not in vSphere 5.1.
  • You are unable to migrate virtual machines between hosts if the virtual machine is connected to a vDS without any uplinks.

  • Some virtual machines might display a red warning icon in the inventory. However, the Alarms tab for the virtual machine does not indicate any alarm being triggered. This can appear for powered on and powered off virtual machines.

  • Attempts to clone a vApp that uses a storage cluster might fail with the error:

    An internal error occurred in the vSphere Client. Details: Object Reference not set to an instance of an object.

    However, if you select the Disable Storage DRS for this virtual machine option during the cloning process, the clone operation succeeds.

  • When you attempt to edit the settings of a Storage DRS cluster, or when you click on SDRS scheduling settings, you may see the error:

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

  • You might not be able to edit the settings of a virtual machine that is a member of a datastore cluster by using a user account that does not have configure a datastore cluster permission in vCenter Server, but has full permissions at the virtual machine level. This error is displayed:

    Permission to perform this operation was denied.
    You do not hold privilege "Datastore cluster > Configure a datastore cluster on Datastore cluster Cluster Name"

  • Storage related operations such as cold migration, storage vMotion, and cloning of a virtual machine with IDE disks and change block tracking enabled, fail at 99% when you are using vCenter 5.1 to manage ESXi/ESX 4.x hosts. This error is displayed in the GUI:

    A general system error occurred: Configuration information is inaccessible.

  • In a Linked Mode environment, attempting a storage vMotion operation on a virtual machine managed by a vCenter Server instance other than the vCenter Server that the user is logged into might result in an error similar to:

    The object has already been deleted or has not been completely created." or " Call
    PropertyCollector.RetrieveContents" or object "propertyCollector" on vCenter Server
    XXXXXXXX failed."

  • vCenter Service status displays a warning related to performance statistics rollup:

    Performance Statistics rollup from Past xxx to Past xxx is not occurring in the database

    This issue occurs if the statistics collection for one or more interval durations is disabled in the vCenter Server settings. In this case, the warning is triggered when the rollup jobs for the disabled interval run, but do not produce any results.

  • Attempting to save a domain name starting with a digit in the host profile fails.

  • When you clone a virtual machine through the Web Client, you have the option to edit the hardware of the destination virtual machine. If you choose to edit a disk and adjust its size, the disk of the resulting virtual machine points back to the source virtual machine's disk. This results in the destination virtual machine using the source virtual machine's disk.

  • When you add a user profile or user group profile in a host profile for ESX 4.x hosts, you are unable to access this user profile or user group profile. You see an error similar to:

    Call "HostProfile.RetrieveDescription" for object "Hostname-xxxx" on vCenter Server "Vcenterhostname-xxx" failed".

  • When running vCenter Server Appliance 5.1, you may experience these symptoms:
    • The vCenter Service Status tab in the vSphere Client shows one or more warnings related to the vCenter Server database.
    • You see one of these warnings in the vCenter Service Status tab:
      • Performance statistics rollup from Past Day to Past Week is not occurring in the database.
      • Performance statistics rollup from Past Week to Past Month is not occurring in the database.
      • Performance statistics rollup from Past Month to Past Year is not occurring in the database.
    • The performance graphs appear to function without any issues.

  • Virtual machines are incorrectly shown as being managed by VMware vCenter Site Recovery Manager. After a failover from production site (a) to recovery (b), the virtual machines at the new production site (b) might be shown as being managed by VMware vCenter Site Recovery Manager in the Summary tab. This issue is resolved in vCenter Server 5.1 Update 1 and vCenter Server 5.0 Update 2.

  • After upgrading to vCenter Server to 5.0 Update 1a or 5.0 Update 1b, the search functionality might not work. This issue occurs when there is a large inventory in vCenter Server (more than 1000) and there are more than 1000 virtual machine snapshots.

  • If the physical NIC configuration in the host profile is set to fixed physical NIC configuration policy, and the host's physical NIC is set to auto negotiating at the same speed as that specified in the policy, the host profile compliance check reports the host as compliant instead of non-compliant.

  • During periodic validation of vCenter Server permissions, if one of the entities is invalid, vCenter Server goes into an infinite loop on that thread and becomes unresponsive.

  • The vSphere Client may stop responding when searching for virtual machines. After choosing to hide virtual machines from view (by unchecking Show VMs in Inventory under the View dropdown menu), the client might stop responding when:
    • You perform a search using the search box at the top right, then click a link in the search box results.
    • After selecting a host in the Hosts and Clusters view, you select the Virtual Machines tab and double-click any virtual machine in the list.
    • You click the Virtual Machines tab in the VMs and Templates view and double-click any virtual machine in the list.

  • vCenter Server 5.1 does not support customization of these guest operating systems:
    • Windows 8
    • Windows Server 2012
    • Ubuntu 12.04


Update History

01/23/2013 - removed issue from details for UCS blade. UCS Blade issue was wrong version of ESXi.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 19 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 19 Ratings