Bug 49916 - Show RAM over-commitment in UVMM UMC module
Show RAM over-commitment in UVMM UMC module
Product: UCS
Classification: Unclassified
Component: UMC - Virtual machines (UVMM)
UCS 4.4
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
Depends on:
  Show dependency treegraph
Reported: 2019-07-24 16:51 CEST by Stefan Gohmann
Modified: 2019-08-14 14:46 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number: 2019072221000434
Bug group (optional):
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2019-07-24 16:51:50 CEST
Similar to Bug #49915.

A RAM over-commitment could be shown in UVMM UMC module. It is especially useful when instances have been moved via virsh.
Comment 1 Philipp Hahn univentionstaff 2019-07-25 08:23:49 CEST
CPU utilization is already shown in UVMM UMC in the "host tree" or when doing a search for "Physical servers" - through only for *running* VMs as in most cases a host can contain lots of inactive VMs, which is fine as they do not consume RAM.

Having another display for the sum of RAM of all defined VMs on a host could be done in some "per host detail page", as otherwise the GUI gets to crowded. Is that (or something other) is requested, please REOPEN and clarify.
Comment 2 Stefan Gohmann univentionstaff 2019-07-25 08:35:50 CEST
What I meant. As an administrator, it would be very helpful if I open the UVMM module and there is a RAM over-overcommitment on one of the KVM servers, that a warning is shown which includes on which server an RAM over-overcommitment is.

Would that make sense from your point of view?