Each report a Windows agent asks WMI's root\virtualization\v2 for every VM's state and health, BIOS GUID, generation, vCPUs, memory and automatic start action: COM through x/sys/windows, no cgo, no new dependency. They're the host's VMs on its page and in workloads, judged as libvirt's are, and an agent inside one links to it by the BIOS GUID. Hyper-V shows VMs only to Administrators and Hyper-V Administrators, a group that can also change them, so the agent isn't added on its own: without it, the host page and a warning say so and docs/windows.md says how to add it or set hyperv: false. Tested on Windows Server 2025 with Hyper-V nested under KVM, both ways.