控制台上的DX11全屏输出很奇怪

M.C， 
在全屏模式下看起来像应用程序问题。
您是否使用3Dmark11进行了测试，如果是这样，它是否以全屏模式进行复制？



以下为原文

M.C,
Looks like a application issue in fullscreen mode. Have you tested with 3Dmark11, if so does it replicate in full screen mode?

3Dmark11（基本版）在所有测试中都可以。
同样的错误出现在Unigine的Valley Benchmark中。
我发送邮件给Unigine支持。
M.C>



以下为原文

3Dmark11 (Basic) is ok in all tests.
The same error is in Unigine’s Valley Benchmark.
I sent mail to Unigine support.

M.C>

你使用什么虚拟化堆栈和协议？



以下为原文

What virtualisation stack and protocols are you using?

你能在Citrix XenServer上试试这个吗？
我们目前不支持开源Xen上的vGPU，因此让我们看看您是否可以在XenServer上复制该问题。 
如果您可以复制该问题，我们可以采取措施来获取错误。



以下为原文

Can you try this out on Citrix XenServer? We don't currently support vGPU on open source Xen, so lets see if you can replicate the issue on XenServer.

If you can replicate the issue, we can move to get a bug raised.

你好。
是的，我确认支持的XenServer上的错误。
-  XenServer 6.5 + XS65E002 +“桌面+”许可证
-  drivers dom0 / domU 340.57 / 341.08
- 另一个具有不同固件的nvidia K1（VBIOS 80.07.6D.00.0 *）
-  domU全新安装的Windows 7
- 来自vnc console的截图（设置，加载和运行屏幕截图）
我在XenServer上报告了错误：https：//bugs.xenserver.org/browse/XSO-212
在哪里向Nvidia报告错误？
M.C>



以下为原文

Hello.

Yes, I confirm the error on supported XenServer.
- XenServer 6.5 + XS65E002 + "Desktop+" license
- drivers dom0/domU 340.57/341.08
- another nvidia K1 with different firmware (VBIOS 80.07.6D.00.0*)
- domU fresh install of windows 7  
- screenshots from vnc console (setup, loading and running screenshots)



I reported bug on XenServer: https://bugs.xenserver.org/browse/XSO-212
Where to report bug to Nvidia ?

M.C>

这可能取决于VNC抓取显示器并传输它的方式（全屏幕以不同的方式绘制到窗口应用程序）。
据我所知，VNC不利用GRID SDK，因此刮取屏幕不能直接从帧缓冲区读取。
我怀疑这是错误的协议。



以下为原文

It's possibly down to the way VNC grabs the display and transmits it (fullscreen is drawn differently to a windowed app).

VNC, as far as I'm aware, doesn't leverage the GRID SDK, so is scraping the screen not reading directly from the frame buffer.

I'd suspect it's the protocol at fault here.

Console vnc viewer不受标准DomU安装的vnc服务器的支持。
控制台vnc由Dom0 qemu与nvidia + xenserver集成生成（nvidia“libnvidia-vgx.so”api和“vgpu”io服务器）。
（如果您尝试使用标准的DomU安装的vnc服务器，您会在gpu加速全屏应用中看到“黑屏”）。
M.C>



以下为原文

Console vnc viewer is NOT backed by standard DomU installed vnc server.
Console vnc is generated by Dom0 qemu with nvidia+xenserver integration (nvidia "libnvidia-vgx.so" api and "vgpu" io server).

(If you try to use standard DomU installed vnc server you see only "black screen" in gpu accelerated fullscreen appliaction).

M.C>

我仍然怀疑它是错误的协议。
我可以用VNC复制它，但ICA / HDX或PCoIP都不会受到影响，这强烈表明了VNC协议本身。
你有其他可以测试的协议吗？



以下为原文

I still suspect it's the protocol at fault.

I can replicate this with VNC, but neither ICA/HDX or PCoIP are affected which strongly indicate the VNC protocol itself.

Do you have another protocol you can test with?

不，官方XenServer / Dom0 / qemu不允许更改“有线”协议（vnc）。
但我有同样的问题，如果我编码直接从Nvidia vgpu hypervisor API vmiop_presentation_put_message / vmiop_dt_frame访问的缓冲区（到jpeg）。
如果DomU传输有效，这应该是Nvidia vgpu hypervisor（例如libnvidia-vgx.so和nvidia Dom0驱动程序）中的错误。
Nvidia vgpu hypervisor中还有更多未解决的错误
- 它不显示鼠标指针
- 它有时会无序显示帧
https://gridforums.nvidia.com/default/topic/257/
-  nvidia hypervisor dom0驱动程序不包含linux内核和nv.o blob之间桥接的源代码
https://gridforums.nvidia.com/default/topic/231/
M.C>



以下为原文

No, official XenServer/Dom0/qemu does not allow to change "wire" protocol (vnc).
But I have the same issue was if I encode buffer (to jpeg) accessed directly from Nvidia vgpu hypervisor API vmiop_presentation_put_message/vmiop_dt_frame.
This should be bug in Nvidia vgpu hypervisor (eg. libnvidia-vgx.so and nvidia Dom0 driver) if DomU transfers works.

There are more unresolved bugs in Nvidia vgpu hypervisor
- it does not show mouse pointer
- it sometimes displays frames out-of-order
https://gridforums.nvidia.com/default/topic/257/
- nvidia hypervisor dom0 driver does not contains source codes for bridge between linux kernel and nv.o blob
https://gridforums.nvidia.com/default/topic/231/

M.C>

基于我认为你想做的事情，我正在将这个主题移到API的论坛。
您可以在SDK中找到您要查找的内容，其中包含开发您自己的h264编码流的方法。
https://developer.nvidia.com/grid-app-game-streaming



以下为原文

Based on what I think your trying to do, I'm moving this thread to the API's forum.

You may find what you're looking for in the SDK, which contains the means to develop your own h264 encoded stream.


https://developer.nvidia.com/grid-app-game-streaming

你好。
感谢您的回答。
但我不喜欢转移到DomU SDK仅用于流媒体视频（具有许多Windows API复杂性）。
Dom0流媒体是独立于平台的工作，具有所有DomU操作系统和模式（例如模拟VGA模式（非常典型且通常用于Windows的“安全模式”））。
此外，所有其他流（u***，audio）在Dom0中完美而透明地工作。
安全性也更高（带外分离的以太网端口）。
如果Nvidia将此问题更正为Dom0中的frambebuffer输出和/或将h264的“网格游戏SDK”添加到dom0和/或至少将“Cuda”添加到dom0以便mjpeg卸载或披露配置如何使用“其他”，我将非常高兴
（非K1 / K2）Nvidia卡支持dom0。
谢谢，M.C>



以下为原文

Hello.

Thanks for your answer. But I dislike to move to DomU SDK for streaming video only (with many windows API complications).

Dom0 streaming is platform independent works with all DomU operating systems and modes (for example emulated VGA mode (very typical and often "safe mode" for windows)). Also all other streams (u***,audio) works perfectly and transparently in Dom0. Security is also higher (out-of-band separated ethernet ports).

I will be very pleased if Nvidia corrects this issues to frambebuffer output in Dom0 and/or add "Grid Gaming SDK" for h264 to dom0 and/or at least "Cuda" to dom0 for mjpeg offloading or disclosure config how to use "other" (non K1/K2) Nvidia card for this support in dom0.

Thanks, M.C>

新驱动程序340.78 / 341.44  - 没有任何变化:-(



以下为原文

New drivers 340.78/341.44 - nothing changes :-(

新驱动程序352.46 / 354.13  - 没有任何变化:-(
而K2代替K1没有帮助。
我找到了解决方法 - 只需最小化和恢复（或切换任务）3D应用程序窗口，一切正常。



以下为原文

New drivers 352.46/354.13 - nothing changes :-(

The K2 instead K1 does not help.
I found workaround - simply minimize and restore (or switch task) 3D application window and all is ok.

经过一年和6年发布WHQL认证的驱动程序后，问题仍然存在。
这似乎是MSFT认证过程和NVidia DX11驱动程序开发人员的失败。
XenServer团队仅以NVidia错误https://bugs.xenserver.org/browse/XSO-212关闭了票证。
如果您尝试在vGPU上将Witcher3切换到DX11全屏，我会附加视频。
这与NVidia错误相同也是同样的问题。



以下为原文

After year and 6 released WHQL certified drivers the problem still exists. This seems to be fail of MSFT certification process and NVidia DX11 driver developers.
XenServer team closed ticket as solely NVidia error https://bugs.xenserver.org/browse/XSO-212.

I attached video if you try to switch Witcher3 to DX11-fullscreen on vGPU. This is the same problem with the same NVidia error.

毫不奇怪仍然有bug的Dom0驱动程序 -  352.70,352.83,361.40,361.45.09,352.97,367.43 / 369.17（Grid4.0），367.64 / 369.71（Grid4.1），367.92 / 369.95（Grid4.2），367.106 / 370.12（
Grid4.3），367.12 / 370.16（Grid4.4）......
05/31/2016  - 让我们庆祝500天而不解决这个错误！
2017年1月17日 - 让我们庆祝2年而不解决这个错误！



以下为原文

not surprisingly still buggy Dom0 driver - 352.70, 352.83, 361.40, 361.45.09, 352.97, 367.43/369.17 (Grid4.0), 367.64/369.71 (Grid4.1), 367.92/369.95 (Grid4.2), 367.106/370.12 (Grid4.3), 367.12/370.16 (Grid4.4)...

05/31/2016 - Let us celebrate 500 days without resolving this bug !
01/17/2017 - Let us celebrate 2 years without resolving this bug !

10/12/2017  - 让我们庆祝1000天而不解决这个错误！



以下为原文

10/12/2017 - Let us celebrate 1000 days without resolving this bug !