Knowledge Base

This patch resolves 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.
  
  
• PR891399: This patch updates the misc-drivers VIB to resolve an issue where the ESXi hosts might encounter a purple diagnostic screen with one of the following messages due to a deadlock during SCSI command completion:
  
  PCPU X locked up. Failed to ack TLB invalidate (total of 1 locked up, PCPU(s): X).
  Saved backtrace from: pcpu 4 TLB NMI
  0x41226eb87aa0:[0x418003a7669d]RefCountIncWait@vmkernel#nover+0x28 stack: 0x73cd
  0x41226eb87b00:[0x418003aea71e]Worldlet_WorldletAffinitySet@vmkernel#nover+0xa9 stack: 0xc37c0
  0x41226eb87b30:[0x418003aeaa1b]WorldletAffinityTrackerUpdate@vmkernel#nover+0x42 stack: 0x41226eb87
  0x41226eb87b60:[0x418003ae90ed]vmk_WorldletAffinityTrackerCheck@vmkernel#nover+0xf8 stack: 0x1ef4f9
  0x41226eb87cc0:[0x418003ed3f6e]SCSILinuxWorldletFn@com.vmware.driverAPI#9.2+0x7e1 stack: 0x0
  0x41226eb87d70:[0x418003aed17e]WorldletProcessQueue@vmkernel#nover+0x3c5 stack: 0x70000000c
  0x41226eb87db0:[0x418003aed689]WorldletBHHandler@vmkernel#nover+0x60 stack: 0x41226eb65000
  0x41226eb87e10:[0x418003a1824c]BHCallHandlers@vmkernel#nover+0xbb stack: 0x7004122000683c7
  0x41226eb87e50:[0x418003a1873b]BH_Check@vmkernel#nover+0xde stack: 0x410001772000
  
  

  or

  PCPU Y locked up. Failed to ack TLB invalidate (total of 1 locked up, PCPU(s): Y).
  Saved backtrace from: pcpu 13 TLB NMI
  0x412240ac7bc8:[0x41800bcbe4ba]__raw_spin_failed@com.vmware.driverAPI#9.2+0x1 stack: 0x4100341fc180
  ...
  0x412240ac7c78:[0x41800bca0c90]Linux_IRQHandler@com.vmware.driverAPI#9.2+0x2b stack: 0x41800bcc563e
  0x412240ac7d08:[0x41800b841ba5]IDTDoInterrupt@vmkernel#nover+0x2fc stack: 0x410009a06018
  0x412240ac7d48:[0x41800b841e23]IDT_HandleInterrupt@vmkernel#nover+0x72 stack: 0x41000c73e450
  0x412240ac7d68:[0x41800b84274d]IDT_IntrHandler@vmkernel#nover+0xa4 stack: 0x412240ac7e80
  0x412240ac7d78:[0x41800b8f1047]gate_entry@vmkernel#nover+0x46 stack: 0x4018
  
  
• 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.
  
  

Deployment Considerations

Patch Download and Installation