[SOLVED] UI Bug at CPU cores with 6.2-10

Leah

Well-Known Member
Aug 1, 2019
56
6
48
After upgrading to 6.2-10 the hardware page of some VMs only report 1 core for the affected VM despite they are running and have 20 cores. The unapplied change is not related to this issue and the VM had 20 cores befor too. There are affected and unaffected VMs on the same host. Is this a known behavior?Screenshot2020-08-04_14-04-21.png
 
what does the VM config file contain (/etc/pve/local/qemu/VMID.conf) ?
 
The config file contains the right data

Code:
root@node5:~# cat /etc/pve/local/qemu-server/175.conf
agent: 1
bootdisk: scsi0
cores: 20
memory: 26624
name: srv.example.com
net0: virtio=D2:1B:17:ff:ff:ff,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: HDD:vm-175-disk-0,size=600G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=65fdf0bf-13ff-4aae-aaaa-920280c3fb2b
sockets: 1
startup: down=300
vmgenid: 97dd6437-54fb-4a9e-aaaa-b33a9f7af8c8

[PENDING]
cores: 10
cpu: host,flags=+md-clear
numa: 1
sockets: 2
 
Last edited:
can reproduce, there is definitely a bug there. it's just cosmetic though, I'll post back here once I found the case.
 
  • Like
Reactions: Leah
fixed in libpve-guest-common-perl 3.1-2 (not yet available in the repositories)
 
  • Like
Reactions: Leah
now available up to pve-no-subscription!