Troubleshooting vGPU Metrics with ControlUp

A discussion took place about vGPU metrics and how they differ depending on whether Windows or Nvidia API is used for data collection. One member asked for tips on making data collection via Nvidia API work and another member suggested checking for the installation of NVIDIA WMI and restarting the ControlUp agent after switching. ControlUp documentation on vGPU can be found at https://support.controlup.com/v1/docs/gpu-monitoring-with-controlup#collecting-data-from-nvidia-api-optional.

Read the entire ‘Troubleshooting vGPU Metrics with ControlUp’ thread below:

Hi guys, I’m currently playing around with the vGPU metrics.

I wanted to see how they differ when Windows or Nvidia API is used for data collection (see https://support.controlup.com/v1/docs/gpu-monitoring-with-controlup#collecting-data-from-nvidia-api-optional).

This is when I noticed, that the cu console doesn’t show any gpu metrics when I switch to collect the metrics via Nvidia API…

Have some of you managed to make the data collection via Nvidia API work?

Have you installed NVIDIA WMI?

Also make sure these Powershell snippets return data.

Get-WmiObject -Namespace "root\cimv2\nv" -Class "gpu"

Get-WmiObject -Namespace "root\cimv2\nv" -Class "system"

Thanks for the tips Dennis! Both powershell commands return data and Nvidia WMI is installed as far as I know. The vGPU documentation states, that it’s included in the driver package, so it should be good.

try to restart the cu agent after the switch

Continue reading and comment on the thread ‘Troubleshooting vGPU Metrics with ControlUp’.  Not a member? Join Here!