ESXi host fails with PSOD #PF Exception 14 in world xxxx:Res6Affinity IP

Products

• VMware vSphere ESXi

Issue/Introduction

• The ESXi might fail with a purple diagnostic screen.
• In the /var/run/log/vmkernel.* log file, entries can be found similar to:

  <timestamp> cpu25:66762)@BlueScreen: #PF Exception 14 in world 66762:Res6Affinity IP 0x############ addr 0x0
  PTEs:0x80574cf023;0x80574d0023;0x80574d1023;0x0;
  <timestamp> cpu25:66762)Code start: 0x418018000000 VMK uptime: 155:03:46:53.395
  <timestamp> cpu25:66762)0x43916651beb0:[0x418018e83e3e]Res6AffMgrGetLFBCInfoBucket@esx#nover+0x32 stack: 0x1
  <timestamp> cpu25:66762)0x43916651bef0:[0x418018e84c40]Res6AffinityManager@esx#nover+0x134 stack: 0x43099b4faae0
  <timestamp> cpu25:66762)0x43916651bf90:[0x418018108adf]vmkWorldFunc@vmkernel#nover+0x4f stack: 0x418018108ada
  <timestamp> cpu25:66762)0x43916651bfe0:[0x4180182c91f5]CpuSched_StartWorld@vmkernel#nover+0x99 stack: 0x0

Note:The preceding log excerpts are only examples. Environmental variables and memory addresses may vary depending on the environment

 

Environment

• VMware vSphere ESXi 6.5
• VMware vSphere ESXi 6.7

Cause

This PSOD might occur due to a race condition between resource allocations and VMFS6 volume closing operation.

Resolution

This issue is resolved in the following ESXi versions:

• ESXi 6.7 P02 (ESXi670-202004002)
• ESXi 6.5 P07 (ESXi650-202110001)

As a workaround:

1. Create a VMFS5 datastore
2. Storage vMotion the VMs from VMFS6 to VMFS5 datastore.

Additional Information

Impact/Risks:
None