From: "DERUMIER, Alexandre via pve-user" <pve-user@lists.proxmox.com>
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Cc: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
Subject: Re: [PVE-User] Hardcoded startup RAM for QEMU memory hotplug
Date: Thu, 8 Jan 2026 15:21:01 +0000 [thread overview]
Message-ID: <mailman.281.1767886627.353.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <mailman.278.1767879864.353.pve-user@lists.proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 13656 bytes --]
From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Hardcoded startup RAM for QEMU memory hotplug
Date: Thu, 8 Jan 2026 15:21:01 +0000
Message-ID: <1b5536bef426ee07ef087fc76ec1a7ca196a5afa.camel@groupe-cyllene.com>
hi currently no, but it's related to the number of cpu sockets of the
vm. (it's 512mb by socket if I remember correctly).
so, you can try a vm with 4 sockets.
you can also add "memhp_default_state=online" to kernel boot option, it
should auto enable the hotplug memory dimm when kernel boot
-------- Message initial --------
De: Jan Pechek via pve-user <pve-user@lists.proxmox.com>
Répondre à: Proxmox VE user list <pve-user@lists.proxmox.com>
À: pve-user@lists.proxmox.com
Cc: Jan Pechek <jan.pechek@daktela.com>
Objet: [PVE-User] Hardcoded startup RAM for QEMU memory hotplug
Date: 08/01/2026 14:43:34
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://antiphishing.vadesecure.com/v4?f=ODlJNFRJTjZBcWFlaWxQaCCCfKFVnu
mwdchN4vpTQ37VVnHbAe0-
uLaq4GRZbkYvBbl2pqUJSOyVY2GhvAcSRg&i=MUo0RzFIRTVvbFhYVGloQqpJQ0nHicCJvq
kbuHR5-
5Q&k=b1p5&r=cFdGNHFjVENnWDEzUVliSYiC92oq8d703C2vrBtDKIQQ2JpsHhTCAL84sa9
nPXth0ZxP0R68yhAvbVSThpqxug&s=483fcb0eca7ea10b6dc41ce29e666d196b3b3eee2
f0c8d0e20c168f59c8b32ef&u=https%3A%2F%2Flists.proxmox.com%2Fcgi-
bin%2Fmailman%2Flistinfo%2Fpve-user
[-- 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 prev parent reply other threads:[~2026-01-08 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 13:43 Jan Pechek via pve-user
2026-01-08 15:21 ` DERUMIER, Alexandre via pve-user [this message]
[not found] ` <1b5536bef426ee07ef087fc76ec1a7ca196a5afa.camel@groupe-cyllene.com>
2026-01-13 9:33 ` Jan Pechek via pve-user
[not found] ` <CAHQqQDZkUi60z3CsHc5-WVtPEoBETZCHRtqhF197nbR50dQ5xQ@mail.gmail.com>
2026-01-13 10:46 ` 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.281.1767886627.353.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=alexandre.derumier@groupe-cyllene.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox