1/4
VM won’t boot after a node failover? My UEFI vs SeaBIOS checklist before escalating
  

George Fady Lv2  Posted 2026-Oct-27 20:03

I am George Fady, I am a technical support engineer in Sangfor.
One pattern I keep seeing after a node failover or a fresh VM creation on HCI: the VM powers on, but the install or boot screen just doesn’t show up - no obvious error, just a stuck or black screen. Before escalating, this is the order I check:

  • Boot mode mismatch - some installation ISOs don’t support UEFI. If UEFI is selected in the VM’s boot settings but the ISO doesn’t support it, the install screen will simply fail to render. Switching the boot mode to SeaBIOS usually resolves it immediately.

  • Boot order - confirm the CD/DVD drive with the ISO attached is actually first in the boot order, not the (empty) system disk.

  • VM boot config missing - a corrupted or missing boot config shows the same symptom as a boot-order problem, so don’t stop at step 2 if the CD is already first.

  • Black screen after power-on - this is often console/display driver related rather than the VM actually failing, so I check the console output before assuming the VM itself crashed.

  • Stuck on initiate page - if it hangs exactly here, I treat it as a different fault path than a true boot failure and check the underlying node health before touching the VM config again.

Running through these five in order has saved me a lot of “let’s just reinstall the VM” tickets. Question for the community: which of these five do you hit most often in your environment, and is there a step you’d add that isn’t on this list?

Like this topic? Like it or reward the author.

Creating a topic earns you 5 coins. A featured or excellent topic earns you more coins. What is Coin?

Enter your mobile phone number and company name for better service. Go