Search the VMware Knowledge Base (KB)
View by Article ID
VMware ESXi 5.0, Patch ESXi500-201203201-UG: Updates the VMware ESXi 5.0 esx-base vib (2010814)
Summaries and Symptoms
This patch updates the esx-base VIB to resolve the following issues:
- PR 711076: When you connect to an ESXi 5.0 host through Managed Object Browser (MOB), the VirtualMachineConfigSummary displays the CPU reservation value [virtualMachineConfigSummary.cpuReservation] and memory reservation value [virtualMachineConfigSummary.memoryReservation] for a virtual machine as Unset.
- PR 711546: 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.
- PR 712342: Cannot assign VMware vSphere Hypervisor license key to an ESXi host with pRAM greater than 32GB.
- PR 718677: An ESXi host might stop responding if you enable the embedded SNMP agent on the host and send SNMP queries using the VMWARE-VMINFO-MIB.mib MIB file to virtual machines that are being migrated, cloned, created, or deleted.
- PR 719472: 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" instead of OK even though VMware Tools are up-to-date.
- PR 719895: Unable to add a USB device to a virtual machine (KB 1039359).
- PR 721191: Modifying snapshots using the commands vim-cmd vmsvc/snapshot.remove or vim-cmd vmsvc/snapshot.revert
will fail when applied against certain snapshot tree structures.
This issue is resolved in this release. Now a unique identifier, snapshotId, is created for every snapshot associated to a virtual machine. You can get the snapshotId by running the command vim-cmd vmsvc/snapshot.get <vmid>. You can use the following new syntax when working with the same commands:
Revert to snapshot: vim-cmd vmsvc/snapshot.revert <vmid> <snapshotId> [suppressPowerOff/suppressPowerOn]
Remove a snapshot: vim-cmd vmsvc/snapshot.remove <vmid> <snapshotId>
- PR 724376: Data corruption might occur if you copy large amounts of data (more than 1GB) from a 64-bit Windows virtual machine to a USB storage device.
- PR 725429: Applying a host profile to an in-compliance host causes non-compliance (KB 2003472).
- PR 728257: On a pair of HA storage controllers configured for redundancy, if you take over one controller, the datastores that reside on LUNs on the taken over controller might show inactive and remain inactive until you perform a rescan manually.
- PR 730109: When you disconnect a storage cable from a ESXi 5.0 host, browse to the datastore created on this FC SAN using MOB (Managed Object Browser) and invoke the RefreshDatastore method on the MoRef (Managed Object Reference) of the defunct datastore,. the RefreshDatastore API does not display any error.
- PR 730117: In vCenter Server, a cloned Windows 2000 Professional virtual machine displays Windows 2000 as the guest operating system in the vmx file instead of Windows 2000 Professional.
- PR 731232: On ESXi 5.0 hosts, you cannot change default Storage Array Type Plugins (SATP) plugin for LSI Asymmetric Logical Unit Access (ALUA) supported arrays from VMW_SATP_LSI to VMW_SATP_ALUA.
- PR 731453: VMware Tools for hosts provisioned with Auto Deploy (KB 2004018).
- PR 734366: Purple diagnostic screen with vShield or third-party vSphere integrated firewall products (KB 2004893)
- PR 734707: Virtual machines on a vNetwork Distributed Switch (vDS) configured with VLANs might lose network connectivity upon boot if you configure Private VLANs on the vDS. However, disconnecting and reconnecting the uplink solves the problem.This issue has been observed on be2net NICs and ixgbe vNICs.
- PR 742242: XCOPY commands that VAAI sends to the source storage device might fail. By default, XCOPY commands should be sent to the destination storage device in accordance with VAAI specification.
- PR 746203: In rare instances, hostd might stop responding during a Network File Copy operation. This is usually triggered by environmental networking issues. Hostd logs messages similar to the following to /var/log/vmware/hostd in rapid succession (several times per millisecond) resulting in high CPU usage (80-100%):
[2010-12-14 13:15:39.238 F5135B90 warning 'Libs'] [NFC ERROR] NfcFssrvrRecv: failed with code = 9
[2010-12-14 13:15:39.238 F5135B90 info 'Libs'] NfcNetTcpRead: timed out waiting for data
These messages are logged until you restart hostd.
- PR 748656: ESXi 5.0 Update 1 adds support for Mac OS X Server Lion 10.7.2 and 10.7.3.
- PR 750460: Adding and removing a physical NIC might cause an ESXi host to fail with a purple screen. The purple diagnostic screen displays an error message similar to the following:
NDiscVlanCheck (data=0x2d16, timestamp=<value optimized out>) at bora/vmkernel/public/list.h:386
- PR 751803: When disks larger than 256GB are protected using vSphere Replication (VR), any operation that causes an internal restart of the virtual disk device causes the disk to complete a full sync. Internal restarts are caused by a number of conditions including any time:
- A virtual machine is restarted
- A virtual machine is vMotioned
- A virtual machine is reconfigured
- A snapshot is taken of the virtual machine
- Replication is paused and resumed
- PR 752307 ESXi host fails with a purple diagnostic screen when multiple processes access the same resource during Dentrycache initialization.
- PR 753294: On a 3D-enabled Windows 7 virtual machine that is running on an ESXi 5.0 host, non-ASCII characters on certain websites might appear garbled on Internet Explorer 9 browser. This issue is observed when you browse certain Asian websites.
- PR 754047: When you upgrade VMware Tools the upgrade might fail because, some Linux distributions periodically delete old files and folders in /tmp. VMware Tools upgrade requires this directory in /tmp for auto upgrades.
- PR 756741: This release adds support for Native Storage Drivers for Intel C600 series chipset.
- PR 760022: If you subscribe for an ESXi Server’s CIM indications from more that one client (for example, C1 and C2) and delete the subscription from the first Client (C1), the other client (C2) might fail to receive any indication notification from the host.
- PR 766179: ESXi host installed on a server with more than 8 NUMA nodes fails and displays a purple screen.
- PR 766797: When you run the Windows Remote Management (WinRM) enumerate operation for the class CIM_SoftwareIdentity on an ESXi 5.0 host installed with Dell OpenManage Server Administrator (OMSA) 6.5, the query might time out with an error message similar to the following:
The WinRM client can not complete the operation within the time specified. check if the machine name if valid and is reachable over the network
Error messages similar to the following are written to var/log/syslog.log:
2011-09-22T15:18:53Z sfcb-vmware_base: spGetMsg receiving from 50 4927-11 Resource temporarily unavailable
2011-09-22T15:18:53Z sfcb-vmware_base: rcvMsg receiving from 50 4927-11 Resource temporarily unavailable
2011-09-22T15:18:53Z sfcb-vmware_base: Timeout or other socket error
The query works when OMSA software is not installed.
- PR 768488: When a SCSI device goes into permanent device loss (PDL) state, all the virtual machines that use datastore(s) backed by that SCSI device are affected. Some third party HA solutions incorporate a VMX option where disk.terminateVMOnPDLDefault is equal to True. With this option the VMkernel will stop such affected virtual machines.
Starting with this release, when VMkernel stops affected virtual machines, a warning message similar to the following is logged in vmkernel.log once for each virtual machine.
WARNING: VSCSI: CompleteIOCommand:4033: handle 8193(vscsi0:1):opened by wid 4061 (vmm0:win2k3-sp1) has Permanent Device Loss. Killing world group with leader id <id>
- PR 769620: In vCenter Server, the vStorage APIs - Array Integration (VAAI) feature is not listed under Configuration > Licensed Features on the vSphere Client for vSphere Enterprise edition.
- PR 769677: If you perform a VMotion operation to an ESXi host on which the boot-time option "pageSharing" is disabled, the ESXi host might fail with a purple screen.
Disabling pageSharing severely affects performance of the ESXi host. Because pageSharing should never be disabled, starting with this release, the "pageSharing" configuration option is removed.
- PR 773187: On an ESXi host, if you configure the Network I/O Control (NetIOC) to set the Host Limit for Virtual Machine Traffic to a value higher than 2000Mbps, the bandwidth limit is not enforced.
- PR 773261: WSMan service reports Service Unavailable error if a parameter has arrays in WS-Management Invoke operation. WSMan service on an ESXi host does not support one-element array input parameters for performing an invoke operation.
- PR 773639: You cannot add an ESXi host to the Active Directory (AD) domain. When you attempt to join an ESXi 5.0 host to an AD environment through the vSphere Client, the task fails with an error message similar to the following:
Could not join <domainname>: The specified domain either does not exist or could not be contacted.
Starting with this release, the outbound TCP port 53 on the firewall of the ESXi host is enabled by default.
- PR 773769: An ESXi host halts and displays a purple diagnostic screen when using Network I/O Control with a Network Adapter that does not support VLAN Offload (KB 2011474).
- PR 774564: A third party client is able to perform operations that are reserved for paid licenses when a Hypervisor vRAM license is assigned to an ESXi host.
Starting with this release, third party clients are restricted from VIM API if the ESXi host is assigned with a hypervisor vRAM license.
- PR 774699: Continuing in this release vSphere Essentials for ROBO and vSphere Essentials Plus for ROBO can be managed by the following vCenter Server editions:
- VMware vCenter Server Standard
- VMware vCenter Server for Essentials
- VMware vCenter Server Foundation
- PR 775477: In certain situations, if an ESXi 5.0 host fails after you perform a provisioning operation on a virtual machine, the virtual machine might become orphaned after the host recovers. Attempts to power on the virtual machine fail with an error message similar to the following:
The power-on attempt for VM <VM name> failed because the VM was not found on the anticipated ESX host
This issue does not occur on stateless ESXi 5.0 hosts.
- PR 777175: A vMotion operation might fail with error messages similar to the following:
Failed to initialize migration at source. Error 0xbad00a4. VMotion failed to start due to lack of cpu or memory resources.
vMotion task failed - This host has reached its concurrent migration limit.
- PR 785619/816333: You may notice that sfcb-ProviderMa memory size is increasing. sfcb-ProviderMa process crashes when the memory size reaches memSizeLimit of 17920MB. CIM indications are stopped, and a message similar to the following indicating that the memSizeLimit is reached is written to vmkernel.log:
2011-12-04T10:49:41.852Z cpu4:3570)MemSched: vm 3570: UserReserveBStore:7987: Invalid memSize=17221 + memSizeResv=0 + nPages=1101 > memSizeLimit=17920
- PR 787746: If you hot-clone a virtual machine, the e1000e network adapter type on the cloned virtual machine changes to flexible if the Guest Operating System originally selected was Other > Other (64-bit).
- PR 788962: When an ESXi host encounters a corrupt VMFS volume, VMFS driver might leak memory causing VMFS heap exhaustion. This stops all VMFS operations causing orphaned virtual machines and missing datastores. vMotion operations might not work and attempts to start new virtual machines might fail with errors about missing files and memory exhaustion. This issue might affect all ESXi hosts that share the corrupt LUN and have running virtual machines on that LUN.
- PR 789483: After you upgrade to ESXi 5.0 from ESXi 4.x, Windows 2000 Terminal Servers might perform poorly. The consoles of these virtual machines might stop responding and their CPU usage show a constant 100%.
- PR 789789: ESXi host might fail with a purple screen when a virtual machine connected to VMXNET 2 vNIC is powered on. The purple diagnostic screen displays an error message similar to the following:
0x412261b07ef8:[0x41803b730cf4]Vmxnet2VMKDevTxCoalesceTimeout@vmkernel#nover+0x2b stack: 0x412261b0
0x412261b07f48:[0x41803b76669f]Net_HaltCheck@vmkernel#nover+0xf6 stack: 0x412261b07f98
You might also observe an error message similar to the following written to VMkernel.log:
WARNING: Vmxnet2: 5720: failed to enable port 0x2000069 on vSwitch1: Limit exceeded^[[0m
- PR 790909: If you limit the number of virtual machines that can power on by setting the VMkernel.Boot.maxVMs value (Advanced Settings > VMkernel > Boot) to less than 6, the ESXi host might fail upon reboot by displaying a purple screen. An error message similar to the following is displayed on the diagnostic screen:
- PR 791407: If you configure the Syslog.global.LogDir parameter incorrectly, the vmsyslogd service fails without displaying any error message, and logs are not written to the default /var/log directory.
- PR 792110: ESXi host generates excessive Reverse Address Resolution Protocol (RARP) packets when virtual machines join or leave multicast groups.
- PR 793274: ESXi 5.0 issues with PXE booting virtual machines with Citrix Provisioning Server (KB 2008436).
- PR 793955: Space reclamation might not succeed on target LUNs due to an issue with certain vendor specific SCSI commands issued on physical RDM LUNs. This issue has been observed with NetApp SnapDrive used for space reclamation on NetApp Filers.
- PR 814402: On a Dell server that is running on Unified Extensible Firmware Interface (UEFI) mode, if you boot an ESXi host installed with OMSA, the BIOS tab on OMSA does not display certain options such as NIC and NUM lock.
- PR 769675: ESXi 5.0 hosts fail to mount VMFS5 volumes that are formatted with ATS-only capabilities (KB 2006858).
- PR 762592: If a guest operating system is receiving and transmitting data at the same time, data transmission might stop under certain load conditions.
None beyond the required patch bundles and reboot information listed in the table above.
Patch Download and Installation
The typical way to apply patches to ESXi hosts is through the VMware Update Manager. For details, see the Installing and Administering VMware vSphere Update Manager.
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.