VMware ESXi 5.1, Patch ESXi-5.1.0-20160504001-standard
search cancel

VMware ESXi 5.1, Patch ESXi-5.1.0-20160504001-standard


Article ID: 337520


Updated On:


VMware vSphere ESXi


Profile Name
For build information, see KB 2141429.
VMware, Inc.
Release Date
May 24, 2016
Acceptance Level
Affected Hardware
Affected Software
Affected VIBs
  • VMware:esx-base: 5.1.0-3.85.3872664
  • VMware:tools-light: 5.1.0-3.85.3872664
PRs Fixed
1207127, 1381419, 1488507, 1512181, 1523122 , 1580019, 1508881
Related CVE numbers

For information on patch and update classification, see KB 2014447.

To search for available patches, see the Patch Manager Download Portal.


VMware vSphere ESXi 5.1


Summaries and Symptoms

This patch updates the following issues:

  • When a Citrix machine is set as PXE boot, there might be many network connect and disconnects to the virtual machine NICs. This can cause the WorkHeap exhaustion if the virtual machine connects to vDS making the system unstable.

  • The lsassd service on the ESXi host might stop responding due to insufficient stack space. This happens when the Physical NICs get disconnected and connected during network maintenance.

  • Attempts to reconnect rsyslog server to the host using a TCP TLS vmsyslogd after a disconnection might fail. This happens when you restart the rsyslog on the remote syslog server and an F5 load balancer is present between the ESXi host and remote syslog server.

  • Virtual machines on vSphere 5.1 environment with Microsoft Volume Shadow Copy Service (VSS) and vSphere Replication might stop responding intermittently. This happens when you consolidate the vSphere Replication generated snapshots files.

  • The Hardware Status tab might stop responding when the FRU device is accessed on word and the read_cnt is greater than or equal to 1. An error message similar to the following is logged in the syslog.log file:
    Dropped response operation details -- nameSpace: root/cimv2, className: OMC_RawIpmiEntity, Type: 0\

  • The hostd service might stop responding when you run esxcli commands using PowerCLI resulting in mismanagement of memory and memory consumption exceeding the hard limit. Error message similar to the following is logged in the hostd.log file:
    YYYY-MM-DDTHH:MM:SS.135Z [nnnnnnnn error 'UW Memory checker'] Current value 646016 exceeds hard limit 643993. Shutting down process.
  • Rebooting or shutting down a guest operating system with VMware tools installed, might cause kernel panic in Linux operating system that kernel version is lower than 3.9.

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. ESXi hosts can also be updated by manually downloading the patch ZIP file from the Patch Manager Download Portal and installing the VIB by using the esxcli software vib command.