来宾驱动程序与“许可证类型”无关（它必须与VGX协议兼容）。
主机驱动程序（XenServer / ESXi）将请求的许可证类型推送到Guest虚拟化/中介驱动程序，并且访客驱动程序请求许可证。
如果您有主机驱动程序“367.123”（与Guest驱动程序“370.17”捆绑在一起），则主机端“/usr/share/nvidia/vgpu/vgpuConfig.xml”M60-1Q的签名文件请求其中一个许可证“GRID-Virtual
-WS，2.0; Quadro-Virtual-DWS，5.0; GRID-Virtual-WS-Ext，2.0“在Guest中。
M10-1Q + 367.123 / 370.17 +许可证服务器5.1 / 2017.11对我有用。
如果您有较旧的主机驱动程序（例如“367.106”），请求的许可证是“GRID-Virtual-WS，2.0; GRID-Virtual-WS-Ext，2.0”！
您应该升级主机驱动程序。
如果您已升级主机驱动程序，旧的许可证请求字符串可能会卡在某些注册表设置中（尝试执行一些regedit清理或重新安装Guest驱动程序）。
Grid4中未强制执行许可证可能是由于许可/营销混乱（以及像您这样的问题），许可证服务器无法处理K1 / K2卡的“无”许可证请求。
您可以忽略“许可证弹出”或停止许可证请求（删除“CurrentControlSet”中的regkey“GridLicensedFeatures”）。
以上来自于谷歌翻译
以下为原文
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").
来宾驱动程序与“许可证类型”无关（它必须与VGX协议兼容）。
主机驱动程序（XenServer / ESXi）将请求的许可证类型推送到Guest虚拟化/中介驱动程序，并且访客驱动程序请求许可证。
如果您有主机驱动程序“367.123”（与Guest驱动程序“370.17”捆绑在一起），则主机端“/usr/share/nvidia/vgpu/vgpuConfig.xml”M60-1Q的签名文件请求其中一个许可证“GRID-Virtual
-WS，2.0; Quadro-Virtual-DWS，5.0; GRID-Virtual-WS-Ext，2.0“在Guest中。
M10-1Q + 367.123 / 370.17 +许可证服务器5.1 / 2017.11对我有用。
如果您有较旧的主机驱动程序（例如“367.106”），请求的许可证是“GRID-Virtual-WS，2.0; GRID-Virtual-WS-Ext，2.0”！
您应该升级主机驱动程序。
如果您已升级主机驱动程序，旧的许可证请求字符串可能会卡在某些注册表设置中（尝试执行一些regedit清理或重新安装Guest驱动程序）。
Grid4中未强制执行许可证可能是由于许可/营销混乱（以及像您这样的问题），许可证服务器无法处理K1 / K2卡的“无”许可证请求。
您可以忽略“许可证弹出”或停止许可证请求（删除“CurrentControlSet”中的regkey“GridLicensedFeatures”）。
以上来自于谷歌翻译
以下为原文
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").
举报
举报
