VMware ESXi-5.0, Patch ESXi-ESXi-5.0.0-20151004001-standard
search cancel

VMware ESXi-5.0, Patch ESXi-ESXi-5.0.0-20151004001-standard


Article ID: 334300


Updated On:


VMware vSphere ESXi


Release date: October 1, 2015

Patch Name ESXi-5.0.0-20151004001-standard
BuildFor build information, see KB2113684
VendorVMware, Inc.
Release DateOctober 01, 2015
Acceptance LevelPartnerSupported
Affected HardwareN/A
Affected SoftwareN/A
Affected VIBs
  • VMware:esx-base:5.0.0-3.73.3086167
  • VMware:tools-light:5.0.0-3.73.3086167
PRs Fixed1396716, 1399161, 1406124, 1509256, 1408747, 1453061, 1504807, 1419963
Related CVE numbersN/A


VMware vSphere ESXi 5.0


Summaries and Symptoms

This patch resolves the following issues:

  • Attempts to provision and remove virtual machines using VIEW might fail with an error. An error message similar to the following is displayed in vCenter server logs:
    Failed to get DVS state from vmkernel Status (bad0006)= Limit exceeded" can be found. Provisioning failure with message similar to the following is displayed:
    Unable to Add Port; Status(bad0006)= Limit exceeded

  • The CTK lock files (ctk.vmdk.lck) created on a changed block tracking enabled (CBT) enabled virtual machine might not get deleted until you do a clean power off of the virtual machine. This might cause issues during HA events and while running recovery software.
    You might also not be able to deploy the same template in a vApp multiple times if the template of the VM is CBT enabled. This is because CBT locks the file and is not released in time for the additional deployments.

  • When you run esxtop in batch mode to export performance data into a .csv file, the exported file might not contain the vSCSI data

  • When you delete a VDI environment enabled desktop pool, the VMDK files of the other virtual machine from a different desktop pool might get deleted. Multiple virtual machines from different desktop pools might affected. This happens when after deleting the disk, the parent directory gets deleted due to an error where the directory is perceived as empty, even though its not.
    An error message similar to the following might be displayed:
    014-07-23T14:08:03.408-07:00 [06072 info 'Default' opID=30545c60] [VpxLRO] -- ERROR task-19533 -- vm-1382 -- vim.ManagedEntity.destroy: vim.fault.FileNotFound:
    --> Result:
    --> (vim.fault.FileNotFound) {
    --> dynamicType = <unset>,</unset>
    --> faultCause = (vmodl.MethodFault) null,
    --> file = "[cntr-1] guest1-vm-4-vdm-user-disk-D-c7a28539-3d34-4771-9bcb-cb2386ec2016.vmdk",
    --> msg = "File [cntr-1] guest1-vm-4-vdm-user-disk-D-c7a28539-3d34-4771-9bcb-cb2386ec2016.vmdk was not found",
    --> }
    --> Args
    VMDK deletion occurs, when a particular virtual machine's Operating System (OS) and user data disk are spread across different datastores. This issue is not visible when all VM files reside in same datastore.
  • Virtual machines using VMXNET3 virtual adapter might fail when attempting to boot from iPXE (open source boot firmware).
  • Under memory overload, an ESXi host might experience a purple diagnostic screen and fail to respond.A trace similar to the following is displayed on the host:

    @BlueScreen: PCPU 4: no heartbeat (2/2 IPIs received)
    Code start: 0x418023200000 VMK uptime: 0:00:58:25.198
    Saved backtrace from: pcpu 4 Heartbeat NMI
    SP_WaitLockIRQ@vmkernel#nover+0x168 stack: 0x1fe00000
    LPage_ReapPools@vmkernel#nover+0x14e stack: 0x1
    MemDistributeAllocateAndTestPages@vmkernel#nover+0x229 stack: 0x4123
    MemDistributeAllocPagesWait@vmkernel#nover+0x2b stack: 0x4123648a500
    MemDistributeAllocPagesWaitLegacy@vmkernel#nover+0xae stack: 0x0
    MemDistributeAllocVMPageWaitInt@vmkernel#nover+0xd9 stack: 0x0
    MemDistribute_AllocSharedVMPageWait@vmkernel#nover+0x25 stack: 0x418
    VmMem_AllocSharedPage@vmkernel#nover+0xf3 stack: 0x1
    VmMemCowSharePageInt@vmkernel#nover+0x12e stack: 0x0
    VmMemCow_SharePages@vmkernel#nover+0x341 stack: 0x410077a032a4
    VMMVMKCall_Call@vmkernel#nover+0x186 stack: 0x0

  • When Unidesk is used in conjunction with VMview or vSphere with vShield Endpoint enabled, applications such as QuickTime might experience a slowdown in performance. This is due to an interoperability issue that gets triggered when Unidesk volume serialization filter driver and vShield driver is present on the stack.

    For each file opened by the application, even if it is just for reading the attributes, the vShield driver callsFltGetFileNameInformation;causing further processing to be performed on the files. As a result Unidesk driver opens directories that causes an overall application performance degradation.

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.