[pve-devel] [PATCH v2 pve-manager 2/2] ui: qemu : memoryedit: add new max && virtio fields

DERUMIER, Alexandre alexandre.derumier at groupe-cyllene.com
Tue Sep 5 17:10:32 CEST 2023


> 
> The advantage with 'max' is that it can be used for both, hotplug
> with
> dimms and virtio-mem. Otherwise, we'd need two different sub-options
> depending on hotplug method.
> 
yes, that's what I thinked too, it could be great to have same api call
with same options, with or without virtio-mem.

(virtio-mem will be the default for new linux distro, but for windows
or older linux distro, we still need to use old dimm method)



My first idea for the gui, for the max value, was a combobox displaying
an hint with mem topology, something like:

max = 64GB : 64 x 1GB dimm
max = 128GB: 64 x 2GB dimm
...

(or maybe it could be a hint outside a simple integer field)






More information about the pve-devel mailing list