使用vGPU的Horizon View：未分配GPU资源

我们在Nvidia K1s上运行了几年的vSGA。
升级到Horizo​​n View 6.2并测试vGPU配置文件。
最初的测试进行得很顺利但是一旦我将我的池缩小了几个虚拟机失败的定制。
但是，Horizo​​n没有发生错误，它们只是处于自定义状态。
如果我强制重置电源然后响应Windows恢复以正常启动，它通常会继续定制并完成。
最好的部分是因为它永远不会启动，因为控制台是通过连接到VM的vGPU K100禁用的，所以我无法进入VNC。
这是非常奇怪的行为，我有一个与VMware的开放票。
当我挖掘日志时，我在VM的vmware.log中找到了这个有趣的项目：
2016-04-27T01：44：09.329Z |
MKS |
W110：GLWindow：无法保留主机GPU资源
2016-04-27T01：44：09.339Z |
VMX |
I120：[msg.mks.noGPUResourceFallback]硬件GPU资源不可用。
虚拟机将使用软件渲染。
如果你看看周围的工作，我重新启动VM，它最终会工作。
似乎在开机期间某些VM在K1上分配了GPU核心时出现故障。
我没有找到任何在线提到这个问题。
我会保持这篇文章更新。
系统环境
超微
双K1
ESXi 6.0 U2
Nvidia VIB 361.40
Windows Nvidia 362.13



以下为原文

We have been running vSGA for a couple years off of Nvidia K1s. Upgraded to Horizon View 6.2 and testing vGPU profiles. The initial testing went very well but once I scaled my pool out several VMs failed customization. However, no error occurred in Horizon, they just remained in a customization status.

If I forced a power reset and then responded to windows recovery to boot normally, it would usually continue customization and finish. The best part is because it never boots, I can't VNC into it as the console is disabled with the vGPU K100 attached to the VM. It is very odd behavior and I have an open ticket with VMware.  


As I dug through the logs, I found this interesting item in the vmware.log for the VM:

2016-04-27T01:44:09.329Z| mks| W110: GLWindow: Unable to reserve host GPU resources
2016-04-27T01:44:09.339Z| vmx| I120: [msg.mks.noGPUResourceFallback] Hardware GPU resources are not available. The virtual machine will use software rendering.

If you look at the work around, where I power reset the VM and it eventually works. It seems like there is a failure during power on for some VMs to get assigned a GPU core on the K1s. I haven't found ANYTHING online referring to this issue. I'll keep this post updated.


System Environment

• Super Micro
  

• Dual K1s
  

• ESXi 6.0 U2
  

• Nvidia VIB 361.40
  

• Windows Nvidia 362.13