Failed to start kdump on Hyper-V due to "No memory reserved for crash kernel"
Issue
- The VM on Hyper-V failed to start kdump due to "No memory reserved for crash kernel".
- The kernel failed to reserve
192MBmemory for crash kernel due tocrashkernel: invalid sizein the early stage of the boot sequence. kdumpservice enabled but fails on proxmox vms runningrhel10with 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.