This is a short documentation on how to setup kdump on live images. All steps was tested on Fedora 25 Alpha LiveCD and successfully saved vmcore captured by kdump to a USB stick.
Signed-off-by: Tong Li tonli@redhat.com --- live-image-kdump-howto.txt | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 live-image-kdump-howto.txt
diff --git a/live-image-kdump-howto.txt b/live-image-kdump-howto.txt new file mode 100644 index 0000000..e57e75b --- /dev/null +++ b/live-image-kdump-howto.txt @@ -0,0 +1,23 @@ +Kdump now works on live images with some manual configurations. Here is the step +by step guide. + +1. Enable crashkernel reservation + +Since there isn't any config files that can be used for adding kernel parameters +for Live images, we have to append 'crashkernel' argument in boot menu every +time we boot a Live image. + +2. Change dump target in /etc/kdump.conf + +When kdump kernel boots in a live environment, the default target /var/crash is +in in ram so you need change the dump target to an external disk or an network +dump target. + +3. Start kdump service + + $ kdumpctl start + +4. Trigger a kdump test + + $ echo 1 > /proc/sys/kernel/sysrq + $ echo c > /proc/sysrq-trigger
On 10/13/16 at 04:16pm, Tong Li wrote:
This is a short documentation on how to setup kdump on live images. All steps was tested on Fedora 25 Alpha LiveCD and successfully saved vmcore captured by kdump to a USB stick.
Signed-off-by: Tong Li tonli@redhat.com
live-image-kdump-howto.txt | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 live-image-kdump-howto.txt
diff --git a/live-image-kdump-howto.txt b/live-image-kdump-howto.txt new file mode 100644 index 0000000..e57e75b --- /dev/null +++ b/live-image-kdump-howto.txt @@ -0,0 +1,23 @@ +Kdump now works on live images with some manual configurations. Here is the step +by step guide.
+1. Enable crashkernel reservation
+Since there isn't any config files that can be used for adding kernel parameters +for Live images, we have to append 'crashkernel' argument in boot menu every +time we boot a Live image.
+2. Change dump target in /etc/kdump.conf
+When kdump kernel boots in a live environment, the default target /var/crash is
~into
+in in ram so you need change the dump target to an external disk or an network
~~duplicate
+dump target.
+3. Start kdump service
- $ kdumpctl start
+4. Trigger a kdump test
- $ echo 1 > /proc/sys/kernel/sysrq
- $ echo c > /proc/sysrq-trigger
-- 2.7.4 _______________________________________________ kexec mailing list -- kexec@lists.fedoraproject.org To unsubscribe send an email to kexec-leave@lists.fedoraproject.org
On Thursday 13 October 2016 03:51 PM, Baoquan He wrote:
On 10/13/16 at 04:16pm, Tong Li wrote:
This is a short documentation on how to setup kdump on live images. All steps was tested on Fedora 25 Alpha LiveCD and successfully saved vmcore captured by kdump to a USB stick.
It seems, you will need V3. It would be good if you send V3 of both the patch as series.
Use `git format-patch -C -M --thread=shallow HEAD~2` to create a series of both of your patches.
If you want to add a coverletter as well, then you may use
`git format-patch -C -M --thread=shallow --cover-letter`
Signed-off-by: Tong Li tonli@redhat.com
live-image-kdump-howto.txt | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 live-image-kdump-howto.txt
diff --git a/live-image-kdump-howto.txt b/live-image-kdump-howto.txt new file mode 100644 index 0000000..e57e75b --- /dev/null +++ b/live-image-kdump-howto.txt @@ -0,0 +1,23 @@ +Kdump now works on live images with some manual configurations. Here is the step +by step guide.
+1. Enable crashkernel reservation
+Since there isn't any config files that can be used for adding kernel parameters +for Live images, we have to append 'crashkernel' argument in boot menu every +time we boot a Live image.
+2. Change dump target in /etc/kdump.conf
+When kdump kernel boots in a live environment, the default target /var/crash is
~into+in in ram so you need change the dump target to an external disk or an network
~~duplicate+dump target.
to change the.......... ..... a network
+3. Start kdump service
- $ kdumpctl start
+4. Trigger a kdump test
- $ echo 1 > /proc/sys/kernel/sysrq
- $ echo c > /proc/sysrq-trigger
Thanks ~Pratyush