Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

VMware ESXi 5.0, Patch ESXi-5.0.0-20130804001-no-tools (2053138)

Details

Profile Name
ESXi-5.0.0-20130804001-no-tools
Build
For build information, see KB 2053131.
Vendor
VMware, Inc.
Release Date
August 29, 2013
Acceptance Level
PartnerSupported
Affected Hardware
N/A
Affected Software
N/A
Affected VIBs
  • esx-base
  • net-e1000
PRs Fixed
832350, 928616, 936878, 951566, 964062, 991194, 994472, 1001539, 1002062, 1002982, 1005317, 1005328, 1024051, 1024879, 1043909, 1051030, 994208
Related CVE numbers
N/A

 

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

Solution

Summaries and Symptoms

This patch resolves the following issues:

  • During the ESXi boot process, loading the nfsclient module might hold lock on the esx.conf file for a long time if there is a delay in the host name resolution for Network File System (NFS) mount points. This might cause failure of other module loads such as migrate, ipmi, or others.

  • If you use iSCSI initiator software, the ESXi host might panic with a purple diagnostic screen (PSOD) when two threads attempt to free an iSCSI session simultaneously. You see error messages similar to the following logged in the vmkernel log:

    PANIC bora/vmkernel/main/dlmalloc.c:4787 - Corruption in dlmalloc

  • An ESXi 5.0 host might get disconnected from the vCenter Server due to a memory leak in the VMkernel heap area when the ESXi server is in a low memory reservation state.

  • When using a NEC ESMPRO Server Manager as the Common Information Model (CIM) client software, you cannot connect to the WS-Management (openwsmand) service on the ESXi host. You see error messages similar to the following in the CIM client software:

    javax.xml.soap.SOAPException: java.io.IOException: Unauthorized

  • When you perform certain operations that directly or indirectly involve Virtual Machine File System (VMFS), usually in an ESXi cluster environment sharing large number of VMFS datastores, you might encounter the following issues:

    • ESXi host stops responding intermittently
    • ESXi host gets disconnected from the vCenter Server
    • Virtual machine stops responding intermittently
    • Microsoft Cluster Service (MSCS) stops responding resulting in failover
    • Host communication errors during Site Recovery Manager (SRM) data recovery and failover tests

  • When you set an ESXi host, on which IPv6 support is disabled, to use Active Directory authentication, the traffic might still contain the Authentication, Authorization, Accounting and Auditing (AAAA) records for DNS queries.

  • For two ESXi hosts with different host names, identical machine names are generated in the Domain Controller under certain conditions. This causes one of the two ESXi hosts to lose the Active Directory functionality.

  • On an ESXi host with HP SMX CIM Provider, all resource groups of the Small-Footprint CIM Broker daemon (sfcbd) might get consumed, thereby causing the sfcbd to be out of service.

  • Black frames might appear around text boxes in an application running on Virtual Machine Hardware Version 8 or later. You might also observe this issue if any of the open application windows are moved across on the desktop. This issue occurs on virtual machines with Windows 7 guest operating system and VMware View 5.0 PC-over-IP (PCoIP).

  • On an ESXi 5.0 host, sfcbd might fail frequently and display CIM errors. As a result, the Hardware Status tab might stop displaying the host health status and the syslog.log might contain error messages similar to the following:

    Timeout (or other socket error) sending request to provider.

  • An ESXi host might stop responding and display a purple diagnostic screen (PSOD) indicating the PF exception 14 in UserTeletype_Ioctl error message in the VMkernel due to a race condition during the clean up of a UserCartel session. You see a backtrace similar to the following is displayed:

    0x41220ae47cb8:[0x41801c7e0c9c]UserTeletype_Ioctl@vmkernel#nover+0x343 stack: 0x41003d160fe0
    0x41220ae47d68:[0x41801c87d16d]DevFSIoctl@vmkernel#nover+0x470 stack: 0x41220ae47ebc
    0x41220ae47dc8:[0x41801c8600c7]FSS2_IoctlByFH@vmkernel#nover+0x36a stack: 0xbcd00000066
    0x41220ae47e18:[0x41801c85fce8]FSS_IoctlByFH@vmkernel#nover+0x8b stack: 0xffb0abec0000541

  • An ESXi host might stop responding to network connections, suffer unplanned disconnection issues, or other networking issues. You can see an error message similar to the following logged in the vmkwarning.log file:

    Heap: 2638: Heap netGPHeap already at its maximum size. Cannot expand.

  • While performing certain network related operations on an ESXi host, the e1000 physical NIC might not process any incoming or outgoing packets for about five seconds. After five seconds, the ESXi host resets the NIC to resume packet transfer and displays warning messages similar to the following in the vmkwarning.log:

    WARNING: NetSched: 1857: Scheduler [0x4100045b3780] lock up [stopped=0] for vmnic1:
    WARNING: NetSched: 1868: detected at 273740129 while last xmit at 273734446 and 2/66740 packets/bytes in flight [window full 1] and binary heap size 1 last queue at 273738236 [stress 0]
    WARNING: NetSched: 1877: Packets completion seem stuck, issuing reset on vmnic1 [stress 0]

    However, the ESXi host resets the NIC only when there is an outgoing packet on the NIC. If there is no outgoing packet, the e1000 NIC remains in the failed state and does not process any incoming packet.

Deployment Considerations

None beyond the required patch bundles and reboot information listed in the table above.

Patch Download and Installation

An ESXi system can be updated using the image profile, by using the esxcli software profile command. For details, see the vSphere Command-Line Interface Concepts and Examples and the vSphere Upgrade Guide. For information about image profiles and how it applies to ESXi 5.0 hosts, see Image Profiles of ESXi 5.0 Hosts (2009231). ESXi hosts can also be updated by manually downloading the patch ZIP file from the VMware download page and installing the VIB by using the esxcli software vib command.


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.

Feedback

  • 0 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)
  • 0 Ratings
Actions
KB: