Well, easy-going to tell that. But if you already happen to follow quite a lot of the important projects there is not much spare time left. And honestly I would not start at this topic, but rather with
- why does a proxmox cluster node change its ssh keys on occasion (happened 3 times during the last weeks)
(no more migration possible then, first remove old key, re-login and answer "yes" to save new key)
- why does corosync not allow to change mtu in config during runtime, but pmtud is allowed to change it on the fly?
- why does a whole ha-group go in failure-state (vms running) sometimes?
(can only be cleared by deleting the group and re-adding vms to new group)
- the vms listed in the search tab show a relative percentage of RAM usage, but no absolute value (e.g. in GB).
(prevents recognising the top RAM users, additionally high percentage says absolutely nothing in a linux guest)
- why is the vm list to the left always id-sorted? Nobody outside the proxmox software cares about the id, its the _name_ you give a vm that you want to find.. (true for all lists btw)
- a combined load tab of all vms (load for every single vm) would be great. There one could see if some (or all) peak some time during the day/night and who's to blame, same for RAM usage.
- add your favourite problem here