Blame live-image-kdump-howto.txt
|
Petr Šabata |
f5bf49 |
Kdump now works on live images with some manual configurations. Here is the step
|
|
Petr Šabata |
f5bf49 |
by step guide.
|
|
Petr Šabata |
f5bf49 |
|
|
Petr Šabata |
f5bf49 |
1. Enable crashkernel reservation
|
|
Petr Šabata |
f5bf49 |
|
|
Petr Šabata |
f5bf49 |
Since there isn't any config file that can be used to configure kernel
|
|
Petr Šabata |
f5bf49 |
parameters for live images before booting them, we have to append 'crashkernel'
|
|
Petr Šabata |
f5bf49 |
argument in boot menu every time we boot a live image.
|
|
Petr Šabata |
f5bf49 |
|
|
Petr Šabata |
f5bf49 |
2. Change dump target in /etc/kdump.conf
|
|
Petr Šabata |
f5bf49 |
|
|
Petr Šabata |
f5bf49 |
When kdump kernel boots in a live environment, the default target /var/crash is
|
|
Petr Šabata |
f5bf49 |
in RAM so you need to change the dump target to an external disk or a network
|
|
Petr Šabata |
f5bf49 |
dump target.
|
|
Petr Šabata |
f5bf49 |
|
|
Petr Šabata |
f5bf49 |
Besides, make sure that "default dump_to_rootfs" is not specified.
|
|
Petr Šabata |
f5bf49 |
|
|
Petr Šabata |
f5bf49 |
3. Start kdump service
|
|
Petr Šabata |
f5bf49 |
|
|
Petr Šabata |
f5bf49 |
$ kdumpctl start
|
|
Petr Šabata |
f5bf49 |
|
|
Petr Šabata |
f5bf49 |
4. Trigger a kdump test
|
|
Petr Šabata |
f5bf49 |
|
|
Petr Šabata |
f5bf49 |
$ echo 1 > /proc/sys/kernel/sysrq
|
|
Petr Šabata |
f5bf49 |
$ echo c > /proc/sysrq-trigger
|