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

VMware ESXi 6.0, Patch ESXi600-201603201-UG: Updates esx-base, vsanhealth, vsan vib (2142185)

  • 0 Ratings

Details

Release date: Mar 15, 2016

Patch Category Bugfix
Patch Severity Critical
Build For build information, see KB 2142184.
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.34.3620759
  • VMware:vsanhealth:6.0.0-3000000.3.0.2.34.3544323
  • VMware:vsan:6.0.0-2.34.3563498
PRs Fixed 1128579, 1434877, 1455020, 1477248, 1477257, 1500099, 1510290, 1517829, 1526666, 1540114, 1550633, 1551431, 1552199, 1553310, 1555228, 1555240, 1555755, 1559781, 1559790, 1560820, 1572485, 1575130, 1575550, 1576755, 1580173, 1581300, 1582259, 1582877, 1587500
Related CVE numbers NA

Solution

Summaries and Symptoms

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

  • Virtual machines affected by Permanent Device Loss (PDL) do not power on in a failover host. The VM is left in an invalid state with a warning message stating that Hardware Version 1 is not recognized whenever there is a PDL of any of the storage hosting VM.

  • Hostd might randomly stop responding on ESXi hosts with 3D acceleration. Messages similar to the following are logged in the hostd log:

    Crash Report build=2809209
    Signal 11 received, si_code 1, si_errno 0
    Bad access at 34
    eip 0xnnnnnnn esp 0xnnnnnnnn ebp 0xnnnnnnnn
    eax 0xnnnnnnnn ebx 0xnnnnnnn ecx 0x47 edx 0x0 esi 0x30 edi 0xnnnnnnnn

  • After you join the ESXi host to Active Directory, you might be unable to perform Active Directory activities like adding Active Directory Users for permission after certain addition of users from different trusted domains, log in, and so on. In the /var/log/likewise.log file, you see entries similar to:

    20150522181259:DEBUG:lsass:LsaJoinDomain():join.c:380: Error code: 40286 (symbol: LW_ERROR_LDAP_SERVER_DOWN)

  • During live VIB installation, jumpstart plugins, rc scripts and service scripts of the live vib are executed. These plugins and scripts might throw error and/or exception. The errors and/or exceptions might terminate the installation process and cause unexpected behavior such as the live VIB is reported as installed on the system, but does not function properly. Also, the live VIB is lost after a reboot.

  • When you perform a disk-only storage vMotion, the VM might stop responding or go into a power off state as multiple threads attempt to access the same data.

  • The VSISH statistics might show huge false positive packet drops due to integer overflow.

  • ESXi now supports 25G and 50G Ethernet link speeds.

  • Attempts to perform vMotion with virtual machines that have two 2 TB virtual disks created on ESXi 5.0 fail with an error messages similar to the following logged in the vpxd.log file:

    2015-09-28T10:00:28.721+09:00 info vpxd[xxxxx] [Originator@6876 sub=vpxLro opID=xxxxxxxx-xxxxxxxx-xx] [VpxLRO] -- BEGIN task-919 -- vm-281 -- vim.VirtualMachine.relocate -- xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx(xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
    2015-09-28T10:00:28.727+09:00 info vpxd[xxxxx] [Originator@6876 sub=vpxLro opID=xxxxxxxx-xxxxxxxx-xx-xx] [VpxLRO] -- BEGIN task-internal-343729 --  -- VmprovWorkflow --
    ....

  • When you add an ESXi host with powered on VMs to the vCenter Server or when you switch the host from one vCenter Server to another, the vSphere Web Access is unable to open console connection to the VMs. Error messages similar to the following are observed with this issue:

    Web console error message:

    The console has been disconnected. Close this window and re-launch the console to reconnect.

    Standalone VMware Remote Console error message:

    Failed to initialize SSL session to remote host.

    VI client console error message:

    unable to connect to the mks: internal error

    Error message in the vmware.log file:

    SOCKET 6 (150) Error during authd-VNC negotiation: (1) Asyncsocket error.

  • In a vSphere Distributed Switch (vDS) environment, vMotion fails after removing Link Aggregation Groups (LAG). vMotion Wizard Compatibility shows an error message similar to the following:

    Currently connected network interface 'Network Adapter 1" uses network 'DSwitchName', which is not accessible

  • You might experience hardware monitoring failure when you use third-party software ServerView RAID Manager. The sfcb-vmware_aux stops responding due to race condition.

  • During the live VIB installation, esximage creates stage data for live VIB. If you execute the esxcli software VIB get/list command at the same time, the stage data might get deleted and cause the live VIB installation transaction to fail.

  • Attempts to use the Virtual Disk Development Kit (VDDK) HotAdd transport mode to HotAdd and open 2TB+ disk on Virtual Volumes datastore might fail.

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

  • On an ESXi host that has 3D hardware, when hostd detects power state change of a vm, a function is called to check the vm state. In the case of vMotion, the source VM is powered off before being unregistered on the source host, the ManagedObjectNotFound exception is displayed and the hostd might stop responding.

  • The VMware Host Client is an HTML5-based client that is used to connect to and manage single ESXi hosts. It can be used to perform administrative tasks to manage host resources, such as virtual machines, networking, and storage. The VMware Host Client can also be helpful to troubleshoot individual virtual machines or hosts when vCenter Server and the vSphere Web Client are unavailable. For further details on VMware Host Client, see VMware Host Client 1.0 Release Notes.

  • The ESXi mClock IO scheduler does not limit the IOs with a lesser load even after you change the IOPS of the VM using the vSphere Client.

  • Occasionally you might observe slight delay in LUN path state update, as an internal API does not issue scan call to the existing LUNs.

  • Hostd might randomly stop responding on ESXi hosts with 3D acceleration. Messages similar to the following are logged in the hostd log:

    Crash Report build=2809209
    Signal 11 received, si_code 1, si_errno 0
    Bad access at 34
    eip 0xnnnnnnn esp 0xnnnnnnnn ebp 0xnnnnnnnn
    eax 0xnnnnnnnn ebx 0xnnnnnnn ecx 0x47 edx 0x0 esi 0x30 edi 0xnnnnnnnn

  • In ESXi 6.0, when a Permanent Device Loss (PDL) error is received on one path, failover is not triggered on the other available working paths.

  • Hostd might stop responding when you execute esxcli commands using PowerCLI resulting in memory leaks 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.

  • ESXi 6.0 Update 2 supports VMIOF versions 1.0 and 1.1. The vmiof_1_1_0_0 vib tag is added to the list of supported VIB tags in the ESXi base image. This allows you to create filters that are compatible only with ESXi 6.0 U2 and later, as the filters created on the ESXi 6.0 Update 2 devkit will only install on ESXi 6.0 Update 2 or later hosts.

    Filters created on ESXi 6.0 Update 1 will also work with ESXi 6.0 Update 2 hosts without any issues.

  • On an ESXi host that has 3D hardware, when hostd detects power state change of a vm, a function is called to check the vm state. In the case of vMotion, the source VM is powered off before being unregistered on the source host, the ManagedObjectNotFound exception is displayed and the hostd might stop responding.

  • Virtual machine performance metrics are not displayed correctly as the performance counter cpu.system.summation for a VM is always displayed as 0.

  • The ESXi host might fail with a purple diagnostic screen due to an unresponsive CPU as a result of several CMCIs within a short time. Entries similar to the following are displayed on the purple diagnostic screen:

    cpu1:33127)MCE: 1118: cpu1: MCA error detected via CMCI (Gbl status=0x0): Restart IP: invalid, Error IP: invalid, MCE in progress: no.
    cpu1:33127)MCE: 231: cpu1: bank9: MCA recoverable error (CE): "Memory Controller Scrubbing Error on Channel 0."
    cpu1:33127)MCE: 222: cpu1: bank9: status=0xXXXXXXXXXXXXXXXX: (VAL=1, OVFLW=0, UC=0, EN=0, PCC=0, S=0, AR=0), ECC=no, Addr:0xXXXXXXXXXXXXXXXX (valid), Misc:0x8c3589300 (valid)


  • When collecting ESXi log bundle, the lldpnetmap command enables LLDP; however, the LLDP can be only set on Both mode and the LLDP packets are sent out by the ESXi host. The packets might cause the FCoE link to go down.

  • The ESXi host is not moved to maintenance mode in event of a resource pool allocation error.

  • After you upgrade an vSAN environement to ESXi 6.0 Update 1b, the vCenter Server reports a false alarm similar to the following:

    Host cannot communicate with all other nodes in vSAN enabled cluster

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.

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)




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