Issues known to occur after upgrading vSphere 4.1 Update 2 to vSphere 5.0 (2007404)
The following issues are known to occur after you upgrade from ESX/ESXi 4.1 Update 2 to ESXi 5.0. These issues are resolved in vSphere 4.1 Update 2, but not in vSphere 5.0.
- Windows guest operating systems display incorrect NIC device status after a virtual hardware upgrade
When you upgrade ESX host from ESX 3.5 to ESX 4.1 along with the hardware version of the ESX from 4 to 7 on Windows guest operating systems, the device status of the NIC is displayed as This hardware device is not connected to the computer (Code 45).
- After you install VMware Tools on a virtual machine with Windows NT 4.0 operating system, the vSphere Client displays the VMware Tools status as VMware Tools: Out of date.
- Modifying snapshots using the commands vim-cmd vmsvc/snapshot.remove or vim-cmd vmsvc/snapshot.revert fails when applied against certain snapshot tree structures.
- Cannot add a USB device to a virtual machine. For more information, see Unable to add a USB device to a virtual machine (1039359).
- In vCenter, a cloned virtual machine displays Windows 2000 as the guest operating system instead of Windows 2000 Professional.
- Mouse movements in VMware View might cause SVGA messages similar to the following to be repeatedly written to vmware.log:
May 02 12:01:28.464: mks| SVGA: Restoring cursor bypass 3 from vm which took 3->2->3 roundtrip
May 02 12:01:30.468: mks| SVGA: Restoring cursor bypass 3 from vm which took 3->2->3 roundtrip
The I/O generated by this repeated logging might generate increased load on storage systems.
- Memory Hotplug feature does not work on SLES 11 32-bit guest operating systems.
- An issue in the DHCP client might cause the DHCP client to send DHCPRELEASE messages using the broadcast MAC address of the server. However, the release messages might be dropped by an intermediate DHCP proxy router. Eventually the DHCP server runs out of IP addresses.
- RefreshDatastore API does not display any error when invoked on a datastore that is offline.
- Customization of the hot clone of a Windows 2008 R2 guest operating system fails with an auto check not found error message, and the virtual machine reboots continuously.
- Network connectivity might fail if VLANS and PVLANs are configured on the same vNetwork Distributed Switch.
- Purple diagnostic screen with vShield or third-party vSphere integrated firewall products. For more information, see ESX/ESXi 4.1 host fails with a purple diagnostic screen: #PF Exception 14 mentioning DVFilterSocketAcceptTcpip and vmk_accept (2004893).
- vSphere Client and vSphere PowerCLI might not display the service tag of ESX/ESXi hosts if the hosts are not based on Dell hardware platforms.
- Updates openldap and openldap-client RPMs.
- VMware hostd service might fail during a quiesced snapshot operation.
- VMware Tool upgrade fails as some folders in /tmp are deleted in some Linux guest operating systems.
- ESX/ESXi hosts that have passive MSCS nodes and RDM LUNs might take a long time to restart.
VMkernel log of the ESX/ESXi host might display messages similar to:
Sep 24 12:25:36 cs-tse-d54 vmkernel: 0:00:01:57.828 cpu0:4096)WARNING: ScsiCore: 1353: Power-on Reset occurred on naa.6006016045502500176a24d34fbbdf11
Sep 24 12:25:36 cs-tse-d54 vmkernel: 0:00:01:57.830 cpu0:4096)VMNIX: VmkDev: 2122: Added SCSI device vml0:3:0 (naa.6006016045502500166a24d34fbbdf11)
Sep 24 12:25:36 cs-tse-d54 vmkernel: 0:00:02:37.842 cpu3:4099)ScsiDeviceIO: 1672: Command 0x1a to device "naa.6006016045502500176a24d34fbbdf11" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0
- If the virtual machine configured in the recovery plan of VMware vCenter Site Recovery Manager (SRM) uses one or more Raw Device Mapping (RDM) files and the pointer file is in a folder other than the home folder, or if the pointer file is in the home folder and the virtual machine's hard disk is in a folder other than the home folder, VMware vCenter SRM failover fails and SRM logs contains entries similar to:
[2011-05-05 09:26:35.756 22348 verbose 'RSVm-49592-Task'] Error set to (vim.fault.InvalidDeviceBacking)
- If the embedded SNMP agent of an ESX/ESXi host is enabled and SNMP queries are sent using the VMWARE-VMINFO-MIB.mib MIB file to virtual machines that are being migrated, cloned, created, or destroyed, the ESX/ESXi host might stop responding.
- In vCenter Server 5.0, the Message of the day text box does not allow you to type more than 1024 characters.
- After applying a host profile that configures a host to join an Active Directory domain by right-clicking the host and selecting Host Profile > Apply Profile in the Host and Clusters view, if you enter the credentials to make the host join the domain, the Apply Profile window does not display any information. Clicking Finish has no response, and when you click Cancel the window closes.
- When a host in the vSphere Client inventory is put in standby mode and vCenter Server is re-started, you might be able to browse the local datastore of the host. However, the contents of the datastore cannot be viewed. Sometimes shared datastore cannot be browsed if vCenter server has selected hosts in standby mode.
- When you try to rename a folder in the VMs and Templates view of vSphere Client on a VMware HA/DRS enabled system that has large number of users logged in, then some virtual machines might incorrectly get renamed instead of the target folder. The Recent Tasks panel indicates that the Rename virtual machine task was recently run. This issue occurs on VMware HA/DRS enabled systems that generate too many events causing the vSphere Client to refresh its inventory view while you are trying to rename a folder.
- If the interval period of a task scheduled to export virtual machines is more than 999 and the task is executed for the first time or when the VMware Virtual Center Server service is restarted, the Recent Tasks pane gets filled with entries of the scheduled task. Removing the queued tasks might result in an Invalid argument error.
- The Windows System Up Time counter is reset to zero when the system runs continuously for 49.7 days. If you have more than one DRS cluster where one or more cluster is created or enabled before the counter resets and one or more cluster is created or enabled after the counter resets, then when DRS is started to provide recommendations for tasks such as powering on a virtual machine, but it has not collected enough statistics from the newly created clusters, vCenter Server might fail. In such a situation, the following error message is recorded in the vpxd.log file:
- When you install ESXi 5.0 on a system where ESX 4.x was installed earlier, while the ESX host is connected to vCenter Server, vSphere Client incorrectly displays service console memory in the Configuration tab for the ESXi host after reconnecting. The issue occurs because the vCenter Server retains a record of the previous ESX 4.x service console memory.
- After upgrading to vCenter Server 5.0 and vSphere Client 5.0, when vSphere Client is connected to vCenter Server, several windows might appear displaying an error message similar to:
A internal error occurred in the vSphere Client. Details: Object reference not set to an instant object.
The viclient.log file might contain errors similar to the following:
[viclient:Error :M: 6] 2010-09-23 10:21:53.272 UnhandledCallbackError in NotifyUpdates for server https://vcenter.usa-ed.net/sdk
System.NullReferenceException: Object reference not set to an instance of an object.
at VpxClient.VMList.OnUpdate(FilterUpdateArray fUpdates)
at VirtualInfrastructure.Updates.PollerDispatcherImpl.NotifyUpdates(Map`2 handler2Updates)
- During periods of intermittent network connectivity between ESX/ESXi hosts and vCenter Server, if vCenter Server attempts to collect performance statistics from a host that is not accessible, the statistics collection task remains in the pending state and no further statistics are collected for that host. This causes vCenter Server to show gaps in performance data for the inaccessible ESX/ESXi hosts.
The vpxd.log files might contain entries similar to:
[VpxdMoHost::CollectRemote] Attempt to collect stats on <Host_Name> [VpxdMoHost::CollectRemote] Not collecting stats this time on host <Host_Name> because collection pending Had to drop performance data coming from host <Host_Name> because it has error (The specified network name is no longer available.)
- When a virtual machine with snapshots is migrated to another ESX/ESXi host, a mismatch of the snapshot object ID in the vCenter database might cause vCenter to fail in reverting the virtual machine to the states of the snapshot and vSphere Client displays a message similar to:
This object has already been deleted or has not been completely created.
vCenter Server logs might contain entries similar to:
13421:[2011-03-08 09:50:53.257 02580 info 'App' opID=3DB842F7-0000013A] [VpxLRO] -- ERROR task-489263 -- vm-9273 -- vim.vm.Snapshot.revert: vmodl.fault.ManagedObjectNotFound:
13424- dynamicType = <unset>,
13425- faultCause = (vmodl.MethodFault) null,
13426: obj = 'vim.vm.Snapshot:snapshot-133808',
13427- msg = "",
- vCenter Server 5.0 does not support customization of SLES 11 SP2, Ubuntu 10.04, Ubuntu 10.10, and Ubuntu 11.04 guest operating systems.
No workarounds exist for these issues.
Note: VMware vCenter Server 5.0 Update 1 is now available, please reference the VMware vCenter Server 5.0 Update 1 Release Notes for information on resolved issues.