------- Comment From mihaj...@de.ibm.com 2020-10-14 07:51 EDT------- Sorry for not responfing earlier. After installing a new system I can see that the update happening:
$ cat /proc/cmdline root=/dev/mapper/vgubuntu-root crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M However it still turns out that - if using an encrypted volume - it's not possible to unlock the volume from the kdump kernel for a ~2GB VM as the 320MB are still not sufficient. Bumping the VM memory to 4GB will allow the kdump kernel to unlock the volume. I think that either 512M should be the lowest value used for the crashkernel, or at least a warning should be emitted, alerting the system administrator that for a < 4GB machine kdump is not going to work with an encrypted root/dump volume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
