An ESXi host becomes unresponsive and displays a Purple Screen of Diagnostics (PSOD) with the below output.
cpu##:########)@BlueScreen: #PF Exception 14 in world ########:prealloc-1 IP 0x############ addr 0x## ...cpu##:########)Backtrace for current CPU ###, worldID=########, fp=0x1cpu##:########)0x############:[0x############]VmMemPf_PreallocRange@vmkernel#nover+0x45 stack: ...cpu##:########)0x############:[0x############]AllocPreallocOneDomain@vmkernel#nover+0x44 stack: ...cpu##:########)0x############:[0x############]Alloc_DomainFnOneCPU@vmkernel#nover+0x57 stack: ...cpu##:########)0x############:[0x############]CpuSched_StartWorld@vmkernel#nover+0xbf stack: ...cpu##:########)0x############:[0x############]Debug_IsInitialized@vmkernel#nover+0xc stack: ...
VMware vSphere ESX 8.x
VMware ESX 9.x
For some types of VMs, such as PCIe passthrough VMs, ESX tries to preallocate memory while the VM powers on.
If the VM is terminated during the memory preallocation, the ESX host might fail with a purple diagnostic screen.
It is caused by very rare race condition between the memory preallocation and the VM termination.
This issue is resolved in the following version:
PR 3539502
This issue is also described in the release note of ESX 8.0u3h and ESX 9.0.1.0.