Web UI bug?

[Loic92]

Proxmox VE 9.1.1
Linux 6.17.2-1-pve

Hello,
I noticed a strange behavior of the Web UI.
- I created a Windows 11 VM with a Machine Type of pc-q35-9.1
- Then I wanted to go back to q35 (without any specific version, so normally the latest available), so I did the commande "qm set 105 --machine q35"
- Then when I came back to the UI I saw that "pc-q35-5.1" was displayed!
- But when I'm doing the command "qm config 105", I confirm that I have "machine: q35" into the config!
- ChatGPT is saying that the good information is coming from the result of "qm config 105" and there is an issue with the WebUI
- Then, in the WebUI, when I'm opening the combo box to select the version of q35, the "Latest" entry is not available anymore!



What do you think?

Thanks.

 

[fabian]

please provide
- cat /etc/pve/qemu/XXX.conf
- pveversion -v

thanks!

 

[Loic92]

please provide
- cat /etc/pve/qemu/XXX.conf
- pveversion -v

thanks!

root@nab92:~# qm config 105
agent: 1
balloon: 12288
bios: ovmf
boot: order=scsi0;net0
cores: 4
cpu: x86-64-v2-AES
efidisk0: ceph-pool:vm-105-disk-0,efitype=4m,ms-cert=2023,pre-enrolled-keys=1,size=1M
hotplug: 0
machine: q35
memory: 12288
meta: creation-qemu=10.1.2,ctime=1763585020
name: sirius
net0: virtio=BC:24:11:13:71:09,bridge=vmbr0,firewall=1,tag=4
numa: 0
onboot: 1
ostype: win11
scsi0: ceph-pool:vm-105-disk-1,discard=on,iothread=1,size=64G
scsihw: virtio-scsi-single
smbios1: uuid=874a5ff0-99eb-47bd-a73b-add28e517249
sockets: 1
tpmstate0: ceph-pool:vm-105-disk-2,size=4M,version=v2.0
vga: virtio
vmgenid: bb0017de-3e73-4215-8887-a8405ef35632

root@nab92:~# pveversion -v
proxmox-ve: 9.1.0 (running kernel: 6.17.2-1-pve)
pve-manager: 9.1.1 (running version: 9.1.1/42db4a6cf33dac83)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
proxmox-kernel-6.17: 6.17.2-1
ceph: 19.2.3-pve2
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx11
intel-microcode: 3.20250812.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.4
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.0.7
libpve-cluster-perl: 9.0.7
libpve-common-perl: 9.0.15
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.2.3
libpve-rs-perl: 0.11.3
libpve-storage-perl: 9.0.18
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-3
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.20-1
proxmox-backup-file-restore: 4.0.20-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.1
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.2
pve-cluster: 9.0.7
pve-container: 6.0.18
pve-docs: 9.1.1
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.17-2
pve-ha-manager: 5.0.8
pve-i18n: 3.6.2
pve-qemu-kvm: 10.1.2-3
pve-xtermjs: 5.5.0-3
qemu-server: 9.0.30
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve3
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1

 

[fabian]

yeah, this is just the UI being misleading. the backend actually handles this correctly, and pins the machine to that recorded at the time of creation in this case (you can check with "qm showcmd XXX --pretty" or by inspecting the running VM's cmdline).

 

[Loic92]

yeah, this is just the UI being misleading. the backend actually handles this correctly, and pins the machine to that recorded at the time of creation in this case (you can check with "qm showcmd XXX --pretty" or by inspecting the running VM's cmdline).

thanks.
In fact I was talking about 1 VM, but I have 2 VMs in this case, and by doing your command, I can see a little difference, q35-10.1 for one, and q3510.0 for the other one.

root@nab92:~# qm showcmd 105 --pretty | grep q35
  -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg \
  -machine 'pflash0=pflash0,pflash1=drive-efidisk0,hpet=off,type=pc-q35-10.1+pve0'

root@nab92:~# qm showcmd 102 --pretty | grep q35
  -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg \
  -machine 'pflash0=pflash0,pflash1=drive-efidisk0,hpet=off,type=pc-q35-10.0+pve0'

 

[fabian]

yes, like I said: for Windows VMs, if you don't specify an explicit machine version, the creation metadata will be used to decide on one. the fallback to 5.1 is only valid if no creation metadata exists, e.g., because the VM is very old.

so VM 105 was likely created after the node was updated to have QEMU 10.1, while VM 102 was created when the installed QEMU version was still 10.0