hotplug problem - VM 101 qmp command 'object-add' failed - Parameter 'size' is missing

[H4R0]

Trying memory hot plug I get.

Parameter verification failed. (400)

memory: hotplug problem - VM 101 qmp command 'object-add' failed - Parameter 'size' is missing





@Stoiko Ivanov

 

[Stoiko Ivanov]

Works here...

I assume the VM is running?

please post:
* pveversion -v
* the guest config of the machine

 

[H4R0]

Yes the error only happens if the vm is running.

cpu hot plug works fine.

Spoiler: pveversion

root@lab:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-3-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-6
pve-kernel-helper: 7.0-6
pve-kernel-5.4: 6.4-4
pve-kernel-5.11.22-3-pve: 5.11.22-6
pve-kernel-5.11.22-1-pve: 5.11.22-2
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 14.2.21-1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.2.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-5
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-10
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.8-1
proxmox-backup-file-restore: 2.0.8-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

Spoiler: VM Config

agent: 1
autostart: 1
balloon: 512
bios: ovmf
boot: c
bootdisk: scsi0
ciuser: ****
cores: 4
cpu: host
efidisk0: local-zfs:base-100-disk-0/vm-101-disk-0,size=1M
hotplug: disk,network,usb,memory,cpu
ide2: local-zfs:vm-101-cloudinit,media=cdrom,size=4M
ipconfig0: ip=192.168.1.131/24,gw=192.168.1.1
kvm: 1
machine: q35
memory: 2048
name: kube1
net0: virtio=3A:9A:E8:B2:2D:C4,bridge=vmbr0
numa: 1
onboot: 1
ostype: l26
scsi0: local-zfs:base-100-disk-1/vm-101-disk-1,size=256G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=c2917a43-f7a5-4771-a035-0c51ddc2cb10
sockets: 1
sshkeys: ****
vcpus: 1
vga: type=none
vmgenid: c4594c24-ecc5-4dc6-b0c9-4dc14b2459f0

 

[H4R0]

Also triggered by qm set 101 --memory 4096

Seems like it is returned directly by qemu, however size is set in props

root@lab:/usr/share/perl5/PVE# qm set 101 --memory 4096
update VM 101: -memory 4096

$VAR1 = '{"arguments":{},"execute":"qmp_capabilities","id":"91725:1"}';

$VAR1 = '{"arguments":{"qom-type":"memory-backend-ram","id":"mem-dimm2","props":{"size":536870912}},"execute":"object-add","id":"91725:2"}';

$VAR1 = {
          'cmds' => [],
          'current' => {
                         'arguments' => {
                                          'qom-type' => 'memory-backend-ram',
                                          'id' => 'mem-dimm2',
                                          'props' => {
                                                       'size' => 536870912
                                                     }
                                        },
                         'callback' => sub { "DUMMY" },
                         'execute' => 'object-add',
                         'id' => '91725:2'
                       },
          'qga' => 0,
          'sname' => '/var/run/qemu-server/101.qmp',
          'vmid' => '101',
          'error' => 'Parameter \'size\' is missing'
        };

$VAR1 = 'VM 101 qmp command \'object-add\' failed - Parameter \'size\' is missing';

 

[Stoiko Ivanov]

Versions are uptodate (and the same versions that work here for me).

How long has this guest been running?
can you stop it and start it and see if this changes the situation?
(alternatively migrate the machine to another node if you have a cluster)

 

[H4R0]

How long has this guest been running?

Only a couple of hours.

It's IaC provisioned.

can you stop it and start it and see if this changes the situation?

Makes no difference, also rebooted the pve host.

(alternatively migrate the machine to another node if you have a cluster)

It's a single node testlab.



Funny enough I can reduce the memory value to hot unplug it.

But then again trying to set it back to it's original value I get the same error.

 

[H4R0]

I fixed it, I will submit it with some other patches to devel soon.

 

[Mickelebof]

Hello,

When will the patch be available?
I just did all the updates and I still have this problem.
Thank you.

Mick

# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-7
pve-kernel-helper: 7.0-7
pve-kernel-5.11.22-4-pve: 5.11.22-8
pve-kernel-5.11.22-3-pve: 5.11.22-7
ceph-fuse: 15.2.13-pve1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-6
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-11
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.9-2
proxmox-backup-file-restore: 2.0.9-2
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-3
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

 

[H4R0]

Has been merged over a month ago, dunno when it will be shipped.

 

[Mickelebof]

It's ok today, thanks !