Applications Systems

Hyper-V virtual machines not visible when Hyper-V host is monitored through SolarWinds Agent

When a Hyper-V host is monitored through the SolarWinds Agent in SolarWinds Observability Self-Hosted / VMAN 2025.2, the Hyper-V host appears in the web console but the list of virtual machines (VMs) for that host is empty. The VM information is missing from the Hyper-V view even though the host itself is up and responding.

First published date

8/5/2026 4:19 PM

Last published date

8/5/2026 4:19 PM

Overview

When a Hyper-V host is monitored through the SolarWinds Agent in SolarWinds Observability Self-Hosted / VMAN 2025.2, the Hyper-V host appears in the web console but the list of virtual machines (VMs) for that host is empty. The VM information is missing from the Hyper-V view even though the host itself is up and responding.

Product section

Virtualization Manager

Cause

In this configuration, the Hyper-V host is polled through the SolarWinds Agent using agent-based polling. VMAN virtualization polling is not supported when the Hyper-V host is monitored through the agent, so virtualization data for that host (including the child VMs) is not collected or displayed.

To collect Hyper-V virtualization data and show the VMs, the Hyper-V host must use a VMAN-supported virtualization polling method instead of “Agent” for virtualization polling.

Resolution

Follow these steps to change the virtualization polling method for the affected Hyper-V host so that VM information is collected and displayed:

  1. Open the Hyper-V host in the SolarWinds web console.

    • In SolarWinds Observability Self-Hosted, navigate to the node details page for the Hyper-V host that is currently monitored via the SolarWinds Agent.

  2. Go to the Virtualization Polling Settings for the host.

    • From the host details, open the Virtualization Polling Settings view for that Hyper-V host.

  3. Change the virtualization polling type from Agent to Basic.

    • In the virtualization polling configuration for this Hyper-V host, locate the polling type (or poller) setting.
    • Change the polling type from Agent to Basic for the Hyper-V host.
    • This change ensures the host is polled using a VMAN-supported virtualization polling method instead of Agent polling for virtualization data.

  4. Save the changes.

    • Save or apply the updated virtualization polling settings for the Hyper-V host.

  5. Allow at least one full polling cycle.

    • Wait for the next virtualization polling cycle to complete.
    • After the polling completes, return to the Hyper-V view in the console and verify that the VM information (VM list and details) is now populated for the Hyper-V host.