ESXi 9.1 Host Experiences PSOD During Installation on HPE Hardware
search cancel

ESXi 9.1 Host Experiences PSOD During Installation on HPE Hardware

book

Article ID: 443904

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • ESXi 9.1 hosts may encounter a PSOD during installation on HPE ProLiant DL380 Gen11 hardware, limited to the PSOD stacks listed below.

  • VMware ESXi 9.1.0 [Rclcasebuild-25378933 x86_61 (default: ULM)
    PANIC bora/vmkernel/main/dlmalloc.c:4914 - Corruption in dlmalloc

    Module(s) involved in panic: [vmkernel Version Releasebuild-25370933]
    cr0=0x8001003b cr2=0x1b5cc917a2 cr3=0x6370e000 cr4=0x34216c
    FMS=06/cf/2 uCode=0x210002e0
    -PCPU12:2097417/reapHorker-45

    Code start: 0x420020200000 VMK uptime: 1:06:05:30.189
    0x453a4425bcb0:[0x42002044e370]PanicvPanicInt@vnkernellnover*0x1c4 stack: 0x60000003f
    0x453a4425bd80:[0x42002044eba8]Panic_NoSave@vmkernel#nover+0x5d stack: 0x453a4425bda0
    0x453a4425bde0:[0x4200203f45a7]DLM_free@vmkernel#nover+0x538 stack: 0x43laa7e183a0
    0x453a4425be00:[0x4200203fe4b2]Heap_Free@vnkernel#nover+0xb7 stack: 0x453a4425beb8
    0x453a4425bc50:[0x420020904c09]User_Wor ldCleanup@vmkerncl#nover+0x102 stack: 0xlc
    0x453a4425be80: [0x42002042b82f ]InitTable_Cleanup@vmkernellnover+0x2c stack: 0x431632001220
    0x453a4425bca0:[0x42002049883d]Wor ld_TryRcap@vnkernel#nover+0x4c6 stack: 0x2001
    0x453a4425bf90:[0x42002045460e]ReaperHorkerHor ld@vmkernellnover+0xcb stack: 0x0
    0x453a4425bfe0:[0x420020223eef ]CpuSched_StartWor ld@vnkernel#nover+0xe8 stack: 0x0
    0x453a4425c000:[0x42002040cb67]Debug_IsInitialized@vnkernelinover+0x10 stack: 0x0
    base fs=0x0 gs=0x420043000000 Kgs=0x0
    2026-05-20112:19:32.851Z cpu6:2100145)VM: 1422: Defaulting monitor to ULM
    0:00:00:06.215 cpu0:2097152)LLSwap: 3832: Host Cache will be deprecated in the next na jor release.
    No disk partition configured to dump data.
    Dump completed successfully.
    FileDunp: Successful
    No port for renote debugger.

Crash Dump 2: 

  • List_RemoveNoReinit (itemPtr=<optimized out>) at bora/vmkernel/public/list.h:436
    List_Remove (itemPtr=<optimized out>) at bora/vmkernel/public/list.h:438
    List_Remove (itemPtr=<optimized out>) at bora/vmkernel/public/list.h:436
    UserMemUnmapLocked (world=world@entry=0x453a60f5f000, addr=addr@entry=4096, length=length@entry=4398046502912, fromUser=fromUser@entry=0 '\000', isUnmap=isUnmap@entry=1 '\001') at bora/vmkernel/user/userMem.c:7007
    0x000042001dd2c574 in UserMem_Unmap (world=0x453a60f5f000, addr=addr@entry=4096, length=length@entry=4398046502912, fromUser=fromUser@entry=0 '\000') at bora/vmkernel/user/userMem.c:8746
    0x000042001dd2c9ef in UserMem_EarlyCartelCleanup (world=<optimized out>) at bora/vmkernel/user/userMem.c:4511
    0x000042001dd0129e in UserModuleTableRun (table=table@entry=0x42001dfc07c0, startIndex=startIndex@entry=11, endIndex=endIndex@entry=0, doInit=doInit@entry=0 '\000', world=0x453a60f5f000, lastIdx=lastIdx@entry=0x453a60f5bde8) at bora/vmkernel/user/user.c:3490
    0x000042001dd02800 in UserModuleTableRunCleanup (startAt=11, table=0x42001dfc07c0, world=<optimized out>) at bora/vmkernel/user/user.c:3530

Crash Dump 3: 

VMware ESXi 9.1.0 [Rclcoscbuild-25378933 x06_64] (default: ULM)
VERIFY bora/vnkernel/public/list.h:411

Mndule(s) invnlved in panir: [vmkernel Version Releasehuild-253709331
cr0=0x00010031 cr2=0x2cer502766 rr3-Ax1735h6A88 cr4-Gx342768
FMS=06/cf/2 uCode=Ax210002eA
Trane-0x453a60f5bab0 ip-0x42001dd27ccf er-@x0 rflags-8x1026
ax-0xB rbx-0x1000 rex-Đx43166d802a18
rdx-0x43166d80f080 rbp-OxD rsi-0x43166d88f888
di-0x2cec4e1000 r8-0x0 r9-0x2cec4e3008
-10-0x431660802010 r11-0x0 r12-0xB
.13-0xU r14-0x3frrrfff000 r15-Bx43166088efce
*PCPU58:2278937/localeli
CPU

Code start: Ox12001d600000 VMK uptine: 1:03:29:07.336
0x153a60f5bb70:[0x12001dd27ccf JUserMewUnmapLocked@vrkernel#nover .0x303 stack: 0x2ceacf0
0x153a60f5bd10:[0x42001dd2c573]UserMcm_Unmap@vmkernel#nover,0x68 stack: 0x12001dfc07c0
0x153a60f5bd50:[0x12001dd2c9cc ]UserMen_EarlyCartclClcanup@vnkerncl#nover+0x1f stock: 0x153a60fSbdc8
0x453a60f5bd60:[0x42001ddB129d]UserModulcTablcRun@vrkernel#nover +0x8a stack: 0x2ccacf0650
0x453a60f5bdb0:[0x42001ddB27ff]User_ExitDeadThrcod@vrkernel#nover+0x2a0 stack: 0x0
0x453a60f5bc50:[0x42001dd039o6]User_Except lon@vmkernel#nover+0xdb stack: 0x453a60r5r000
0x453a60f5bcb0:[0x42001ddf5c01]IDT_Goncr icExc@vmkernel#nover+0x29o stack: 0x6o0f44c4
0x453a60f5bf40:[Ox4200lddeffce]gate_cntry@vwkernel#nover+Gxaf stack: 0x0
basc fs=0x0 qs=0x42004c000000 Kqs=0x8
2026-05-20T14:10:29.436Z cpu79:21A0143)VM: 1422: Defaulting monitor to ULM
0:00:00:06.241 cpu0:2097152)LLSwop: 3032: Host Cache will he deprecated in the next no jor relense.
No disk partition configured to dunp data.
Dunp in progress, do not pouer off: Collecting userunr ld dunps (15/16) .. Recursive panic (cpu 58, wor ld 2278937, depth 1): ip-Ax
42001ddfbb57 randonnff=Ax1dGDDAAA:
#PF Exceptinn 14 in world 2278937:localcli IP 8x42881dd38c25 addr 8x30
PTES:0x19f80027:0x007A50007:0x0:
No port for renote debugger.

Environment

Esx 9.1

Cause

This issue is caused by third-party software installed on ESXi, which leads to intermittent memory corruption and results in portions of memory being unexpectedly zeroed out.

 

Resolution

Since the issue is attributed to third-party software components installed on ESXi, we recommend engaging the HPE team for further investigation.

Powered by Wolken Software