Important
Coming from a version before 5.0.0? Read the 5.0.0 release notes first. That release carried the migrations and the changes to entities and options that this one builds on; the notes below assume you are on 5.0.0 or later.
Nothing needs to be reconfigured. The new sensors are diagnostic and disabled by default — enable the ones you want on the guest's device page.
What a guest waits for
Six sensors per VM and container from the Linux kernel's pressure stall information: CPU pressure, IO pressure, Memory pressure and their … stalled counterparts. Each is the share of the last ten seconds in which at least one task waited for that resource — or, for stalled, in which every task did. "RAM used" says little on Linux, because the kernel keeps what it can; this is what tells a comfortable guest from a thrashing one. Proxmox reports the values on a read the integration already makes, so they cost no extra request. (#685)
The reading differs by guest type, and it is worth knowing which you are looking at:
- For a container these are its own cgroup — what the workload experiences.
- For a VM they are measured on the host for that VM's process, so they say the host is stalling for this VM rather than what the guest sees. That is also why they work for a Windows guest.
Proxmox VE 8 does not report them; there they stay unknown.
Memory used on host per VM comes along with it: what the guest costs the host, which is more than what it reports using — device models, migration buffers and the like.
Fixed
- A refused ZFS read produced a traceback every minute. A 403 hands back nothing by design — the repair is filed instead — and the ZFS coordinator iterated that anyway. Its second guard, for a pool the listing no longer has, could never fire. (#686, reported by @Pivens)
- The repairs named ACL paths Proxmox does not have: a disk's asked for the privilege on
/nodes/<disk WWN>, a storage's on/storage/storage/<node>/<name>, and a ZFS pool's came out asUnmapped. The node now comes from the read's own path, and a storage's path is its bare name. A cluster-wide refusal raisedNameErrorinstead of the repair it exists for. (#687, same reporter)
Documentation
docs/entities.md describes both sensor groups, including which guest type means what. New strings are English for now; the other languages follow through Crowdin.
Full changelog: 5.2.2...5.3.0