HSAVMCORE.CONF(5)

🎀 HSAVMCORE.CONF(5) — the hsavmcore config file, explained by your favorite unix bestie 🎀

ok so this is the hsavmcore.conf man page, straight out of the File Formats Manual section. it's giving "tiny config file, big responsibilities" and honestly? we love her for it. let's get into it 💅

---

✨ NAME ✨

hsavmcore.conf — the configuration file for the hsavmcore tool, periodt.

---

🌸 DESCRIPTION 🌸

so the hsavmcore.conf configuration file holds, you guessed it, the configuration information for the hsavmcore tool. that's the whole vibe. 🦋

and here's the iconic part: every single specification in the configuration file is optional. literally all of them. if you skip a parameter, the command defaults just apply and everything's chill. no cap. ✨

---

🔥 verbose

this parameter sets the verbosity level of the output messages — like, how much does the tool want to talk to you. these are the pre-defined numeric values you can use:

• 0 — show only error messages (this is the default)
• 1 — show error and warning messages
• 2 — show error, warning and information messages
• 3 — show error, warning, information and debug messages
• 4 — show error, warning, information, debug and trace messages

like, 0 is the strong silent type and 4 will not stop texting you. choose your fighter 💀

---

🌈 mount_debugfs

mount (1) or do not mount (0) debugfs. use this configuration if the kdump kernel does not mount the debugfs during the boot process. lowkey a "the kernel forgot so I'm doing it myself" moment 🫶

---

💖 workdir

specifies a work directory on the kdump system where the hsavmcore tool can create temporary files. and listen — this specification is required if use_hsa_mem is set to 0. yes bestie, required. don't forget it 😭

---

⭐ use_hsa_mem

cache the HSA memory in regular memory (1) or in a file on a file system (0). pick your storage situation, it's giving "where do I put my stuff" energy.

---

🦋 hsa_size

specify a value, in bytes, for the HSA memory size instead of reading the size from /sys/kernel/debug/zcore/hsa. this parameter is intended only to test the hsavmcore tool without being in a kdump kernel — iykyk, it's a test-only girly. specifying -1 falls back to reading the size from /sys/kernel/debug/zcore/hsa.

ngl, that -1 is the "never mind, do it the normal way" escape hatch. iconic.

---

🍓 release_hsa

release (1) or do not release (0) the HSA memory after it is cached by the hsavmcore tool. simple as that, no notes 💅

---

🧚 bind_mount_vmcore

replace (1) the original vmcore file with the new file created by the hsavmcore tool, or keep the original file (0), which no longer contains the information from the HSA memory. set this parameter to 1 if you intend to use kdump tools to create a core dump. like, that's the whole point of setting it to 1, fr fr 🔥

---

💜 swap

specify a swap device or file through its path in a kdump system. the specified swap device or file must exist and have the proper swap format (no shortcuts, bestie 🙈).

why would you even need this? because the amount of memory available in the kdump kernel during a stand-alone dump is limited to the size of the HSA memory. so yeah, you might need a swap device. it's giving "small apartment, big stuff" 🎀

---

👑 fuse_debug

enable (1) or disable (0) fuse debugging. that's it. that's the whole option. slay ✨

---

🌟 EXAMPLES 🌟

a complete configuration file could look like this — and yes, I'm keeping it exactly as it is because code is sacred:

------------------------------ config file start ------------------------------
# Example configuration for hsavmcore

# 0 - ERROR
# 1 - WARN
# 2 - INFO
# 3 - DEBUG
# 4 - TRACE
verbose = 3

workdir = /var/crash

mount_debugfs = 1

use_hsa_mem = 1

hsa_size = -1
release_hsa = 1

bind_mount_vmcore = 1

swap = /dev/disk/by-uuid/3cf6630b-4c4d-49ac-a0ae-0f5484cb5721
#swap = /swap.img

fuse_debug = 0
------------------------------ config file end ------------------------------

look at her. fully configured. main character config file energy 👑💖

---

💫 SEE ALSO 💫

• hsavmcore(8) — go read that one too, bestie, it's the whole reason this config file exists 🫶

---

and that's the page!! this beauty lives in the s390-tools collection and the date on it is May 2021 — so yeah, she's been serving correct and useful info since then, and she'll keep serving. mwah 💋 🌸✨