ESXi host running on HPE Gen11 hardware become unresponsive and stuck at banner screen intermittently
search cancel

ESXi host running on HPE Gen11 hardware become unresponsive and stuck at banner screen intermittently

book

Article ID: 450081

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • ESXi hosts may become unresponsive, leading to a loss of management connectivity. During this state, the host console remains stuck at the banner screen and does not respond to standard keyboard shortcuts, leading to physical reboot of the host hardware as the only possibility to recover. 

  • ESXi Log File: /var/log/vmkernel.log
    Description: HPE Integrated Lights-Out (iLO) log spam
    YYYY-MM-DDTHH:MM:SS.XXXZ In(182) vmkernel: cpu64:2100023)FSS: 7434: Failed to open file 'hpilo-d0ccXX'; Requested flags 0x5, world: 2100023 [sut], (Existing flags 0x5, world: 2100188 [ahsdv]): Busy
    YYYY-MM-DDTHH:MM:SS.XXXZ In(182) vmkernel: cpu64:2100023)FSS: 7434: Failed to open file 'hpilo-d0ccXX'; Requested flags 0x5, world: 2100023 [sut], (Existing flags 0x5, world: 2100188 [ahsdv]): Busy
    YYYY-MM-DDTHH:MM:SS.XXXZ In(182) vmkernel: cpu65:2100023)FSS: 7434: Failed to open file 'hpilo-d0ccXX'; Requested flags 0x5, world: 2100023 [sut], (Existing flags 0x5, world: 2100188 [ahsdv]): Busy
    YYYY-MM-DDTHH:MM:SS.XXXZ In(182) vmkernel: cpu64:2100023)FSS: 7434: Failed to open file 'hpilo-d0ccXX'; Requested flags 0x5, world: 2100023 [sut], (Existing flags 0x5, world: 2100188 [ahsdv]): Busy
    YYYY-MM-DDTHH:MM:SS.XXXZ In(182) vmkernel: cpu79:2100023)FSS: 7434: Failed to open file 'hpilo-d0ccXX'; Requested flags 0x5, world: 2100023 [sut], (Existing flags 0x5, world: 2100188 [ahsdv]): Busy
    YYYY-MM-DDTHH:MM:SS.XXXZ In(182) vmkernel: cpu73:2100023)FSS: 7434: Failed to open file 'hpilo-d0ccXX'; Requested flags 0x5, world: 2100023 [sut], (Existing flags 0x5, world: 2100188 [ahsdv]): Busy

  • ESXi Log File: /var/run/log/vmksummary.log
    Description: Firmware-level issue in the BIOS/ROM where the system receives System Management Interrupts (SMI) at an excessively high rate, specifically related to SPD DIMM service requests, causing the processor to remain in a high-priority interrupt level.
    YYYY-MM-DDTHH:MM:SS.XXXZ In(14) heartbeat[19247697]: up 228d12h1m59s, 88 VMs; [[2110355 vmx 33553720kB] [17255990 vmx 37745544kB] [15035702 vmx 67107348kB]] [[19247696 sh 0%max]], [numSMI 22950]
    YYYY-MM-DDTHH:MM:SS.XXXZ In(14) heartbeat[19250041]: up 228d13h1m59s, 88 VMs; [[2110355 vmx 33553736kB] [17255990 vmx 37745552kB] [15035702 vmx 67108448kB]] [[19250046 sh 0%max]], [numSMI 22952]
    YYYY-MM-DDTHH:MM:SS.XXXZ In(14) heartbeat[19252365]: up 228d14h2m0s, 88 VMs; [[2110355 vmx 33553716kB] [17255990 vmx 37745456kB] [15035702 vmx 67108448kB]] [[19252366 sh 0%max]], [numSMI 22954]

Environment

  • vSphere ESXi 8.0
  • Various models of HPE Gen11 hardware 

Cause

HPE has reported various models of Intel Based Gen11 hardware require Firmware Update to resolve systems that potentially stop responding during normal operation.

Resolution

Engage with HPE Support to apply the latest firmware, drivers, and ESXi patches to align with the current hardware compatibility list.

Additional Information

Powered by Wolken Software