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

Summaries and Symptoms

This patch resolves the following issues:

• Virtual machines running on the same host and same NFS datastore might experience high latency and low virtual disk performance when you set the IOPS limit on one of the VMs.
• After you mount a snapshot LUN with any of the commands used for persistent mounting, the snapshot LUN mount might fail to persist and might not mount following an ESXi reboot. You might not be able to view the datastore of the snapshot LUN from vSphere Client after the ESXi host reboots.
• Each time when you register, unregister or reconfigure a virtual machine on an ESXi host, a new lock is created and the existing lock does not get erased. This can lead to the hostd process consuming large amounts of memory.
• On an ESXi host running on sandybridge server likeIntel Xeon CPU E5 processor, a secondary Fault Tolerance virtual machine might fail with an error message similar to the following written to vmware.log:
  
  |vcpu-0| StateLogger::Commiting suicide: Statelogger divergence
  
  Note: Before you applied the patch, the secondary Fault Tolerance VM failed due to record replay divergence. After you install the patch, the VM does not fail, instead the recording or replaying program closes.
• During vMotion, the ESXi host might fail and displays a purple diagnostic screen with a message similar to the following:
  
  0x4122e7147330:[0x418039b5d12e]Migrate_NiceAllocPage@esx#nover+0x75 stack: 0xnnnnnnnn
  0x4122e71473d0:[0x418039b5f673]Migrate_HeapCreate@esx#nover+0x1ba stack: 0xnnnnnnnn
  0x4122e7147460:[0x418039b5a7ef]MigrateInfo_Alloc@esx#nover+0x156 stack: 0xnnnnnnnn
  0x4122e7147560:[0x418039b5df17]Migrate_InitMigration@esx#nover+0x1c2 stack: 0xnnnnnnnn
  ...
  WARNING: Heartbeat: 646: PCPU 27 didn't have a heartbeat for 7 seconds; *may* be locked up.
  ALERT: NMI: 1944: NMI IPI received. Was eip(base):ebp:cs
  
  This occurs when you run vMotion on a host under memory overload.
• After you install VMware Tools on a virtual machine running on an ESXi host, the ISO image entry might not be removed from the VMX file even after the CD is ejected and the CD-ROM is disconnected.
  
  This patch resolves the issue for newly created VMs. For existing VMs for which the VMX file contains an ISO image entry, run the cdrom_iso_line.py script to remove the entry as described in KB 2076512.
  
  Note: To completely resolve this issue, you must install both the esx-base VIB (ESXi500-201405401-BG) and tools-light VIB (ESXi500-201405402-BG) bulletins of this patch.
• Creating and deploying a host profile from an ESXi host in a vCenter Server might take a long time or might fail when the host is configured with multiple storage devices and the host cache is SSD enabled. An error message similar to the following is displayed in the vSphere Client:
  
  Error: vcenter took too long to respond. Error Stack: Call "HostProfileManager.CreateProfile" for object "HostProfileManager" on vCenter Server "your.vcenter.server.fqdn" failed.
• The hostd service might fail on an ESXi host resulting in SNMP traps not getting generated.
• The performance chart displays incorrect throughput usage values for the following vCenter Server inventory objects:
  • Virtual Machine > Virtual Disk
  • Host > Disk
  • Host > Storage Path
  • Host > Storage Adapter

  
  For more information see KB 2064464.
• If the SCSI command timer is triggered and the path task management halts the command before the ScsiMidlayerFrame is initialized, the ESXi host might fail with a purple diagnostic screen and displays an error message similar to the following:
  
  @BlueScreen: #PF Exception 14 in world 619851:PathTaskmgmt IP 0x418022c898f6 addr 0x48
  Code start: 0x418022a00000 VMK uptime: 9:08:16:00.066
  0x4122552dbfb0:[0x418022c898f6]SCSIPathTimeoutHandlerFn@vmkernel#nover+0x195 stack:
  0x4122552e7000 0x4122552dbff0:[0x418022c944dd]SCSITaskMgmtWorldFunc@vmkernel#nover+0xf0 stack:0x0
• When you use the Add Storage wizard to create new VMFS datastore, populating the available LUNs for provisioning might be delayed. The delay depends on the number of read-only LUNs presented to the ESXi host.
• Attempts to install ESXi on an iSCSI remote LUN might fail with the following error:
  
  Expecting 2 bootbanks, found 0
• The object identifier (OID) generated by the ESXi host during linkup and linkdown events might not match the value in the Management Information Base (MIB) browser.
• On an ESXi host, a virtual machine might fail when a suspend operation or a checkpoint process is in progress with activities such as collecting vm-support. Alternatively, a VM might fail while running vm-support with HungVM:Suspend_VM as described in KB 2005831.
  
  The vmware.log file might contain a message similar to the following:
  
  |vcpu-0| I120: ASSERT bora/vmcore/vmx/main/monitorAction.c:<xxx>
• An ESXi host running on a hardware enabled with Non-Uniform Memory Access (NUMA) reports incorrect values for number of vcpus and vcpus powering on as shown in the following VSI output. This might lead to a degradation in performance:
  
  vsishoutput:
  /sched/numaStats/numaNodes/> cat 0
  NUMA node statistics {

  used:4476 msec
  idle:595562 msec
  entitled:0 msec
  owed:0 msec
  normalized load average:0 pct
  number of vcpus:1937339183 <--
  vcpus powering on:1937339183 <--
  free memory:98685648 KB
  total memory:100580612 KB

  }
   
• After VMware Tools auto-upgrade, the virtual machine might reboot when you enable the upgrading of VMware Tools on power cycle and use vMotion to migrate the VM from ESXi 5.0 Update 1 with no tools profile to ESXi 5.0 Update 3.
  
  This patch prevents the VMware Tools to auto-upgrade and reboot after you use vMotion to migrate a VM from a host without the VMware Tools ISO to a host that contains VMware Tools ISO.
• On a vNetwork Distributed Switch (vDS) where the traffic shaping is enabled, burst of data packets sent by applications might drop due to limited queue size.
• When you perform a compliance check on an ESXi host, an error message similar to the following is displayed in the vSphere Client:
  
  Found extra CIM-XML Indication Subscription on local system for query u'select * from CIM_AlertIndication' sent to destination u'https://IP:port'
• An XML parsing error might occur when you query CIM instances from Web Server Manager (WSMAN) Client on an ESXi host with special characters in one of its properties.
• Storage vMotion of virtual machines with RDM disks might fail and VMs might switch to a powered off state. Attempts to power on the VM fails with the following error:
  
  Failed to lock the file
• When simultaneous shared memory operations are triggered through Virtual Machine Communication Interface (VMCI), an ESXi host might display a purple screen (PSOD) with panic message similar to the following:
  
  CPU 24 tried to re-acquire lock alloc-404778
• ESXi host fails with a purple diagnostic screen when you run custom scripts using the AdvStats parameter to check the disk usage. A message similar to the following is written to vmkernel.log:
  
  VSCSI: 231: Creating advStats for handle 8192, vscsi0:0
  
  The host reports a backtrace similar to:
  
  Histogram_XXX
  VSCSIPostIOCompletion
  AsyncPopCallbackFrameInt
   
• When you attempt to extend a Virtual Disk located on a VAAI-NAS datastore, the ESXi host might stop responding with an error similar to:
  
  Assert Failed: "pos <= max" @ bora/vim/hostd/vdisksvc/vdiskManagerImpl.cpp:102
  
  An error message similar to the following is displayed in the vCenter Server similar to:
  
  An error occurred while communicating with the remote host.
• Attempts to deploy a virtual machine on a VMFS volume backed by a StorMagic SVA instance that is deployed on the same host with VMDK backed by LUNs might fail during guest operating system installation.
   
• When you power on a virtual machine with a dvPort on a host that already has a large number of dvPorts in use, an error similar to the following is written to hostd.log:

Unable to Get DVPort list ; Status(bad0014)= Out of memory

A warning is also written to the vmkernel.log similar to the following:

WARNING: Heap: 2757: Heap dvsLargeHeap (132993984/134217728): Maximum allowed growth (1224704) too small for size (9269248)

• When VMware Tools is uninstalled from a Windows Server 2012 VM configured with more than one disk, the second disk might go offline after reboot.

  
  Note: If the error condition has already occurred due to uninstallation of VMware Tools without this fix, you can bring the disk back online by following the procedure mentioned in KB 2000767.

• Binary kmod packages might not be available from OSP format tools for the Ubuntu 12.04.3 (3.8.0-29) operating system.
  
  Note: This patch contains kmod package for Ubuntu 12.04.3 (3.8.0-29). <ui> </ui>
• After you install VMware Tools, the Windows Event Viewer displays a warning similar to the following:
   

  Unable to read a line from 'C:\Program Files\VMware\VMware Tools\messages\es\hgfsUsability.vmsg': Invalid byte sequence in conversion input.

  This issue is particularly noticed after installing VMware Tools on Spanish locale operating system.

• An ESXi 5.x host fails with a purple diagnostic screen when you use an LSI MegaRAID SAS driver version ealier than 6.506.51.00.1vmw.

You see entries similar to the following:
 

 

@BlueScreen: #PF Exception 14 in world 4795:helper31-5 IP 0x41800b4e2eef addr 0xce8

 

Code start: 0x41800ae00000 VMK uptime: 156:04:02:21.485

 

0x41224aec7eb0:[0x41800b4e2eef]megasas_reset_fusion@#+0x1e stack: 0x0

 

0x41224aec7f60:[0x41800b2ea697][email protected]#9.2+0x11a stack: 0x0

 

0x41224aec7ff0:[0x41800ae3e129]helpFunc@vmkernel#nover+0x568 stack: 0x0

 

0x41224aec7ff8:[0x0] stack: 0x0

• When you use LSI SMI-S provider with MegaRaid SAS device driver on an ESXi 5.x host, the status change of LSI MegaRaid disk might not be indicated or might be delayed when you run the command enum_instances LSIESG_PhysicalDrive lsi/lsimr13.
  
  The following example indicates that the value of PowerState does not change or changes after a delay when the Power Saving mode of LSI MegaRaid disk is modified:
  
  LSILSIESG_PhysicalDrive.Tag="500605B004F93CF0_252_36",CreationClassName="LSIESG_PhysicalDrive"
  CreationClassName = LSIESG_PhysicalDrive
  Tag = 500605B004F93CF0_252_36
  UserDataBlockSize = 512
  PiType = 0
  PiEligible = 0
  PiFomatted = 0
  PowerState = 0 ---> No change in status
  Vendor = (NULL)
  FRUNumber = (NULL)
  DiskDrive_DeviceID = 252_36

Deployment Considerations

Patch Download and Installation