xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2026-09-28 08:10:53 +00:00
Code Issues Releases Wiki Activity

docs(riscv64): describe crash dumps on riscv64 nodes

Browse Source 
Explain why the riscv64 templates disable the installer's kdump add-on,
how to reserve memory for crash dumps on an installed node, and what
diskless images reserve by default.
This commit is contained in:
Vinícius Ferrão
2026-08-21 00:05:48 -03:00
parent 4314781f73
commit ba352c01f6
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/source/guides/admin-guides/manage_clusters/riscv64/index.rst
+16
View File
@@ -75,6 +75,22 @@ package lists add ``grub2-efi-riscv64`` and ``efibootmgr``, and the
these files. After ``nodeset <node> boot`` the firmware boots the installed
system because the per-node ``grub2-<node>`` loader link is removed.
Crash dumps
~~~~~~~~~~~
EL10 defines no default crash kernel reservation for riscv64
(``kdumpctl get-default-crashkernel`` is empty there), so the installer's kdump
add-on writes the literal ``crashkernel=auto``, which the kernel ignores: no
memory is reserved and ``kdump.service`` fails on every installed node. The
riscv64 templates therefore turn that add-on off. To take crash dumps on a
riscv64 node, reserve the memory yourself with a real value, for example::
chdef -t osimage rocky10.2-riscv64-install-compute addkcmdline="crashkernel=256M"
Diskless images use ``linuximage.dump`` and ``linuximage.crashkernelsize`` as on
the other architectures; a riscv64 image with ``dump`` set and no explicit size
reserves 256M.
Stateless (diskless) images
---------------------------