memory hotplug does not boot

[H4R0]

I followed https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory)

setting udev rule for cpu and memhp_default_state=online kernel option for memory hotplug.

As soon as i enable memory hotplug in vm options, the vm does not boot anymore. Its stuck at the proxmox logo.

Once its disabled it boots again, proxmox is up to date.

Tested in a testlab and on productive hardware.

I tried using legacy/uefi boot and q35/i440fx chipset to no avail.

What am i missing ?

agent: 1
balloon: 2048
bios: ovmf
bootdisk: scsi0
cores: 12
cpu: host
efidisk0: local-zfs:vm-101-disk-1,size=1M
hotplug: disk,network,usb,memory,cpu
ide2: local:iso/debian-10.5.0-amd64-netinst.iso,media=cdrom
machine: q35
memory: 4096
name: hotplug
net0: virtio=7A:49:39:19:B7:D1,bridge=vmbr0,firewall=1
numa: 1
ostype: l26
scsi0: local-zfs:vm-101-disk-0,discard=on,size=32G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=359f8db4-de29-4170-84e2-fc21cc5693f6
sockets: 1
vcpus: 4
vmgenid: 9d4a614a-5684-44f2-baad-37a16c82df62

 

[Allister]

I am having the same exact problem. Still trying to find a solution. :-(

 

[Brian Read]

and so am I, linux VM one Centos7 other Debian 11.

 

[fiona]

Hi,
please share the output of qm config <ID> and pveversion -v. Do you see anything in the host's system logs/journal? Any visible error message in the guest?

 

[Brian Read]

root@pve:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-2-pve)
pve-manager: 8.2.7 (running version: 8.2.7/3e0176e6bb2ade3b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-2
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.8
libpve-cluster-perl: 8.0.8
libpve-common-perl: 8.2.5
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.10
libpve-storage-perl: 8.2.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-4
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.2.4
pve-cluster: 8.0.8
pve-container: 5.2.0
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.13-2
pve-ha-manager: 4.0.5
pve-i18n: 3.2.4
pve-qemu-kvm: 9.0.2-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

 

[Brian Read]

ok, monitoring logs showed that the numa parameter is quite tricky to get to stick! And also Memory has to be in 512 chunks for the Memory hot plug to work.