Bug 432242
Summary: | Feature Request: Kdump kickstart | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Jong Bae KO <jko> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.1 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-10 18:31:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jong Bae KO
2008-02-10 11:32:59 UTC
%post chkconfig kdump on This isn't enable kdump. You have to modify the bootloader configuration to pass a crashkernel string on the kernel command line. Perhaps you should run system-config-kdump (or firstboot) on a freshly installed system to enable kdump, then examine /boot/grub/grub.conf and /etc/kdump.conf to see what needs to be configured before the service can be fully enabled. Once you have modified the kernel command line in the bootloader configuration you will need to reboot your system so that the new settings take effect. Once you have done this, it will be clear to you what you need to do in your kickstart %post. |