From: Jan Pechek via pve-user <pve-user@lists.proxmox.com>
To: pve-user@lists.proxmox.com
Cc: Jan Pechek <jan.pechek@daktela.com>
Subject: [PVE-User] Hardcoded startup RAM for QEMU memory hotplug
Date: Thu, 8 Jan 2026 14:43:34 +0100 [thread overview]
Message-ID: <mailman.278.1767879864.353.pve-user@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 5734 bytes --]
From: Jan Pechek <jan.pechek@daktela.com>
To: pve-user@lists.proxmox.com
Subject: Hardcoded startup RAM for QEMU memory hotplug
Date: Thu, 8 Jan 2026 14:43:34 +0100
Message-ID: <CAHQqQDa-z-vEdrE1Fpt1F6BsqSsxcqpECfFhb=L=ssviMn+eOQ@mail.gmail.com>
Hello,
I would like to ask if it is possible to have the startup RAM size for
memory hotplug configurable.
We encountered a problem when upgrading Alma9 to Alma10 using the
leapp (https://leapp-repository.readthedocs.io/latest/) tool. It
creates a modified initramfs in which it performs the operating system
upgrade. However, because it is in the early boot stage of the system,
the automatic connection of hotpluggable memory does not work and only
1024MB of startup RAM is available. So leapp does not have enough
memory and OOM killer terminates it.
If we patch this hardcoded value
(https://github.com/proxmox/qemu-server/blob/e781d9713fb3d45a523fe14db6cd99ac60bbfbb5/src/PVE/QemuServer/Memory.pm#L66)
and increase the startup RAM to 2048MB, for example, everything will
work fine.
For current RHEL, the minimum required memory is 2GB as is stated here
- https://access.redhat.com/articles/rhel-limits#minimum-required-memory-3.
Please also see this related issue -
https://bugzilla.redhat.com/show_bug.cgi?id=2139907.
If there is better way to create feature request, please let me know, thanks.
Best regards,
Jan Pechek
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next reply other threads:[~2026-01-08 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 13:43 Jan Pechek via pve-user [this message]
2026-01-08 15:21 ` DERUMIER, Alexandre via pve-user
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=mailman.278.1767879864.353.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=jan.pechek@daktela.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.