-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kdump: Update kdump kernel_param_cmd command for different OS version #4146
Conversation
Hi @MiriamDeng and @fbq815, Would you guys want to check multi-arch for this part? Thanks in advance, |
Test Result
The above three failures are known issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
RESULTS : PASS 4 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
The patch looks good to me from code view. Hi @maxujun, could you please give a hand to try it on ppc side as you are the only person working on it now ? Thank you ! :) |
(01/20) Host_RHEL.m8.u10.product_rhel.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.10.0.ppc64le.io-github-autotest-qemu.kdump.one_vm: STARTED LGTM,Acked. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Hi @vivianQizhu, Could you help review this as well? Thanks : ) |
Based on RHEL-41849, the `crashkernel=auto` parameter is no longer supported in the latest RHEL versions. We should use the `kdumpctl reset-crashkernel` command to reset crashkernel values to our default settings. Signed-off-by: wji <[email protected]>
Based on RHEL-41849, the
crashkernel=auto
parameter is no longer supported in the latest RHEL versions. We should use thekdumpctl reset-crashkernel
command to reset crashkernel values to our default settings.ID: 2654
Signed-off-by: wji [email protected]