Odd CPU metrics on reboot of container

monkfish

Renowned Member
Dec 13, 2015
35
23
73
Hello, got me an odd one here. Within a last few batch of updates I get a massive negative CPU readout when rebooting any of my containers.

Once restarted it settles down but I wouldn't have expected to see this level of oddness. Systems hardened in accordance with CIS but I doubt this causes this as metrics are clearly displayed properly once ct is started, if it were something blocking readout then one might consider it to be present all the time.

Happens on all the proxmox hosts I have access to, differing CPU, memory and storage. Same package list. pve-no-subscription repos in use here. Grateful for any thoughts on whats occuring here. Can live with it, no adverse affect on practical operation just unexpected.

Thank you for Proxmox!

Screenshot:

1782938529790.png
Package list:

Code:
proxmox-ve: 9.2.0 (running kernel: 7.0.12-1-pve)
pve-manager: 9.2.4 (running version: 9.2.4/5e5ae681198514d4)
proxmox-kernel-helper: 9.2.0
proxmox-kernel-7.0: 7.0.12-1
proxmox-kernel-7.0.12-1-pve-signed: 7.0.12-1
ceph-fuse: 19.2.3-pve1
corosync: 3.1.10-pve2
criu: 4.1.1-1
frr-pythontools: 10.6.1-1+pve2
ifupdown2: 3.3.0-1+pmx12
intel-microcode: 3.20251111.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.1
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.1.1
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.1.6
libpve-cluster-perl: 9.1.6
libpve-common-perl: 9.1.16
libpve-guest-common-perl: 6.0.4
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.6.6
libpve-notify-perl: 9.1.6
libpve-rs-perl: 0.15.3
libpve-storage-perl: 9.1.6
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 7.0.0-2
lxcfs: 7.0.0-pve1
novnc-pve: 1.7.0-2
proxmox-backup-client: 4.2.2-1
proxmox-backup-file-restore: 4.2.2-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.3
proxmox-kernel-helper: 9.2.0
proxmox-mail-forward: 1.0.3
proxmox-mini-journalreader: 1.7
proxmox-offline-mirror-helper: 0.7.4
proxmox-widget-toolkit: 5.2.6
pve-cluster: 9.1.6
pve-container: 6.1.10
pve-docs: 9.2.2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.18-4
pve-ha-manager: 5.2.4
pve-i18n: 3.9.0
pve-qemu-kvm: 11.0.0-4
pve-xtermjs: 6.0.0-2
qemu-server: 9.1.18
smartmontools: 7.5-pve2
spiceterm: 3.4.2
swtpm: 0.8.0+pve3
vncterm: 1.9.2
zfsutils-linux: 2.4.2-pve1
 
When rebooting containers, I also regularly see a negative number for a short time. It has been like this for a long time and on freshly installed PVE also. I always assumed that it was an overflow (or some other error like an uninitialized variable) caused by the container not running for the whole timeslice (or sliding window) that is used to calculate the CPU usage. I assume that it is harmless (and it does not seem to mess up the graphs).
 
Last edited: