There's a few problems in all the listings—I'll file separate bugs for the following issues:
1. cores count can go to subzero if you compose more cores on your VMs than available on the pod (since it's customary to do that, we should probably instead display core utilisation, maybe even in percentages when lower than 1, and possibly like Nx [eg. "2.2x utilisation"] when greater than 1)
2. local storage will be added up even though it might be using the same backing devices — however, this one can be really hard to solve properly, even if libvirtd gives us enough information (path and local storage), because some of it might still be only known to the system (eg. /var/lib/libvirt/pool1 might be a different mount point than /var/lib/libvirt/pool2). I think this one is not really worth fixing, but I'll file it anyway for reference.
There's a few problems in all the listings—I'll file separate bugs for the following issues:
1. cores count can go to subzero if you compose more cores on your VMs than available on the pod (since it's customary to do that, we should probably instead display core utilisation, maybe even in percentages when lower than 1, and possibly like Nx [eg. "2.2x utilisation"] when greater than 1)
2. local storage will be added up even though it might be using the same backing devices — however, this one can be really hard to solve properly, even if libvirtd gives us enough information (path and local storage), because some of it might still be only known to the system (eg. /var/lib/ libvirt/ pool1 might be a different mount point than /var/lib/ libvirt/ pool2). I think this one is not really worth fixing, but I'll file it anyway for reference.