在不使用Citrix/VmWare的情况下部署GRID

remoteFX解决方案不是直通解决方案。
“Microsoft RemoteFX Grapics设备 -  WDDM”不是NVidia设备，NVidia驱动程序不附加。
Grid VM驱动程序用于vGPU（例如，仅在VMware / Xenserver虚拟机管理程序VM解决方案中支持的不同“模拟”pci-id）。
虚拟机管理程序中不应该需要用于直通的驱动程序（仅将GPU配置为直通虚拟机，GPU从任何虚拟机管理程序“消失”）。
您可能正在寻找WS2016支持的GPU的“离散设备分配”（您应该在网上搜索）。
如果您能够成功通过设备，那么您应该使用标准驱动程序直接或直接使用标准下载位置http://www.nvidia.com/Download/index.aspx?lang=en-us  - >“GRID” -
>“GRID系列” - > ...  - > 376.33-quadro-grid-desktop-notebook-win8-win7-64bit-international-whql.exe您必须购买并安装特斯拉M10直通的NVidia许可证（参见“网格许可”）
“）。
（更新：我期待nv_dispwi.inf但驱动程序包中缺少支持Tesla M10。来自许可门户的软件包可能用于直通。）
您也可以使用Linux KVM或Linux / FreeBSD XEN（除了XenServer）进行直通。
我的观点：Maxwell一代多芯片直通卡有更便宜的解决方案 -  GRID M40（不是特斯拉M40！）卡。
它与M10相同，但是内存的一半（例如，每GPU 4GB，特斯拉M10的更大RAM，每张卡的额外芯片成本约为100美元，然后是GRID M40，请参阅https://gridforums.nvidia.com/default/topic
/ 823 /网格板/特斯拉-M10 /）。
但NVidia否认存在GRID M40板（从未设计，制造，销售或支持，但请查看Ebay）。
在之前的开普勒产品中支持配对板解决方案（用于vGPU和直通） -  K1~K340（更多SM /更少内存）和K2~K520。
或者，您可以使用中间和更高版本的Quadro模型，这些模型已经准备就绪（http://www.nvidia.com/object/dedicated-gpus.html + http://www.nvidia.com/object/sli_multi_os.html  -  NVidia
没有披露直通支持的更新列表，但是对于XenServer http://hcl.vmd.citrix.com/gpus/有一些HCL（M10目前尚未正式通过认证））。



以下为原文

• The remoteFX solution is not passthrough solution. "Microsoft RemoteFX Grapics Device - WDDM" is not NVidia device and NVidia drivers does not attach.
  
• The Grid VM driver is for vGPU (eg. different "emulated" pci-id supported only in VMware/Xenserver hypervisor VM solution).
  
• There should not be needed driver in hypervisor for passthrough (only configure GPU as passthrough to VM and GPU "disappears" from any hypervisor).
  

You are probably looking for "Discrete Device Assignment" for GPU that is supported from WS2016 (you should search the web). If you are able to successfully passthrough device then you should use standard driver for passthrough or direct use from standard download location http://www.nvidia.com/Download/index.aspx?lang=en-us -> "GRID" -> "GRID Series" -> ... -> 376.33-quadro-grid-desktop-notebook-win8-win7-64bit-international-whql.exe and you must buy and install NVidia license for Tesla M10 passthrough (see "GRID LICENSING"). (Update: I look to nv_dispwi.inf but support Tesla M10 is missing in driver package. The package from licensing portal should be probably used for passthrough.)


You can also use Linux KVM or Linux/FreeBSD XEN (besides XenServer) for passthrough.

My opinion: There was cheaper solution for Maxwell generation multiple chip passthrough card - GRID M40 (not Tesla M40!) card. It was the same board as M10 but half of memory (eg. 4GB per GPU, larger RAM for Tesla M10 is about $100 additional chip cost per whole card then GRID M40, see https://gridforums.nvidia.com/default/topic/823/grid-boards/tesla-m10/). But NVidia deny existence of GRID M40 board (never design, build, sell or support, but check Ebay). There was supported paired board solution (for vGPU and for passthrough) in previous Kepler generation - K1 ~ K340 (more SM/less memory) and K2 ~ K520.
Alternatively you can use middle and higher Quadro models that are passthrough ready (http://www.nvidia.com/object/dedicated-gpus.html + http://www.nvidia.com/object/sli_multi_os.html - NVidia does not disclosure updated list for passthrough support but there is HCL for example for XenServer http://hcl.vmd.citrix.com/gpus/ (M10 is not officially certified for passthrough now)).

您需要M10的评估许可证，门户网站内有一个超V /服务器2016。
许可将取决于您如何交付它RemoteFX是vPC许可证和RDSH vApps，如果没有quadro需求。
本文包含从何处获取M10驱动程序的详细信息：http：//nvidia.custhelp.com/app/answers/detail/a_id/4120/~/where-to-find-the-drivers-for-nvidia-grid-2.0
-vgpu和行动， - 包括-M60，-M10



以下为原文

You will need an evaluation license for the M10, there is a hyper-V/server 2016 one available within the portal. Licensing would then depend on how you delivered it RemoteFX is a vPC license and RDSH vApps if no quadro needs.

This article contains details of where to get M10 drivers: http://nvidia.custhelp.com/app/answers/detail/a_id/4120/~/where-to-find-the-drivers-for-nvidia-grid-2.0-vgpu-and-up,-including-m60,-m10

似乎有一些社区设置指南：https：//blog.workinghardinit.work/2016/04/11/discrete-device-assignment-in-windows-server-2016-hyper-v/



以下为原文

There do seem to be some community set up guides around: https://blog.workinghardinit.work/2016/04/11/discrete-device-assignment-in-windows-server-2016-hyper-v/

嗨Mcerveny！
谢谢你的快速回复伴侣！
我们已经安装了WS2016并为VM分配了（DDA）一个M10实例（Win10Ent，RDP 10.2）并且它可以工作。
然而，性能并不是那么好，我将不得不找出原因。
我们已经使用Windows 8（RDP 8.1）登录到Win10，但渲染时有点滞后。
我将不得不开始阅读博客和帖子猜测所以:)
根据你的M40理论：你可能是对的，当列出PCI设备时，卡在DELL iDRAC中将自己标识为M40。
问候，
麦克风



以下为原文

Hi Mcerveny!

Thanks for the quick reply mate! We've installed a WS2016 and assigned (DDA) one M10 instance to the VM (Win10Ent, RDP 10.2) and it works. However the performance isn't that great, I'll have to find out why.

We have logged in with a Windows 8 (RDP 8.1) onto the Win10 but the rendering it's somewhat laggy. I'll have to start reading blogs and posts guess so:)

As per your M40 theory: you're probably right, the card identifies itself as a M40 in the DELL iDRAC when listing the PCI devices.

Regards,
MIke