Hi,
can somebody explain to me why memory hotplug for CentOS/Red Hat VMs works out of the box although their kernel doesn't set CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE?
Debian kernels also don't set CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE, and for Debian VMs I therefore have to use kernel parameter "memhp_default_state=online".
See https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory)
I finally want to understand this memory hotplug behaviour in Proxmox (coming from oVirt, where this was never a topic at all...). Is this because of the famous Red Hat frankenkernel?
thx
Matthias
can somebody explain to me why memory hotplug for CentOS/Red Hat VMs works out of the box although their kernel doesn't set CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE?
Debian kernels also don't set CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE, and for Debian VMs I therefore have to use kernel parameter "memhp_default_state=online".
See https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory)
I finally want to understand this memory hotplug behaviour in Proxmox (coming from oVirt, where this was never a topic at all...). Is this because of the famous Red Hat frankenkernel?
thx
Matthias