rpms/kexec-tools
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

kexec-kdump-howto.txt: Add document about encrypted targets

Browse Source 
Currently kdump is not working well with encrypted targets, add document
about this issue.

Signed-off-by: Kairui Song <kasong@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
This commit is contained in:
Kairui Song 2019-05-10 15:11:26 +08:00
parent f544a12e78
commit 8d4db658fd
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
kexec-kdump-howto.txt
View File

@ -684,6 +684,20 @@ a machine with a disk image which have kdump initramfs embedded, you
should rebuild the initramfs using "kdumpctl rebuild" command manually, should rebuild the initramfs using "kdumpctl rebuild" command manually,
or else kdump may not work as expeceted. or else kdump may not work as expeceted.
Notes on encrypted dump target:
Currently, kdump is not working well with encrypted dump target.
First, user have to give the password manually in capture kernel,
so a working interactive terminal is required in the capture kernel.
And another major issue is that an OOM problem will occur with certain
encryption setup. For example, the default setup for LUKS2 will use a
memory hard key derivation function to mitigate brute force attach,
it's impossible to reduce the memory usage for mounting the encrypted
target. In such case, you have to either reserved enough memory for
crash kernel according, or update your encryption setup.
It's recommanded to use a non-encrypted target (eg. remote target)
instead.
Parallel Dumping Operation Parallel Dumping Operation
========================== ==========================
Kexec allows kdump using multiple cpus. So parallel feature can accelerate Kexec allows kdump using multiple cpus. So parallel feature can accelerate