Search the VMware Knowledge Base (KB)
Products:
View by Article ID

VMware ESXi 6.0, Patch ESXi600-201605401-BG: Updates esx-base, vsanhealth, vsan VIBs (2144685)

  • 7 Ratings
Language Editions

Details

Release date: May 12, 2016

Patch Category Bugfix
Patch Severity Critical
Build For build information, see KB 2136186.
Host Reboot Required Yes
Virtual Machine Migration or Shutdown Required Yes
Affected Hardware N/A
Affected Software N/A
VIBs Included
  • VMware:esx-base:6.0.0-2.37.3825889
  • VMware:vsanhealth:6.0.0-3000000.3.0.2.37.3825892
  • VMware:vsan:6.0.0-2.37.3825891
PRs Fixed 1611463, 1616775, 1626050, 1626789, 1626948, 1636418, 1632784
Related CVE numbers NA

Solution

Summaries and Symptoms

This patch updates the esx-base, vsanhealth, and vsan VIBs to resolve the following issues:

  • An ESXi host might stop responding during IOFilter testing with a purple diagnostic screen with messages similar to the following:

    gdb) bt
    #0 0xnnnnnnnnnnnnnnnn in DLM_free (msp=0xnnnnnnnnnnnn, mem= , allowTrim=1 '\001') at bora/vmkernel/main/dlmalloc.c:4867
    #1 0xnnnnnnnnnnnnnnnn in Heap_Free (heap=0x430247659000, mem=0x43024769bea0) at bora/vmkernel/main/heap.c:4356
    #2 0xnnnnnnnnnnnnnnnn in FDSAsyncSGIODone (vmkCmd=0xnnnnnnnnnnnn) at bora/vmkernel/filesystems/devices/fdsCommon.c:1686
    #3 0xnnnnnnnnnnnnnnnn in helpFunc (data= ) at bora/vmkernel/main/helper.c:3288
    #4 0xnnnnnnnnnnnnnnnn in CpuSched_StartWorld (destWorld= , previous=0xnnnnnnnnnnnn) at bora/vmkernel/sched/cpusched.c:10760
    #5 0x0000000000000000 in ?? ()

  • In a DRS cluster, when the memory reservation for a VM is decreased, the change in the reservation does not propagate in the correct order in the VM's memory resource pool hierarchy. An error message similar to the following is displayed in the hostd.log file:

    Unable to apply DRS resource settings on host. The available memory resources in the parent pool are insufficient for the operation.

  • Attempts to upgrade a vSAN cluster On-Disk format version from version 2.0 to 3.0 fails when you Power On CBT-enabled VMs. Also, CBT-enabled VMs from a non-owning host might fail due to on-disk lock contention on the ctk files and you might experience the following issues:

    • Deployment of multiple VMs from same CBT enabled template fail.
    • VMs are powered off as snapshot consolidation fails.
    • VM does not Power On if the hardware version is upgraded (for example, from 8 or 9 to 10) before registering the VM on a different host

  • Attempts to upgrade to ESXi 6.0 Update 2 using the vCenter Update manager with the Lockdown mode enabled might fail with an error message similar to the following:

    The host returns esxupdate error code:18. Maintenance mode is not enabled or could not be determined. Check the Update Manager log files and esxupdate log files for more details.

    For additional details, see KB 2144691.

  • ESXi 6.0 Update 2 host fails with a purple diagnostic screen when the virtual machines have a Hardware Large Receive Offload for VMXNET3 (Vmxnet3HwLRO) NICs enabled and are running hardware version 11. Backtrace similar to the following is displayed:

    @BlueScreen: VERIFY bora/vmkernel/net/vmxnet3_vmkdev.c:10474
    Code start: 0x418000000000 VMK uptime: 0:00:15:27.202
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]PanicvPanicInt@vmkernel#nover+0x37e stack: 0xhhhhhhhhhhhh
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]Panic_NoSaveNoReturn@vmkernel#nover+0x4d stack: 0xhhhhhhhhhhhh
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]Int6_UD2Assert@vmkernel#nover+0x12c stack: 0xhhhhhhhhhhhh
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]gate_entry_@vmkernel#nover+0x0 stack: 0x0
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]Vmxnet3VMKDevRxWithLock@vmkernel#nover+0x1f2f stack: 0x1
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]Vmxnet3VMKDevRx@vmkernel#nover+0x2df stack: 0xhhhhhhhhhhhh
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]IOChain_Resume@vmkernel#nover+0x210 stack: 0xhhhhhhhhhhhh
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]PortOutput@vmkernel#nover+0xae stack: 0x0
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]EtherswitchForwardLeafPortsQuick@<None>#<None>+0x136 stack: 0x1e8024
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]EtherswitchPortDispatch@<None>#<None>+0x5ec stack: 0xhhhhhhhhhhhh
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]Port_InputResume@vmkernel#nover+0x17b stack: 0xhhhhhhhhhhhh
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]Net_AcceptRxList@vmkernel#nover+0x115 stack: 0xhhhhhhhhhhhh
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]NetPollWorldCallback@vmkernel#nover+0x12f stack: 0x100f
    0xhhhhhhhhhhhh:[0xhhhhhhhhhhhh]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0

  • Writes to VMDKs with snapshots using the vsanSparse format will fail if the VMDK sizes are not aligned to 4K.

  • Attempts to upgrade vSAN result in General vSAN error at 10% where some Virtual Disk Descriptor files use non UTF-8 encoding.

Patch Download and Installation

The typical way to apply patches to ESXi hosts is through the VMware vSphere Update Manager. For details, see the Installing and Administering VMware vSphere Update Manager.
 
ESXi hosts can 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. Additionally, the system can be updated using the image profile and the esxcli software profile command. For details, see the vSphere Command-Line Interface Concepts and Examples and the vSphere Upgrade Guide.

Additional Information

For translated versions of this article, see:

Tags

esxi 6.0 3825889, esxi 6.0 patches, build 3825889

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

  • 7 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)




Please enter the Captcha code before clicking Submit.
  • 7 Ratings
Actions
KB: