Release date: December 04, 2014

Summaries and Symptoms

This patch updates the esx-base VIB to resolve the following issues:

• The openwsman process might stop responding when you run consistency checks on the logical drive of an ESXi host installed with LSI CIM provider and managed by NEC ESMPRO agent or ServerManager 5.6. Large amounts of memory might be consumed during the openwsman process causing the process to fail.
  
  An error similar to the following is written to syslog:
  
  YYYY-MM-DDTHH:MM:SS.FFFZ cpuX:XXXXXX)User: 2358: wantCoreDump : openwsmand -enabled : 0

• VMware vCloud Director (vcd) or vRealize Automation (formely known as vCloud Automation Center) deployment through vcd might fail to concurrently deploy multiple instances of a template when Changed Block Tracking is enabled through vSphere Data Protection or third party software. Errors similar to the following are displayed in the vCenter Server:
  
  Error caused by file filename.vmdk
  
  Could not open/create change tracking file
  
  
• VMware vCenter Server performance charts might display incorrect values for Disk.throughput.usage.average. The values are calculated in bytes per second instead of Kilobytes per second (KBps). For more information, see KB 2064464.
  
  
• A new claim rule option reset_on_attempted_reserve has been added for IBM storage Array Model 2145. For more information, see KB 2008333.
  
  
• This patch introduces additional Transparent Page Sharing (TPS) management capabilities. For more information, see KB 2091682.
  
  
• When you attempt to reboot an ESX host, if the primary DNS server is unavailable and the secondary server is still available, the NFS volumes are not restored due to a delay in resolving the NFS server host names (FQDN).
  
  
• The host with virtual machines that use an E1000e virtual network adapter might fail with a purple diagnostic screen if Receive Side Scaling is enabled and the number of receive queues (Rx queue) is set to 1 on the virtual machine.
  

The purple diagnostic screen or backtrace contains entries similar to the following:

E1000PollRxRing@vmkernel#nover+0xeb7
E1000DevRx@vmkernel#nover+0x18a
IOChain_Resume@vmkernel#nover+0x247
PortOutput@vmkernel#nover+0xe3
EtherswitchForwardLeafPortsQuick@ # +0xd6
EtherswitchPortDispatch@ # +0x13bb
Port_InputResume@vmkernel#nover+0x146
Net_AcceptRxList@vmkernel#nover+0x157
NetPollWorldletCallback@vmkernel#nover+0x5c
WorldletProcessQueue@vmkernel#nover+0x488
WorldletBHHandler@vmkernel#nover+0x60
BH_Check@vmkernel#nover+0x185
IDT_IntrHandler@vmkernel#nover+0x1fc
gate_entry@vmkernel#nover+0x63

• Virtual machines using VMXNET3 virtual adapter might fail when attempting to PXE boot from Microsoft Windows Deployment Services (WDS).
  
  
• In a vSphere HA cluster, when virtual machines are left unprotected before the VM configuration is fully loaded, VMware High Availability (HA) attempts to abort for a large number of VMs. In addition, the DVPort data might not be loaded and the VMs are marked to start with the virtual network interface cards (vNICs) disconnected.
  
  
• Under a highly specific and detailed set of internal timing conditions, the AMD Opteron Family 10h processor might incorrectly update the stack pointer and cause ESXi 5.x host to crash or throw a program exception.
  
  Note: This failure is observed with multiple signatures. One of the purple diagnostic screen associated with this issue might display a backtrace similar to the following:
  
  @BlueScreen: #PF Exception 14 in world 1388383:sh IP 0x41800b44634c addr 0x41800b446366
  PTEs:0x12734f023;0x1035f2023;0x1058000a1;
  Code start: 0x41800b400000 VMK uptime: 19:08:58:22.311
  0x41223d7db940:[0x41800b44634c]Heap_AlignWithTimeoutAndRA@vmkernel#nover+0x143 stack: 0x0
  0x41223d7db990:[0x41800b63cca5]OC_SetObjComponentName@vmkernel#nover+0xe4 stack: 0x80000003
  0x41223d7db9f0:[0x41800b62e96b]FSSLookupInt@vmkernel#nover+0x24e stack: 0x410009268e68
  0x41223d7dba20:[0x41800b62e9f1]FSS_Lookup@vmkernel#nover+0x4c stack: 0xf000000ac
  0x41223d7dbb60:[0x41800b891432]UserFileOpen@#+0x245 stack: 0x22082e1000402f
  0x41223d7dbbf0:[0x41800b87c72b]UserObjTraversePath@#+0x1b6 stack: 0x41223d7dbc90
  0x41223d7dbc60:[0x41800b87ca96]UserObj_TraversePath@#+0xfd stack: 0x410000000100
  0x41223d7dbe10:[0x41800b87cbdf]UserObj_Open@#+0xb6 stack: 0x0
  0x41223d7dbeb0:[0x41800b89977c]LinuxFileDesc_Stat64@#+0x57 stack: 0x41223d7e7000
  0x41223d7dbef0:[0x41800b8776fa]User_LinuxSyscallHandler@#+0xe5 stack: 0x0
  0x41223d7dbf10:[0x41800b4a84ce]User_LinuxSyscallHandler@vmkernel#nover+0x19 stack: 0xff9f0a78
  0x41223d7dbf20:[0x41800b510064]gate_entry@vmkernel#nover+0x63 stack: 0x0
  
  
• An ESXi 5.x host that uses AMD Opteron 6300 Series processor might fail and display a purple screen. The message on the purple screen mentions IDT_HandleInterrupt or IDT_VMMForwardIntr followed by an unexpected function. See KB 2061211.

• When you use backup software that uses the Virtual Disk Development Kit (VDDK) API call QueryChangedDiskAreas(), the list of allocated disk sectors returned might be incorrect and incremental backups might appear to be corrupt or missing. A message similar to the following is written to vmware.log:
  
  DISKLIB-CTK: Resized change tracking block size from XXX to YYY
  
  For more information, see KB 2090639.

• An ESXi server might experience a purple diagnostic screen when using DvFilter with a NetQueue supported uplink connected to a vSwitch or a vSphere Distributed Switch (VDS).

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. To update ESXi 5.x hosts when not using Update Manager, download the patch ZIP file from http://support.vmware.com/selfsupport/download/ and install the bulletin using esxupdate from the command line of the host.

Additional Information

• 日本語: VMware ESXi 5.0、パッチ ESXi500-201412401-BG：esx-base のアップデート (2145743)

• 简体中文: VMware ESXi 5.0 修补程序 ESXi500-201412401-BG：更新 esx-base (2145873)