How should the crashkernel parameter be configured for using kdump on Red Hat Enterprise Linux 10 ?

Issue

• When configuring the crashkernel parameter the kdump service fails to start:

# kdumpctl status
kdump: Kdump is not operational

○ kdump.service - Crash recovery kernel arming
     Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; preset: enabled)
     Active: inactive (dead) (Result: exec-condition) since Thu 2025-05-08 16:35:08 IST; 2min 0s ago
 Invocation: 5867b4a368914434b8b7f36b8069391c
  Condition: start condition unmet at Thu 2025-05-08 16:35:08 IST; 2min 0s ago
    Process: 1077 ExecCondition=/bin/sh -c grep -q -e "crashkernel" -e "fadump" /proc/cmdline (code=exited, status=1/FAILURE)
   Mem peak: 1.2M
        CPU: 7ms

May 08 16:35:08 localhost.localdomain systemd[1]: Starting kdump.service - Crash recovery kernel arming...
May 08 16:35:08 localhost.localdomain systemd[1]: kdump.service: Skipped due to 'exec-condition'.
May 08 16:35:08 localhost.localdomain systemd[1]: Condition check resulted in kdump.service - 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