Comment 8 for bug 1925249

@Caleb is the UI now using info under "resources" for virsh pods too?

I can reproduce this with master, where memory/cpu shows 0 available, while storage is correct.

Looking at the websocket data, I see that total/used/available are correct, while "resources" is empty, which is expected since we collect those only for LXD-based vmhosts:

{
 ...
  "cpu_over_commit_ratio": 1,
  "memory_over_commit_ratio": 1,
 ...
  "type": "virsh",
  "total": {
   "cores": 4,
   "memory": 15860,
   "memory_gb": "15.5",
   "local_storage": 489479471104,
   "local_storage_gb": "455.9"
  },
  "used": {
   "cores": 0,
   "memory": 0,
   "memory_gb": "0.0",
   "local_storage": 0,
   "local_storage_gb": "0.0"
  },
  "available": {
   "cores": 4,
   "memory": 15860,
   "memory_gb": "15.5",
   "local_storage": 489479471104,
   "local_storage_gb": "455.9"
  },
  "composed_machines_count": 0,
  "owners_count": 0,
  "hints": {
   "cores": 4,
   "cpu_speed": 2800,
   "memory": 15860,
   "memory_gb": "15.5",
   "local_storage": 201947750400,
   "local_storage_gb": "188.1"
  },
  "storage_pools": [
   {
    "id": "ee6f53a3-3b12-4f64-a4cf-3c2127dc900a",
    "name": "maas",
    "type": "dir",
    "path": "/var/lib/libvirt/maas-images",
    "total": 489479471104,
    "used": 0,
    "available": 489479471104
   }
  ],
...
  "resources": {
   "cores": {
    "allocated_tracked": 0,
    "allocated_other": 0,
    "free": 0
   },
   "memory": {
    "hugepages": {
     "allocated_tracked": 0,
     "allocated_other": 0,
     "free": 0
    },
    "general": {
     "allocated_tracked": 0,
     "allocated_other": 0,
     "free": 0
    }
   },
   "storage": {
    "allocated_tracked": 0,
    "allocated_other": 0,
    "free": 0
   },
   "vm_count": {
    "tracked": 0,
    "other": 0
   },
   "interfaces": [],
   "vms": [],
   "numa": []
  },
...
}