Install Fedora CoreOS and debug kernel crashes using kdump as described in documentation.
- Download and verify the latest FCOS next image (pick the right image for your environment).
How to test
- Create an Ignition file. When writing the configuration, add a
crashkernel=300Msection following the example in the documentation. You don't necessarily need to add it in the ignition, you can do it via rpm-ostree as described in this documentation, you also need to make sure the kdump.service will be enabled, you can do same via ignition or via
systemctl enable kdump.service.
- Launch your Fedora CoreOS system using this Ignition file. See the Quickstart and the provisioning docs for a guide how to launch FCOS in most environments (bare metal, virtual, cloud, etc).
- Acess your Fedora CoreOS and force a kernel panic for testing.
sudo systemctl enable kdump.service echo 1 > /proc/sys/kernel/sysrq echo "c" > /proc/sysrq-trigger
- You can SSH successfully into your FCOS system.
- The kernel arguments (as seen in the /proc/cmdline file) are as specified in the Ignition config, or via rpm-ostree after the reboot
- After FCOS is rebooted you can successfully see the vmcore and other log files created under
- The linked documentation makes sense, nothing is obviously missing, and the instructions are clear.