Due to a rare race condition, an ESXi host might fail with a purple diagnostic screen after a failover of the vmnic when vSAN is used over RDMA.
The ESXi log was as follow:--vmkernel.log--YYYY-MM-DDTHH:MM:SSZ cpu89:2098969)World: 3355: PRDA 0x420056400000 ss 0x0 ds 0x750 es 0x750 fs 0x750 gs 0x750YYYY-MM-DDTHH:MM:SSZ cpu89:2098969)World: 3357: TR 0x758 GDT 0x453a405e9888 (0xffff) IDT 0x42002a09d000 (0xffff)YYYY-MM-DDTHH:MM:SSZ cpu89:2098969)World: 3359: CR0 0x8001003d CR3 0x50660000 CR4 0x14616cYYYY-MM-DDTHH:MM:SSZ cpu89:2098969)Backtrace for current CPU #89, worldID=2098969, fp=0x4336bf83c900YYYY-MM-DDTHH:MM:SSZ cpu89:2098969)0x453af0e1bea0:[0x42002bce596e][email protected]#0.0.0.1+0x142 stack: 0x100000000000750, 0x0, 0x0, 0x420054000000, 0x430384801630YYYY-MM-DDTHH:MM:SSZ cpu89:2098969)0x453af0e1bf70:[0x42002bcd422f][email protected]#0.0.0.1+0x58 stack: 0x72, 0x4336bee11ba0, 0x0, 0x420029b9f7f9, 0x72YYYY-MM-DDTHH:MM:SSZ cpu89:2098969)0x453af0e1bfa0:[0x420029b9f7f8]vmkWorldFunc@vmkernel#nover+0x31 stack: 0x420029b9f7f4, 0x0, 0x453af0e1f000, 0x453aeea9f100, 0x453af0e1f100YYYY-MM-DDTHH:MM:SSZ cpu89:2098969)0x453af0e1bfe0:[0x42002a0d67b2]CpuSched_StartWorld@vmkernel#nover+0xbf stack: 0x0, 0x420029b44cf0, 0x0, 0x0, 0x0YYYY-MM-DDTHH:MM:SSZ cpu89:2098969)0x453af0e1c000:[0x420029b44cef]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0, 0x0, 0x0, 0x0, 0x0YYYY-MM-DDTHH:MM:SSZ cpu89:2098969)VMware ESXi 8.0.3 [Releasebuild-######## x86_64#PF Exception 14 in world 2098969:rdtNetworkWo IP 0x42002bce596e addr 0x8PTEs:0x101bab5e023;0x101bab5f023;0x101bab6c023;0x0;
VMware ESXi 8.0
This issue is resolved in the VMware ESXi 8.0 Update 3i (Build 25205845)
VMware ESXi 8.0 Update 3i Release Notes
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/esxi-update-and-patch-release-notes/vsphere-esxi-80u3i-release-notes.html