## Why
The TUI only shows configured resources. To see which guest needs more CPU, RAM or disk before it becomes a problem, you need what is actually in use.
## Proposal
- Main table: CPU % and memory used (MiB or %), from the data `get guests` already returns (`cpu`, `mem`, `maxmem`, `disk`).
- Info screen, Resources section: "in use" next to each configured value, from `status/current`.
- Optional: a short trend over the last hour from `rrddata`.
## cv4pve-cli (2.4.0)
- `get guests -o json`. It already has `cpu`, `mem`, `disk`, `maxmem` and `maxdisk`.
- `api get /nodes/<node>/<qemu|lxc>/<vmid>/status/current -o json`
- `get guest rrddata <node> <vmtype> <vmid> hour`
## Notes
- For VMs, `disk` is usually 0 unless the guest agent reports it, so show "-" rather than a misleading 0.
- `/cluster/resources` lags a few seconds behind.
## Done when
- Usage is shown in the table and on the info screen.
- Tests are written first.
- A read-only live check passes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why
The TUI only shows configured resources. To see which guest needs more CPU, RAM or disk before it becomes a problem, you need what is actually in use.
Proposal
get guestsalready returns (cpu,mem,maxmem,disk).status/current.rrddata.cv4pve-cli (2.4.0)
get guests -o json. It already hascpu,mem,disk,maxmemandmaxdisk.api get /nodes/<node>/<qemu|lxc>/<vmid>/status/current -o jsonget guest rrddata <node> <vmtype> <vmid> hourNotes
diskis usually 0 unless the guest agent reports it, so show "-" rather than a misleading 0./cluster/resourceslags a few seconds behind.Done when
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com