ESXi Host Crashes with PSOD in FT and vSAN Deployment
search cancel

ESXi Host Crashes with PSOD in FT and vSAN Deployment

book

Article ID: 387255

calendar_today

Updated On:

Products

VMware vSphere ESXi 8.0

Issue/Introduction

ESXi host with Fault Tolerance and vSAN configuration encountered a PSOD with the a message similar to the below backtrace : 

YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)@BlueScreen: #PF Exception 14 in world 2097356:reapWorker-3 IP 0x42002eb23c0a addr 0x452777d000e8
YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)Code start: 0x42002ea00000 VMK uptime: 0:00:21:14.059
YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)0x45390661be28:[0x42002eb23c0a]SimpleBuddy_GetOpaque@vmkernel#nover+0x2 stack: 0x1
YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)0x45390661be30:[0x42002eb54ae2]XMap_Unmap@vmkernel#nover+0x2b stack: 0x43136fe42010
YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)0x45390661be50:[0x4200300c226b]FTCptFreePageMap@(ftcpt)#<None>+0x40 stack: 0x420030109c7f
YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)0x45390661be90:[0x4200300c4776]FTCptSessionInfoCleanup@(ftcpt)#<None>+0x4f3 stack: 0x45393461f000
YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)0x45390661bed0:[0x4200300c8971]FTCpt_QuiesceCallback@(ftcpt)#<None>+0x32 stack: 0x103
YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)0x45390661bee0:[0x42002eb52b21]World_TryReap@vmkernel#nover+0x1ba stack: 0x45392bd9f000
YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)0x45390661bfa0:[0x42002eb1c3ea]ReaperWorkerWorld@vmkernel#nover+0xaf stack: 0x45390659f100
YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)0x45390661bfe0:[0x42002ee2c015]CpuSched_StartWorld@vmkernel#nover+0xe2 stack: 0x0
YYYY-MM-DDTHH:MM:SSZ cpu1:2097356)0x45390661c000:[0x42002eadbdff]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0

Environment

VMware vSphere ESXi 8.0

Cause

Network disruption to FT and vSAN network connectivity can trigger this issue.

During a failover of a Primary VM protected by vSphere Fault Tolerance, if there are unresolved I/O operations between the VM and the ESXi host, the host may intermittently experience a failure, resulting in a purple diagnostic screen (PSOD).

Resolution

This issue is resolved in ESXi 8.0 U2b Build 23305546.

 

Additional Information

Powered by Wolken Software