RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

IIUC the same holds on IBM Z:
On RHEL 9:

```
# kdumpctl get-default-crashkernel
1G-4G:192M,4G-64G:256M,64G-:512M
```

which I can confirm to have been set both in the BLS entries and in the /proc/cmdline.

Furthermore, under "Update the bootloader configuration:"

# grubby --update-kernel ALL --args "crashkernel=<CUSTOM-VALUE>":

on IBM Z, users must additionally run the 'zipl' command (as-is, no arguments) afterwards to make sure the boot entries are updated.

Reported by: smitterl

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_monitoring_and_updating_the_kernel/configuring-kdump-on-the-command-line_managing-monitoring-and-updating-the-kernel#annotations:1f6986e9-baab-4266-9f2b-a67e3ebd5e5a

Created this feedback from "11.1. Configuring kdump memory usage".

Annotation: 

crashkernel default memory size works on IBM Z, but for bootloader configuration on IBM Z machines, add no arguments