vSAN ESA host running specific version of vSphere might encounter a PSOD

Products

• VMware vSAN

Issue/Introduction

Hosts in vSAN ESA cluster may experience PSODs similar to the stack shown below

Backtrace for current CPU #xx, worldID=xxxxxxx, fp=0x0
PanicvPanicInt@vmkernel#nover+0x202 stack: 0x453ac251bc00, 0x420032b19b5a, 0x0, 0x420000000001, 0x420032b19b5a
Panic_vPanic@vmkernel#nover+0x25 stack: 0x15755a45, 0x420032b3251f, 0x45de1b36eba8, 0x420035404218, 0x15755a45
vmk_vPanic@vmkernel#nover+0xf stack: 0x15755a45, 0x8, 0x453ac251bc80, 0x453ac251bc40, 0x0
[email protected]#0.0.0.1+0x4c stack: 0x453ac251bc80, 0x453ac251bc40, 0x0, 0x45de1b36f500, 0x4200354ef90a
[email protected]#0.0.0.1+0x4d7 stack: 0x15752a00, 0x432e45af3368, 0x45bdb6f18048, 0x45de1b36eba8, 0x45de1>
[email protected]#0.0.0.1+0xaec stack: 0x45de1b36eba8, 0xb000000, 0x1328752b134e02, 0x300000040, 0x10
[email protected]#0.0.0.1+0x146 stack: 0x1, 0x40000, 0x0, 0x1, 0x6f632d704d4f447a
vmkWorldFunc@vmkernel#nover+0x31 stack: 0x420032b3a230, 0x0, 0x453ac251f000, 0x453abeb1f100, 0x453ac251f100
CpuSched_StartWorld@vmkernel#nover+0xe2 stack: 0x0, 0x420032adbe00, 0x0, 0x0, 0x0
Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0, 0x0, 0x0, 0x0, 0x0
VMware ESXi 8.0.2 [Releasebuild-22380479 x86_64]

 

Environment

vSAN ESA 8.0 GA

vSAN ESA 8.0 U1

vSAN ESA 8.0 U2

vSAN ESA 8.0 U3

Cause

 
Under rare conditions vSAN ESA stack encounters a deadlock which leads to PSOD.

Resolution

Upgrade the cluster to vSphere 8.0 U3b which contains the fix.

Additional Information

This issue is likely seen on vSAN ESA version between 8.0 GA and 8.0U3