Browse documentation
Supported platforms
Support differs sharply by platform. Read this before concluding something is broken.
| Platform | Support | What you get |
|---|---|---|
| Hyper-V | Fully supported | Hosts and guests, collected by the endpoint agent locally or agentlessly over WMI. Failover clusters are modelled, so a host shows its cluster. |
| Proxmox VE | Hosts and guests only | Collected through the Proxmox API. Clusters are not modelled — every Proxmox node reads as standalone, even when it's part of a cluster. |
| VMware vSphere | Not supported | VMware hosts do not appear in JOATOS at all. There is no vSphere collection method. |
What this means in practice
If you run VMware, this section will be empty and nothing you configure will change that. It isn't a credential problem or a misconfiguration — collection for vSphere doesn't exist.
If you run Proxmox, your nodes will each show as standalone. Grouping them under their cluster isn't supported yet, so don't go looking for the setting.
If you run Hyper-V, you get the complete picture, including cluster membership.
Collection details worth knowing
Guests are polled on a slower cycle than hosts — around five minutes. A VM you've just started or stopped won't be reflected instantly; that's the cycle, not a fault.
Proxmox guests bring their IP address with them — if the guest agent is on. When you import a Proxmox VM or container, JOATOS gives it the addresses the guest reports, so it can be pinged and scanned straight away; an address you've typed in yourself is never replaced. Containers always report theirs. VMs need the QEMU guest agent enabled in Proxmox and running inside the guest, plus a full stop and start — see Showing guest IP addresses for the full requirements, Windows and Linux steps, and troubleshooting.
A stopped Hyper-V VM reports zero memory. That's what Hyper-V itself reports, so any "memory allocated" figure understates what the host would need if everything were running. Treat allocation figures as a floor, not a ceiling.
Notes & tips
- Hypervisor hosts use the same collection methods as servers — see Choosing a collection method. Hyper-V can go either way: agent on the host, or agentless WMI.
- A host that appears with no guests usually means collection is working but the platform hasn't reported them yet — check the host's last-polled time.