Latest revision as of 08:19, 22 March 2012

Description

Reserve crashkernel for kdump by grubby

grubby --args="crashkernl=128M" --update-kernel=$(grubby --default-kernel)

Reboot system and check /proc/cmdline

cat /proc/cmdline | grep "crashkernel"

Edit /etc/kdump.conf. This is an example:

 ext4 /dev/mapper/vg_dhcp6558-lv_root

core_collector makedumpfile --nosuchoptions

default halt

@@ Line 3: / Line 3: @@
 |setup=
 #Install Fedora 17 on your machine
-#After system installed, check if kexec-tools kernel-debuginfo and crash is installed via <pre>rpm -q kexec-tools kernel-debuginfo crash</pre> Or via yum <pre>yum install kexec-tools kernel-debuginfo crash</pre>
+#After system installed, check if kexec-tools kernel-debuginfo and crash is installed via <pre>rpm -q kexec-tools</pre> Or via yum <pre>yum install kexec-tools</pre>
 #Reserve crashkernel for kdump by grubby <pre>grubby --args="crashkernl=128M" --update-kernel=$(grubby --default-kernel)</pre> Reboot system and check /proc/cmdline <pre>cat /proc/cmdline | grep "crashkernel"</pre>
-#Edit /etc/kdump.conf, add this line:<pre> ext4 /dev/mapper/vg_dhcp6558-lv_root</pre><pre>core_collector makedumpfile -E -d 31</pre>
+#Edit /etc/kdump.conf. This is an example:<pre> ext4 /dev/mapper/vg_dhcp6558-lv_root</pre><pre>core_collector makedumpfile --nosuchoptions</pre><pre>default halt </pre>
-#Apply changes and start kdump via service kdump restart
+#Apply changes and start kdump via <pre>service kdump restart</pre>
 |actions=
 #Trigger crash via: <pre>echo c > /proc/sysrq-trigger</pre>
 |results=
-#Test failed if <pre>cat /proc/cmdline | grep "crashkernel"</pre> got nothing means reserve crashkernel memory failed
+#System halt
-#Test failed if restart kdump failed
-#Test suspend if rpm packages couldn't be installed
 }}
 [[Category:Kdump_Test_Cases]]