NVIDIA
Desktops requesting wrong license
So we have a collection of desktops running the m60-1q profile. They are running driver version 370.17. Our issue is none of them will pull a license from the server. This is only affecting our vDWS pools and not vPC pools. Those pull a license. But for some reason, our vDWS machines are only requesting a "GRID-Virtual-WS Version=2.0" and not a "Quadro-Virtual-DWS Version=5.0" which we have licenses for. Anyone seen this issue or have any ideas? License server is version 5.1 (latest). Thanks
So we have a collection of desktops running the m60-1q profile. They are running driver version 370.17.

Our issue is none of them will pull a license from the server. This is only affecting our vDWS pools and not vPC pools. Those pull a license. But for some reason, our vDWS machines are only requesting a "GRID-Virtual-WS Version=2.0" and not a "Quadro-Virtual-DWS Version=5.0" which we have licenses for.

Anyone seen this issue or have any ideas?

License server is version 5.1 (latest).

Thanks

#1
Posted 05/04/2018 11:41 PM   
Guest driver is not "license type" relevant (it must be compatible with VGX protocol). Host driver (XenServer/ESXi) pushes requested license types to Guest paravirtualized/mediated driver and Guest driver ask for license. If you have Host driver "[b]367.123[/b]" (that is bundled with Guest driver "370.17") than Host side "/usr/share/nvidia/vgpu/vgpuConfig.xml" signed file for M60-1Q requests one of license "[b]GRID-Virtual-WS,2.0;Quadro-Virtual-DWS,5.0;GRID-Virtual-WS-Ext,2.0[/b]" in Guest. M10-1Q + 367.123/370.17 + license server 5.1/2017.11 works for me OK. If you have older Host driver (for example "[b]367.106[/b]") the requested licenses are "[b]GRID-Virtual-WS,2.0;GRID-Virtual-WS-Ext,2.0[/b]" ! You should [b]upgrade Host driver[/b]. If you already upgraded Host driver the old license request string may be stuck in some registry setting (try to do some regedit cleanup or reinstall Guest driver). The licenses are not enforced in Grid4 probably due to licensing/marketing chaos (and problems like yours) and license server cannot handle "none" license request for K1/K2 cards. You can ignore "license pop-up" or stop license requests (delete regkey "[b]GridLicensedFeatures[/b]" in "CurrentControlSet").
Guest driver is not "license type" relevant (it must be compatible with VGX protocol). Host driver (XenServer/ESXi) pushes requested license types to Guest paravirtualized/mediated driver and Guest driver ask for license.
If you have Host driver "367.123" (that is bundled with Guest driver "370.17") than Host side "/usr/share/nvidia/vgpu/vgpuConfig.xml" signed file for M60-1Q requests one of license "GRID-Virtual-WS,2.0;Quadro-Virtual-DWS,5.0;GRID-Virtual-WS-Ext,2.0" in Guest. M10-1Q + 367.123/370.17 + license server 5.1/2017.11 works for me OK. If you have older Host driver (for example "367.106") the requested licenses are "GRID-Virtual-WS,2.0;GRID-Virtual-WS-Ext,2.0" ! You should upgrade Host driver. If you already upgraded Host driver the old license request string may be stuck in some registry setting (try to do some regedit cleanup or reinstall Guest driver).

The licenses are not enforced in Grid4 probably due to licensing/marketing chaos (and problems like yours) and license server cannot handle "none" license request for K1/K2 cards. You can ignore "license pop-up" or stop license requests (delete regkey "GridLicensedFeatures" in "CurrentControlSet").

#2
Posted 05/05/2018 12:21 PM   
Scroll To Top

Add Reply