Lookahead: top-like monitor for qubes

[ben-grande]

@otter2

That is what I mean by “displaying unknown MEM(%) for stubdomains correctly and separately”. Otherwise, if you aggregate memory (not maxmem) from stubdomain and domain, you are forced to lie about MEM(%), are you not?

I tested with a HVM StandaloneVM from fedora-44-xfce which has memory balancing enabled. Values that are wrong:

• MEM_SET(MiB) > MEM_MAX(MiB) and therefore, MEM_SET/MAX(%) > 100%`, because value is aggregated with stubdom
• MEM_USED has a fixed amount of memory of the stubdomain plus volatile memory managed by qmemman, as the value is aggregated, we can’t distinct between what the qube is using and what the stubdomain is using. The standard fixed amount is 144MiB but can be customized with stubdom_mem.

Note that values for MEM_SET is only shown when specified or format is max, not in the default view. Those values don’t show NA, but they show misleading (but not too misleading) values. I will leave a TODO for this, to broadcast values used by stubdomains.

---

Not specific to HVMs, but any qube that reports a high meminfo due to swap, caj have MEM_USED(MiB) bigger than MEM_SET(MiB) and MEM_MAX(MiB) and their usages (%). Theoretically, I could fix this by reporting memory consumption and swap usage separately in the qube’s qmemman agent.