We have an M60 on our ESXi 6.5 host with pass-thru to a Windows 2012 R2 guest VM. Windows can see the M60 device, gpumodeswitch reports it as Graphics mode, but NVIDIA Control Panel says it is dedicated for compute and applications can’t see it.
Strangely enough I was able to make it work previously with this setup on a different Windows VM. I haven’t changed anything on the VMware side of things, so I’m guessing it’s a Windows setting/issue.
For the record I found and solved the problem - cause is a bad NVIDIA driver.
I can reliably reproduce this problem on VMware ESXi 6.5 with a M60 (both in Graphics mode) pass-thru to a Windows 2012 R2 guest VM (fresh Windows install from ISO) using the Tesla M60 Windows 2012 R2 CUDA 8 driver version 385.08.
Once I downgraded to driver version 377.35 everything works as expected.
I have same issue on Windows 7 Professional x64 VM with Tesla M60 Windows 7 and 8 64 bit 385.08 driver installed from http://www.nvidia.ru/download/driverResults.aspx/121535/ru. NvAPI_EnumPhysicalGPUs fails with result: NVAPI_NVIDIA_DEVICE_NOT_FOUND - No NVIDIA GPU driving a display was found. NvAPI_EnumTCCPhysicalGPUs( NvPhysicalGpuHandle nvGPUHandle[NVAPI_MAX_PHYSICAL_GPUS], NvU32 *pGpuCount); returns NVAPI_OK and pGpuCount equals 1.
Everything works fine with 377.35 and 377.55 drivers.
But Get Even game requires driver version to be greater than or equal to 385.
It’s a bit confusing now that there are two separate areas for driver downloads. I wish the newer ones could skip to a totally different numbering system so that it would be more obvious which are compatible with the newer GRID releases.
In the above example the "CUDA 8" is a giveaway that this isn’t the right option for running in vGPU/GPU graphics mode.