VMware Horizon 6.1零客户端断开连接上的vGPU

结合VMware，我们相信我们现在已经确定了问题的原因，并且正在努力尽快发布更新。
我目前没有时间表，但它是高度优先的。



以下为原文

In conjuction with VMware we believe we've now identified the cause of the issue and are working on releasing an update as soon as we can.

I don't have a timeline at present but it is high priority.

嗨，我有同样的问题。
你有什么新闻，我如何解决它或新的驱动程序何时可用？
谢谢你的回答。



以下为原文

Hi, I have the same issue. Do you have any news, how I can solve it or when the new driver will be available?
Thank you for an answer.

昨天我们发布了一组新的passthrough驱动程序，如果你在Passthrough / vDGA中遇到它，应该可以解决这个问题。
vGPU驱动程序将很快推出，由于它是一个2部分包，它会经历一个延长的QA循环，这就是为什么需要更长的时间。
发布已关闭，请在下周左右观看驱动程序页面，一旦我知道vGPU包可用，我就会更新该主题。



以下为原文

Yesterday we released a new set of passthrough drivers which should resolve this issue if your encountering it in Passthrough / vDGA.

The vGPU drivers will follow soon, due to being a 2 part package it goes through an extended QA cycle which is why it takes a little longer.

Release is close, watch the driver pages over the next week or so and as soon as I know the vGPU package is available I'll update the thread.

你知道我们在哪里可以得到那些直通司机吗？



以下为原文

Do you know where we can get those passthrough drivers?

驱动程序始终可从NVIDIA网站上的驱动程序下载页面获取。



以下为原文

The drivers are always available from the driver downloads page on the NVIDIA website.

现在已经超过两周了，没有新的驱动程序可用。
新驱动程序何时在线？
这对我来说非常重要，因为用户无法在水平视图环境中正常工作。



以下为原文

It's now more than two weeks and no new driver is availble. When is the new driver online? Its an very important point for me because the users can not work correctly on the horizon-view enwirement.

好的，现在有新的驱动程序可用。
它现在可以正确使用多监视器系统。



以下为原文

OK, new drivers are now available. It works now correct with multi-monitor-system.

ManuelS，您是否记录了错误或支持电话？
如果是这样，你会收到通知。
该驱动程序已于7月10日星期五发布并可供下载。
更新环境时，请检查ESX主机中已有的vGPU Manager版本。
如果已经是346.68，则无需更新vGPU管理器，只需更新VM / Master映像中的驱动程序。
如果您在主机中运行早期版本，例如
346.42，然后您需要在更新VM / Master映像之前更新主机中的vGPU Manager。



以下为原文

ManuelS, did you log a bug or support call? If so you would have been notified.

The driver was released and made available for download Friday 10th July.

When updating your environment check the version of vGPU Manager you already have in your ESX hosts. If it is already 346.68 you will not need to update the vGPU manager, only the driver in the VM / Master image.

If you are running an earlier release in the host e.g. 346.42, then you need to update vGPU Manager in the host before updating your VM / Master image.

嗨Jason，我的一些用户在开始新会话时报告了这些断开连接和黑屏。
即使没有多显示器系统，也不支持Windows和OS X.
当分辨率为1280x1024时，它工作正常，但更高的一切都可能导致客户端崩溃。
我用最新的驱动程序348.27更新了我的主映像，而vGPU管理器是346.68。
我们正在使用NVIDIA Grid K1（K120Q）
我收到这些错误：
IMG_FRONTEND：configure_displays：最初报告的1个显示！
IMG_FRONTEND：configure_displays：（1）单显示[0]：pos：（0,0）w：2560，h：1600，bpp：32
IMG_FRONTEND：在Tera2模式下调用打开显示。
IMG_FRONTEND：sw_host_get_display_modes： - 警告 - 未找到主显示
如问题＃59中所述，pcoip服务器也会在虚拟机上崩溃。
解决这个问题的任何方法？
谢谢
帕特里克



以下为原文

Hi Jason, some of my users reported these disconnects and black screens while starting a new session.
Even without multi-monitor-system and on Windows and OS X.
It works fine when the resolution is 1280x1024, but everything greater can result in a client crash.

I have updated my Master image with the latest driver 348.27 and vGPU Manager is 346.68.
We're using NVIDIA Grid K1 (K120Q)

I'm getting these errors:
IMG_FRONTEND :configure_displays: 1 display(s) initially reported!
IMG_FRONTEND :configure_displays: (1) single display[0]: pos:(0, 0) w: 2560, h: 1600, bpp: 32
IMG_FRONTEND :Calling open display in Tera2 mode.
IMG_FRONTEND :sw_host_get_display_modes:  - warning - primary display not found

As described in Issue #59, pcoip server also crashes on the vm.

Any solutions for this problem?

Thank you
Patrick

我们看到的问题与帕特里克完全相同。
我们刚刚将vGPU Manager vib升级到346.68并在VM /父（Win 7）映像上安装了驱动程序348.27。
这对驱动程序解决了一个已知问题，现在遇到了这个问题。
到底是怎么回事？？？
这导致我们的VDI项目延迟。
解决方法是什么？
强制单显示器并将屏幕分辨率保持在1280x1024及以下？
请解决这个问题。
谢谢。



以下为原文

We are seeing the exact same issue as Patrick is having.

We just upgraded vGPU Manager vib to 346.68 and installed driver 348.27 on VM/parent (Win 7) image. This pair of drivers resolved one known issue and now running into this issue. What is going on??? This is causing delay to our VDI project.

What's the workaround?  Force single monitor and keep the screen resolution to 1280x1024 and below?

Please resolve this. Thanks.

Nvidia驱动程序版本解决了NvFBC api被鼠标崩溃导致的断开连接问题。
如果您仍然遇到断开连接，请在VMware上记录支持电话，详细说明复制步骤。
干杯



以下为原文

The Nvidia driver release resolved the disconnect issues that were due to the NvFBC api being crashed by the mouse.

If you're still experiencing disconnects please log a support call with VMware detailing the reproduction steps.

Cheers

我可以证实这一点，因为我们已经在POC中看到了这一点，无论是在K1还是K2卡上。
由于pcoip_server_win32.exe进程崩溃，使用Windows驱动程序348.07的4监视器设置确实显示随机断开连接。
经过调查，确实发现nvfbc的Nvidia dll确实是罪魁祸首。
只需将虚拟机中的驱动程序更新为348.27即可解决此问题，ESX端的驱动程序保持不变。



以下为原文

I can confirm this as we've seen this in a POC, both on a K1 and K2 card. A 4 monitor setup with the windows driver 348.07 indeed showed random disconnects due to the pcoip_server_win32.exe process crashing. After investigation, the Nvidia dll referring to nvfbc was indeed found to be the culprit. Just updating the driver within the Virtual machine to 348.27 fixed this issue, the driver on the ESX side remained the same.

VMware支持请求将我发送给Nvidia，现在我回到VMware后遇到了很多问题和日志文件。
NvFBC还有问题：
## 1.189 |
NvFBC |
PID 4700 ##：适配器序号1的CheckIfCanCreateD3D :: IDirect3D9 :: CreateDevice（）失败，错误0x8876086c
## 1.190 |
NvFBC |
PID 4700 ##：CheckIfCanCreateD3D ::错误（NVFBC_ERROR_GENERIC）。
无法创建DX9设备..
我希望尽快得到一些答案，因为我们现在几乎不断地使用单个显示器和1280x1024断开连接。



以下为原文

VMware support request sent me to Nvidia, now after lots of questions and log files I'm back with VMware.
Still something wrong with NvFBC:
## 1.189 | NvFBC | PID 4700 ## : CheckIfCanCreateD3D :: IDirect3D9::CreateDevice() for adapter ordinal 1 failed with error 0x8876086c
## 1.190 | NvFBC | PID 4700 ## : CheckIfCanCreateD3D :: Error (NVFBC_ERROR_GENERIC). Could not Create DX9 Device..

I hope to get some answers soon as we are now having disconnects even with single monitor and 1280x1024 almost constantly..

感谢Patrick的更新。
如果您有任何新信息，请及时通知我们。
对于这个问题，我有一个与VMware开放的SR，但我没有从他们那里听到太多。
他们必须参加VMworld大会。



以下为原文

Thanks for the update Patrick. Please keep us updated if you get any new info. I have a SR open with VMware for this issue, but I haven't heard much from them. They must be all at the VMworld conference.

您是否为此记录了支持查询？
如果不是，你需要尽快这样做。



以下为原文



Have you logged a support query for this? If not you need to do this asap.

好的，我已经解决了，你可能也想尝试一下。
当我在具有K1的主机上安装346.68 VIB驱动程序时，我安装在以前版本的顶部。
你需要全新安装346.58 VIB。
综上所述：
从ESXi主机卸载现有VIB>重新引导主机>在主机上安装346.68 VIB驱动程序>再次重新引导主机。
瞧！
您可以在grid-vgpu-deployment-guide.pdf中找到准确的卸载命令
*他们真的应该在“346.68-348.27-nvidia-grid-quick-start-guide.pdf”中提到这一点。



以下为原文



Ok, I got it resolved and you may want to try this as well. When I installed 346.68 VIB driver on a host with K1, I'd installed on top of the previous version. You need to fresh install 346.58 VIB.

In summary:
uninstall the existing VIB from the ESXi host > reboot the host > Install 346.68 VIB driver on the host > reboot the host again. Voila!

You can find the exact command for uninstall in grid-vgpu-deployment-guide.pdf

* They really should mention this on the "346.68-348.27-nvidia-grid-quick-start-guide.pdf"

感谢joeVM的输入。
我会尽快测试一下。
VMware支持仍然要求我提供更多的日志包，到目前为止还没有解决方案。



以下为原文

Thank you joeVM for your input. I will test it as soon as possible.
VMware support is still asking me for more log bundles and so far without a solution..

谢谢你分享这个。
实际上不需要卸载.vib，但我们会将其反馈到QA中以确保它们测试升级以及删除/安装。



以下为原文



Thanks for sharing this.

It really  shouldn't be necessary to uninstall the .vib, but we'll feed this back into QA to make sure they test upgrades as well as remove / install.

谢谢Jason的评论。
这就是我的想法，这真的让我难过。
在升级之前，ESXi主机（K1）处于VMware维护模式，验证命令在升级后都显示驱动程序版本为346.68，然后主机重新启动。



以下为原文

Thanks Jason for your comment.

That's what I thought and this really stumped me. The ESXi host (K1) was put in the VMware maintenance mode before the upgrade and the verification commands all showed the driver version as 346.68 after the upgrade, and then the host was rebooted.