Ack to the report.
While I had some systems (lpar) which worked I was trivially able to confirm
that it doesn't work on KVM guests based on cloud images.
I see this on install of kdump-tools (default answers to debconf)
Setting up kdump-tools (1:1.6.4-2) ...
Using config file '/etc/zipl.conf'
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Preparing boot device: vda (0000).
Done.
Creating config file /etc/default/kdump-tools with new version
But that leaves /etc/zipl.conf unmodified.
Frank already copied the snippet in the report.
This line isn't working:
$ sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}"
/etc/zipl.conf
At least in my guest and my LPARs the following seemed better, so for
your consideration:
$ sed -i "s/^parameters\s*=/& crashkernel=${DEF_PRESET} /"
/etc/zipl.conf
Note: at this point it already checked there is no crashkernel statement
yet, so we can unconditionally insert it here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790788
Title:
Customize 'crashkernel' parameter is not properly working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
