[SOLVED] Not able to change RAM in Cloud-Init created VM in Proxmo GUI 9.1.5

devaux

Active Member
Feb 3, 2024
210
56
33
Hey there,
I created 3 debian 13 based servers with my cloudinit-image. Everything works fine, but when i want to change the RAM amount in the Proxmox GUI, i get the error "Parameter verification failed. (400) delete: unknown option 'allow-ksm". Proxmox 9.1.5
Manually change of the amount in the .conf file works.

Code:
agent: 1
bios: ovmf
boot: order=scsi0
cipassword: $5...
ciuser: user
cores: 4
cpu: x86-64-v2-AES
efidisk0: vms0_ceph:vm-913-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide2: vms0_ceph:vm-913-cloudinit,media=cdrom,size=4M
ipconfig0: ip=10.99.98.153/22,gw=10.99.99.1
machine: q35
memory: 8192
meta: creation-qemu=10.1.2,ctime=1764602484
name: k3s-03
nameserver: 1.1.1.1
net0: virtio=BC:24:11..,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: vms0_ceph:vm-913-disk-1,cache=writeback,discard=on,iothread=1,size=32G,ssd=1
scsihw: virtio-scsi-single
searchdomain: localdomain
serial0: socket
smbios1: uuid=ea28...
sockets: 1
sshkeys: ssh-rsa%20A...
vmgenid: d2381...
 
Last edited:
is this a cluster?

this sounds like that one of the nodes is on a newer version that includes the gui changes but you have a vm on a node selected where that api parameter is not there yet.

can you check (and post) the output of 'pveversion -v' on all nodes ?

if it's not a cluster, are you in a healthy update state? (also check 'pveversion -v')
 
is this a cluster?

this sounds like that one of the nodes is on a newer version that includes the gui changes but you have a vm on a node selected where that api parameter is not there yet.

can you check (and post) the output of 'pveversion -v' on all nodes ?

if it's not a cluster, are you in a healthy update state? (also check 'pveversion -v')

This! I had minor version differences between the nodes. After updating all nodes, it worked.
Thanks!