When trying to add a Hyper-V Virtual Machine sensor I am unable to. Under the Virtual Machine Settings I see "No Virtual Machine available". I have 4 VMs running on this host. Other Perf Counters/WMI sensors seem to be fine on this server.
I have run the following from the WMI Tester: Namespave: root\virtualization SELECT Name,ElementName,Description FROM Msvm_ComputerSystem WHERE ProcessID<>NULL
I get Error: 80041010: The specified class is not valid.
I have looked in the KB threads but found nothing satisfactory. I am currently running 16.3.26.6385 on this cluster.
Article Comments
Hi Erhard,
Here are the results:
---------------------------------------------------------------------------------------------------- Set namespace to: root\virtualization\v2
SELECT Name FROM Win32_PerfRawData_IdePerfProvider_HyperVVirtualIDEControllerEmulated
Result: Specified class is not available
SELECT ElementName,EnabledState FROM Msvm_ComputerSystem WHERE name LIKE 'VMGUID'
Result: Blank response, no data returned but no error
----------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------- Changing the namespace to root\cimV2
SELECT Name FROM Win32_PerfRawData_IdePerfProvider_HyperVVirtualIDEControllerEmulated
Result: I get a list of VMs on each host
SELECT ElementName,EnabledState FROM Msvm_ComputerSystem WHERE name LIKE 'VMGUID'
Result: Specified class is not available
----------------------------------------------------------------------------------------------------
Still, trying to add the VM sensor to the two servers that returned a list of VMs I still get "No Virtual Machine Available".
Feb, 2017 - Permalink
Hello there,
The used namespace in the tester might be indeed wrong, in Server 2012 and newer it is root\virtualization\v2.
The so-called "Meta Scan" that initially tries to list the VMs uses this query:
SELECT Name FROM Win32_PerfRawData_IdePerfProvider_HyperVVirtualIDEControllerEmulated
Though for this query you might need to set root\cimV2 as namespace. What do you get with this query in the tester?
Also try this query:
SELECT ElementName,EnabledState FROM Msvm_ComputerSystem WHERE name LIKE 'VMGUID'
This the query a running sensor would then perform. Here's how to retrieve the VMs GUID.
Kind regards,
Erhard
Feb, 2017 - Permalink