Knowledge Base

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

• PR667599: Certain vSphere Client initiated storage operations such as Storage Rescan, Add Storage, or Detach LUN might take a long time to complete or fail due to a timeout when ESXi host has access to VMFS snapshot volumes (replica LUNs). This patch addresses the issue by reducing the time taken to complete these operations.
  
  
• PR787454: After performing vMotion operations on virtual machines, a NUMA imbalance might occur with all the virtual machines being assigned the same home node on the destination server.
  
  
• PR817140: On IBM BladeCenter HX5 UEFI servers, a message similar to the following might be displayed in the vSphere Client when you attempt to configure the power policy of an ESXi host:
  
  Technology: Not Available
  Active Policy: Not Supported.
  
  
  
• PR886363: When a virtual machine is cloned through vCenter Server, the VM Generation ID of the cloned Windows 8 and Windows Server 2012 virtual machines is not updated.
  
  Note:To resolve this issue, you can edit the .vmx file of the cloned virtual machine to set the vm.genid to 0 or remove the line vm.genid from the .vmx file.
  
  
• PR887134: Timer stops in FreeBSD 8.x and 9.x as virtual hardware HPET main counter register fails to update due to comparison failure between signed and unsigned integer values.
  
  
• PR896193: The VMGencounter generation ID is increased to 128-bit value to support specification changes from MSFT and also ACPI notification support is added.
  
  
• PR903619: The timers resulting from I/O operations are allocated from VMKernel main heap. With increased I/O activity, the number of timers increase proportionally leading to depletion of main heap and eventually resulting in a purple diagnostic screen.
  
  
• PR908776: A virtual machine might fail when it encounters error conditions during snapshot operations. Messages similar to the following are logged in the vmware.log file:
  
  2012-06-15T13:00:14.449Z| vcpu-0| SnapshotVMXConsolidateOnlineCB: nextState = 6 uid 0
  2012-06-15T13:00:14.449Z| vcpu-0| Vix: [1376329 mainDispatch.c:4084]: VMAutomation_ReportPowerOpFinished: statevar=3, newAppState=1881, success=1 additionalError=0
  2012-06-15T13:00:14.449Z| vcpu-0| Vix: [1376329 vigorCommands.c:577]: VigorSnapshotManagerConsolidateCallback: snapshotErr = Change tracking target file already exists (5:F3C)
  2012-06-15T13:00:14.449Z[+0.000]| vcpu-0| Caught signal 11 -- tid 1376329
  
  

  or

  
  2012-08-07T21:10:13.184Z| vcpu-0| SnapshotVMXTakeSnapshotComplete done with snapshot 'Snapshot1': 0
  2012-08-07T21:10:13.184Z| vcpu-0| SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Could not open/create change tracking file (5).
  2012-08-07T21:10:13.184Z[+0.000]| vcpu-0| Caught signal 11 -- tid 5678212
  
  
  
• PR909037: When you attempt to switch the scheduler to SFQ, the ESXi host might fail to respond and display a purple diagnostic screen.
  
  

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.