From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH] kernel config: don't automatically enable kexec handover (KHO)
Date: Tue, 14 Jul 2026 14:44:46 +0200 [thread overview]
Message-ID: <20260714124456.347992-1-d.csapak@proxmox.com> (raw)
CONFIG_KEXEC_HANDOVER_ENABLE_DEFAULT is enabled by default in the
upstream ubuntu kernel config, but has a (probably) unintended
side-effect: when KHO is automatically enabled, the kernel reserves
scratch memory for the kernel handoff and marks it with MIGRATE_CMA to
prevent non-movable allocations there.
This causes unusual stats in /proc/meminfo, for example:
CmaTotal: 0 kB
CmaFree: 4894720 kB
which looks nonsensical on the surface. It also reduces the available
memory for e.g. guests with PCI passthrough, as pinner memory can't live
in these areas.
Since we don't use kexec handover by default, and it can still be
enabled on the kernel commandline (kho=on), disable it by default to
increase the available pinnable memory for guests.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
debian/rules.d/config-common.opts | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/rules.d/config-common.opts b/debian/rules.d/config-common.opts
index 64505b4..204bab4 100644
--- a/debian/rules.d/config-common.opts
+++ b/debian/rules.d/config-common.opts
@@ -68,3 +68,4 @@
-d CONFIG_N_GSM
-d UBSAN_BOUNDS
-e CONFIG_RUST
+-d CONFIG_KEXEC_HANDOVER_ENABLE_DEFAULT
--
2.47.3
next reply other threads:[~2026-07-14 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 12:44 Dominik Csapak [this message]
2026-07-15 8:12 ` [PATCH] kernel config: don't automatically enable kexec handover (KHO) Dominik Csapak
2026-07-15 10:25 ` Thomas Lamprecht
2026-07-15 10:33 ` Dominik Csapak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260714124456.347992-1-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.