[PVE-User] Hardcoded startup RAM for QEMU memory hotplug

[DERUMIER, Alexandre]

>>Hi,
>>Looking at the code, it's 1024MB * the number of sockets, so adding
>>sockets might be workaround. Thanks for the idea. Another workaround
>>might be to simply disable memory hotplug before leapp.
>>The kernel option "memhp_default_state=online" also works. However, I
>>think the ability to configure the startup RAM size in Proxmox would
>>be nice.

I had sent some patches 2 years ago with a rework of the code + virtio-
mem implementation, where 4G was used at minimum static (because
unhotplug is not working fine under 4G).

If I have time, I'll try to rework on it again.




On Thu, Jan 8, 2026 at 4:21 PM DERUMIER, Alexandre
<alexandre.derumier at groupe-cyllene.com> wrote:
> 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 at lists.proxmox.com>
> Répondre à: Proxmox VE user list <pve-user at lists.proxmox.com>
> À: pve-user at lists.proxmox.com
> Cc: Jan Pechek <jan.pechek at 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 at lists.proxmox.com
> https://antiphishing.vadesecure.com/v4?f=ODlJNFRJTjZBcWFlaWxQaCCCfKFV
> nu
> mwdchN4vpTQ37VVnHbAe0-
> uLaq4GRZbkYvBbl2pqUJSOyVY2GhvAcSRg&i=MUo0RzFIRTVvbFhYVGloQqpJQ0nHicCJ
> vq
> kbuHR5-
> 5Q&k=b1p5&r=cFdGNHFjVENnWDEzUVliSYiC92oq8d703C2vrBtDKIQQ2JpsHhTCAL84s
> a9
> nPXth0ZxP0R68yhAvbVSThpqxug&s=483fcb0eca7ea10b6dc41ce29e666d196b3b3ee
> e2
> f0c8d0e20c168f59c8b32ef&u=https%3A%2F%2Flists.proxmox.com%2Fcgi-
> bin%2Fmailman%2Flistinfo%2Fpve-user