TASK ERROR: 400 Parameter verification failed. memory: hotplug problem - 400 Parameter verification failed. dimm38: error unplug memory module

[Sahil]

Hi Team,

I want to use the Hotplug option, but I am getting this message while it triggers for increasing the CPU or Memory, Need some solutions to understand the issue.

We are using the Proxmox API to trigger the value. But In the end, I had to shut down the VM and restart it to enforce the new memory limit.

Error:
Task viewer: VM 727 - Configure

OutputStatus
Stop
update VM 727: -memory 24576 -sockets 2 -vcpus 4
try to unplug memory dimm dimm49
try to unplug memory dimm dimm48
try to unplug memory dimm dimm47
try to unplug memory dimm dimm46
try to unplug memory dimm dimm45
try to unplug memory dimm dimm44
try to unplug memory dimm dimm43
try to unplug memory dimm dimm42
try to unplug memory dimm dimm41
try to unplug memory dimm dimm40
try to unplug memory dimm dimm39
try to unplug memory dimm dimm38
TASK ERROR: 400 Parameter verification failed. memory: hotplug problem - 400 Parameter verification failed. dimm38: error unplug memory module
======================================================================================================================
Error:
update VM 727: -memory 16384 -sockets 2 -vcpus 4
try to unplug memory dimm dimm34
TASK ERROR: 400 Parameter verification failed. memory: hotplug problem - 400 Parameter verification failed. dimm34: error unplug memory module

=======================================================================================================================

root@proxmox23:~# pveversion -v
proxmox-ve: 6.4-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.4-14 (running version: 6.4-14/15e2bf61)
pve-kernel-5.4: 6.4-16
pve-kernel-helper: 6.4-16
pve-kernel-5.4.178-1-pve: 5.4.178-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.5-pve2~bpo10+1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve4~bpo10
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.22-pve2~bpo10+1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.13-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-2
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.7-pve1

 

[fabian]

1. PVE 6.x is EOL, please upgrade to 7.x
2. hot unplugging of memory requires guest support, which seems to not be there in your case..

 

[Sahil]

Thanks for your response,

I have completed point 1. Now its proxmox-ve: 7.2-1

Regarding point 2, Can you please elaborate in detail to understand, that "hot unplugging of memory requires guest support"

How to achieve the new memory limit using hotplug without rebooting/restarting the machine.?

Thanks

 

[Neobin]

Maybe this helps:
https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory)

 

[Azurodb]

Thanks for your response,

I have completed point 1. Now its proxmox-ve: 7.2-1

Regarding point 2, Can you please elaborate in detail to understand that "hot unplugging of memory requires guest support"

How to achieve the new memory limit using hotplug without rebooting/restarting the machine.?

Thanks

Sahil, can you share detailed information on the hardware you're using now?

 

[Mani]

Try this two following commands, those two modules could be prebuilt in kernel.

grep "CONFIG_HOTPLUG_PCI_ACPI=" /boot/config-`uname -r` CONFIG_HOTPLUG_PCI_ACPI=y grep "CONFIG_MEMORY_HOTPLUG=" /boot/config-`uname -r` CONFIG_MEMORY_HOTPLUG=y