Problem Description:
When adding a new Hyper-V host to Druva, no Virtual Machines (VMs) are listed in the Druva console for this host, despite VMs being present on the Hyper-V server. The Druva Agent status on the host appears as "connected."
Findings:
A new Hyper-V host was added to Druva.
This host contained 3 VMs, but the Druva console displayed 0 VMs.
The Druva Agent status on the host was "connected."
Log analysis revealed the following error on the Hyper-V host:
Traceback
level-error ts-2025-05-29T02:20:23.3425467Z filename-errorhandler.go: 124
correlationid-1e3a186e8369de532538b5ebf8c78e63:2538b5ebf8c78e63:7834cb618ce34d#5 retry-false code-hyperv_plugin_main_service-1600 message-"Internal error: exit status 1" traceback-"\ndruva.com/godevkit/endpoint/middleware.ErnorProcessorEnsureCodePrefix\n
\tdruva.com/godevkit@v0.11.23/endpoint/middleware/errorhandler.go:138\ndruva.com/godevkit/endpoint/middleware.ErrorHandlingMiddleware.func1
Cause:
The log snippet indicating an "Internal error: exit status 1" from the hyperv_plugin_main_service-1600 suggests that a core component of the Druva Hyper-V agent, responsible for discovering and reporting VMs, encountered an unexpected termination or error during its operation. This internal error prevented the agent from properly enumerating and sending the VM inventory to the Druva console.
Resolution:
To resolve Hyper-V VMs not being listed in the Druva console after adding a new host:
Access the Hyper-V Host: Log in to the affected Hyper-V host where VMs are not being listed.
Restart Druva Agent Service:
Open the Services management console (services.msc).
Locate the "Druva Enterprise Workloads Agent service" service
Right-click on the service and select "Restart."
Perform Refresh in Druva Console:
Navigate to the Druva console.
Go to the Hyper-V workload section.
Initiate a "Refresh Hosts" operation.
Subsequently, initiate a "Refresh All VMs" operation.
Verify VM Listing: Allow time for the synchronization process to complete. After successful synchronization, verify that the Virtual Machines are now correctly listed under the respective Hyper-V host in the Druva console.