How should the crashkernel parameter be configured for using kdump on Red Hat Enterprise Linux 9 ?
Issue
- When configuring the crashkernel parameter the kdump service fails to start:
# systemctl status kdump.service
○ kdump.service - Crash recovery kernel arming
Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Wed 2022-01-26 23:28:22 IST; 8s ago
└─ ConditionKernelCommandLine=crashkernel was not met
Jan 26 23:26:16 localhost systemd[1]: Condition check resulted in Crash recovery kernel arming being skipped.
Jan 26 23:28:22 localhost.localdomain systemd[1]: Condition check resulted in Crash recovery kernel arming being skipped.
- What is the correct crashkernel parameter for kdump to work?
- "crashkernel reservation failed - memory is in use" errors when kernel panics
Environment
- Red Hat Enterprise Linux 9
- all supported architectures
- kdump
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.