OpenCL not available when using NVIDIA GRID vGPU grid_m60-8q profile on VSphere 6.7

I am using a Tesla M60 card as pass-through by using the m60-8q profile, and I understand that this should allow me to use OpenCL on a Windows 10 VM running on the VSphere 6.7 host, but when I run GPU-Z it shows no OpenCL or CUDA support.

Driver version is as below and the Windows 10 client VM is running the 441.66 that came with the GRID software ZIP:

[root@stc-vdi-01:~] nvidia-smi
Mon Jan 11 17:04:26 2021
±----------------------------------------------------------------------------+
| NVIDIA-SMI 440.43 Driver Version: 440.43 CUDA Version: N/A |
|-------------------------------±---------------------±---------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Tesla M60 On | 00000000:05:00.0 Off | Off |
| N/A 33C P8 27W / 150W | 8143MiB / 8191MiB | 0% Default |
±------------------------------±---------------------±---------------------+
| 1 Tesla M60 On | 00000000:06:00.0 Off | Off |
| N/A 30C P8 25W / 150W | 8143MiB / 8191MiB | 0% Default |
±------------------------------±---------------------±---------------------+

I can see the M60 GPU in task manager and it is working for graphical operations, just no OpenCL support.

The server is a Dell PowerEdge R730 and I have configured the Graphics Cards in VSphere like this:

As I understand it, this should work, what do I need to check for?

Thanks

Gary

Hi Gary

Looks like you’re running that command on the Hypervisor … Try running it inside the VM from a CMD prompt and it should work for you:

“C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi”

CUDA doesn’t get installed inside the Hypervisor, which is why the vGPU Manager doesn’t list it as per your image above. CUDA gets installed with the vGPU Driver inside the VM.

For reference, if you were running Pascal or newer architecture, you could use any Q Profile and be able to run CUDA workloads. It’s just Maxwell that requires the full 8Q Profile be used for CUDA due to the age of the architecture. But it’s a good place to start with, as it’s one of the few GPUs that allows you to run mixed vGPU Profiles concurrently on the same board.

Regards

MG

Hi, thanks for taking the time to get back to me on this.

Here is the output of the nvidia-smi command from withing the VM itself:

C:\Users\vrbuild>"c:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi.exe"
Tue Jan 12 11:48:52 2021
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 441.66       Driver Version: 441.66       CUDA Version: 10.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name            TCC/WDDM | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GRID M60-8Q        WDDM  | 00000000:02:02.0  On |                  N/A |
| N/A   N/A    P8    N/A /  N/A |    771MiB /  8188MiB |      2%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GRID M60-8Q        WDDM  | 00000000:02:03.0 Off |                  N/A |
| N/A   N/A    P8    N/A /  N/A |    542MiB /  8188MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0       800    C+G   Insufficient Permissions                   N/A      |
|    0      1092    C+G   Insufficient Permissions                   N/A      |
|    0      3900    C+G   ...m Files\PiXYZStudio\bin\PiXYZStudio.exe N/A      |
|    0      6140    C+G   Insufficient Permissions                   N/A      |
|    0      6568    C+G   ...dows.Cortana_cw5n1h2txyewy\SearchUI.exe N/A      |
|    0      6716    C+G   ...t_cw5n1h2txyewy\ShellExperienceHost.exe N/A      |
|    0      7028    C+G   C:\Windows\explorer.exe                    N/A      |
+-----------------------------------------------------------------------------+

Within the VM, Compute Mode also shows as “default” which I think means that CUDA/OpenCL should be available in the VM, but GPU-Z (and also my compute app) both say that OpenCL is not available in the VM:

You will note that I have used the m60_8q profile, which should allocate an entire GPU to the VM, which should allow OpenCL/CUDA (as it is not a shared GPU without pre-emption)

So, how do I enable OpenCL in the VM?

Thanks

Gary

Hi

It should just work with that Profile. There’s no special configuration to enable it. I assume the VM has successfully acquired a vGPU License?

Also noticed you’re not running the latest driver branch. vGPU 11.x will install CUDA 11 if that’s better for your workload.

Regards

MG

Hi,

I am only performance testing to evaluate various hardware setups at this time (I may not virtualise and just run on baremetal) and have not setup a flexlm license server yet. I was under the impression that it should work (albeit with a pop-up warning) for testing. Certainly, the vGPU for graphics is working OK, is the OpenCL/CUDA computation mode different - does it definitely need the vGPU license before it will enable?

Once again, thanks for you response.

Rgds

Gary

Hi Gary

Yes, please make sure it’s licensed. Functionality will reduce very quickly if the VM is not licensed.

You can register for a vGPU evaluation here GRID Evaluation | NVIDIA However as you already have the vGPU software, I’m assuming you already have access to the licenses and an evaluation. Setting up a license server is very quick, so you should be up and running in no time!

Regards

MG