An ESXi host experiences a Purple Screen of Death (PSOD) while attempting to delete a stale vSAN object. The panic occurs with a timeout message related to the Durable Log (DLog) quiesce state.
Panic Details: Crash at 2026-04-29T15:52:54.489Z on CPU 43 running world 2099620 - zDOM-com p10/t0. VMK Uptime:266:09:26:40.652
Panic Message: @BlueScreen: ########-####-####-####-########ba6: object exit timeout: quiesceState=busy-dlog latUSec=360003403 (17969)
Backtrace:
0x453a0061bc00:[0x42002277bb40]PanicvPanicInt@vmkernel#nover+0x20c stack: 0x453a0061bcc0, 0x42002277bb40, 0x0, 0x420000000001, 0x42002277bb40
0x453a0061bcb0:[0x42002277c33c]Panic_vPanic@vmkernel#nover+0x25 stack: 0x1575374b, 0x420022797bff, 0x5, 0x4200254f3ca8, 0x1575374b
0x453a0061bcd0:[0x420022797bfe]vmk_vPanic@vmkernel#nover+0xf stack: 0x1575374b, 0x45bc00000008, 0x453a0061bd40, 0x453a0061bd00, 0x0
0x453a0061bce0:[0x4200254f3ca7][email protected]#0.0.0.1+0x4c stack: 0x453a0061bd40, 0x453a0061bd00, 0x0, 0x45bc74753c68, 0x42002562481b
0x453a0061bd40:[0x420025557d08][email protected]#0.0.0.1+0x495 stack: 0x15752a00, 0x4341bd240800, 0x1, 0x45db92da4c18, 0x45bc747529e8
0x453a0061bda0:[0x42002554d004][email protected]#0.0.0.1+0xd45 stack: 0x9e62c7b067ed2c95, 0xa69b1da73e30cde3, 0x44000, 0x51c4f78b3aeab1, 0x0
0x453a0061bf50:[0x4200254f2c83][email protected]#0.0.0.1+0x1e4 stack: 0x6f632d704d4f447a, 0x30742d3031702d6d, 0x303236393930322d, 0x4341bd253b00, 0x82
0x453a0061bfa0:[0x42002279f778]vmkWorldFunc@vmkernel#nover+0x31 stack: 0x42002279f774, 0x0, 0x453a0061f000, 0x4539ff31f100, 0x453a0061f100
0x453a0061bfe0:[0x420022cd67b2]CpuSched_StartWorld@vmkernel#nover+0xbf stack: 0x0, 0x420022744c70, 0x0, 0x0, 0x0
0x453a0061c000:[0x420022744c6f]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0, 0x0, 0x0, 0x0, 0x0
Running routine processdump.
VMware ESXi 8.0.3 build-24022510 or lower
A deadlock can occur in this scenario, which leads to a PSOD to preserve data integrity.
This issue is resolved in VMware ESXi 8.0 Update 3 Patch 04 (8.0U3P04) and later releases.