mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-27 05:57:27 +00:00
rcourtman
3056dccfea
A VM that Pulse can only read through Proxmox's own memory value (no guest agent, no Pulse agent inside it) shows a cache-inclusive percentage that can sit near 100% on a healthy guest. Patrol already treats those sources as "may include cache" for pressure and recovery; the Workloads row and drawer gave no hint, so the red bar read as memory pressure (#2762, #2639). A current reading from status-mem, status-freemem, cluster-resources or derived-total-minus-used keeps its numbers, colour and thresholds, and is now qualified: VM rows show "May include cache" ("Cache?" in compact layouts), the bar tooltip and the drawer's "About this reading" explain it, and the drawer says what can supply the guest's own figure (a Pulse agent in the guest, or the QEMU guest agent on a Linux VM, worded as "can" because source selection does not guarantee a replacement). Every running container reads the cgroup value, so containers carry the note in the tooltip and drawer only, not a label on every row. Retained, unknown and unavailable readings keep their own labels and are never called current. Mock guests now carry memory provenance and a refreshed observation time; before, every mock VM and container read "Freshness unknown", which hid this cue from the demo and from screenshots. Windows VMs never claim Linux meminfo provenance, and scenario-stopped guests read powered-off. Refs #2762, #2639