VM Stuck After Reboot – Emergency Mode & CPU Soft Lockup Errors
search cancel

VM Stuck After Reboot – Emergency Mode & CPU Soft Lockup Errors

book

Article ID: 397153

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

OS encountered problems after a reboot, leading to the following issues:

  •  Entered Emergency Mode with a locked root account.

  • Experienced a CPU soft lockup, causing system instability.

Environment

vCenter Server 8.0.x

vSphere ESXi 7.x

vSphere ESXi 8.x

Cause

 

  • The VM entered Emergency Mode due to potential filesystem corruption or misconfigured system files.

  • The root account was locked, preventing administrative access.

  • Watchdog BUG: CPU soft lockup errors were observed.

  • Possible causes include high CPU utilization, kernel bugs.

 

Resolution

Engaging the OS Team / vendor is recommended to ensure proper resolution.

Fix any possible File system corruption.

And to mitigate any possible OS Kernel bugs.

 

Additional Information

  • Analyze system logs and performance metrics to identify the root cause of the soft lockup, such as a resource bottlenecks. 
  • Adjust application settings or resource allocation to minimize potential CPU intensive operations. 
  • Update to the latest kernel version as it may include bug fixes related to soft lockup detection. 
Powered by Wolken Software