Failed to start kdump on Hyper-V due to "No memory reserved for crash kernel"

Solution Verified - Updated -

Issue

  • The VM on Hyper-V failed to start kdump due to "No memory reserved for crash kernel".
  • The kernel failed to reserve 192MB memory for crash kernel due to crashkernel: invalid size in the early stage of the boot sequence.
  • kdump service enabled but fails on proxmox vms running rhel10 with hotplug enabled

Environment

  • Red Hat Enterprise Linux
  • VM on Hyper-V
  • Proxmox VM

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content