Small test--enable REMOTEFX-GPU virtualization in Windows Server 2016

These two days because of the need to deploy a lot of W2016DC servers, including a workstation with Nvidia Quadro K4200 graphics card, it is easy to test the W2016 Remotefx-gpu virtualization function, the process is as follows, very simple, for the needs of friends to do a reference. Let's take a brief look at this feature. It starts with Windows R2SP1, and with dynamic memory technology, primarily for server virtualization and desktop virtualization markets. The RemoteFX contains three sub-functions: GPU virtualization, enhanced codec, and USB port redirection. By virtualizing the physical GPU and assigning it to the virtual machine, the VM can also have a more complete graphics processing capability, such as the ability to run applications based on Flash, DirectX, and so on, and the process is simple and easy to use. The requirements for VDI clients are also low, as long as the rdp8/8.1 can be supported. Graphics card selection is more important, you can refer to the following Microsoft's official blog, especially the physical graphics card memory size, because when the RemoteFX virtual out Vgpu, assigned to each VM Vgpu memory is not overcommit.

https://blogs.technet.microsoft.com/enterprisemobility/2013/11/05/gpu-requirements-for-remotefx-on-windows-server-2012-r2/

After the preparation has been completed, the configuration can be started, the physical machine installed in this test W2016 data center version, the virtual machine test W2016 Data Center version and WIN10 Professional Edition respectively.

1. The following are the specific models of the graphics card in the physical machine:

650) this.width=650; "title=" 1.png "src=" https://s4.51cto.com/wyfs02/M02/8E/76/wKiom1jBC9riBEfEAAD_ Ukarprw273.png-wh_500x0-wm_3-wmp_4-s_1972790630.png "alt=" Wkiom1jbc9ribefeaad_ukarprw273.png-wh_50 "/>

2. Add the Hyper-V role and the Remote Desktop Virtualization host role because only functional testing is done, so roles such as Remote Desktop Connection Broker and authorization are not deployed, but these are necessary in a production environment. Refer to the diagram below to restart the machine upon completion.

650) this.width=650; "title=" 2.png "src=" https://s3.51cto.com/wyfs02/M01/8E/74/ Wkiol1jbculysvm4aacyfdw9l1k329.png-wh_500x0-wm_3-wmp_4-s_3111290505.png "alt=" Wkiol1jbculysvm4aacyfdw9l1k329.png-wh_50 "/>

650) this.width=650; "title=" 3.png "src=" https://s1.51cto.com/wyfs02/M01/8E/74/ Wkiol1jbcyuq6zmwaab4ebzqqm0616.png-wh_500x0-wm_3-wmp_4-s_2579883569.png "alt=" Wkiol1jbcyuq6zmwaab4ebzqqm0616.png-wh_50 "/>

3. Open Hyper-V Manager, right-click Hyper-V Physical machine, select "Hyper-V Settings ..."-click on "Physical GPU, manage RemoteFX GPU", select the GPU you need to enable virtualization on the right, tick " Use this GPU for RemoteFX ". After the app you can see details such as supported DirectX versions, WDDM driver versions, memory sizes, and more.

650) this.width=650; "title=" 4.png "src=" https://s2.51cto.com/wyfs02/M02/8E/74/wKioL1jBC5vx5_ Ibaact8vdcpp8242.png-wh_500x0-wm_3-wmp_4-s_3928146470.png "alt=" Wkiol1jbc5vx5_ibaact8vdcpp8242.png-wh_50 "/>

4. The power off needs to add VGPU virtual machine, open its settings interface, in the "Add Hardware" menu, select Add "RemoteFX 3D video adapter":

650) this.width=650; "title=" 5.png "src=" https://s5.51cto.com/wyfs02/M01/8E/75/ Wkiol1jbdkugtwhfaacwxmeghjy411.png-wh_500x0-wm_3-wmp_4-s_2011910718.png "alt=" Wkiol1jbdkugtwhfaacwxmeghjy411.png-wh_50 "/>

5. Next, set the virtual machine's maximum number of monitors, resolution and memory size as needed:

650) this.width=650; "title=" 6.png "src=" Https://s3.51cto.com/wyfs02/M02/8E/75/wKioL1jBDVeR6qOcAACbrfIUi_ G316.png-wh_500x0-wm_3-wmp_4-s_188560690.png "alt=" Wkiol1jbdver6qocaacbrfiui_g316.png-wh_50 "/>

6. The same method is added to configure the next virtual machine Vgpu, and finally back to the Hyper-V Physical Machine Setup interface to see the physical graphics Resource usage:

650) this.width=650; "title=" 7.png "src=" https://s3.51cto.com/wyfs02/M01/8E/76/ Wkiom1jbdkpco-staactmuvesuy651.png-wh_500x0-wm_3-wmp_4-s_2002982701.png "alt=" Wkiom1jbdkpco-staactmuvesuy651.png-wh_50 "/>

7. Start the virtual machine with VGPU added and open its Device Manager to see the VGPU device:

650) this.width=650; "title=" 8.png "src=" https://s3.51cto.com/wyfs02/M02/8E/75/ Wkiol1jbdt2sc9c6aacleqdc0hm998.png-wh_500x0-wm_3-wmp_4-s_3534337199.png "alt=" Wkiol1jbdt2sc9c6aacleqdc0hm998.png-wh_50 "/>

8. Run DxDiag in the virtual machine to see that the DirectX related Acceleration feature is enabled:

650) this.width=650; "title=" 9.png "src=" https://s3.51cto.com/wyfs02/M01/8E/75/ Wkiol1jbd43cszxoaaejevuhg40077.png-wh_500x0-wm_3-wmp_4-s_2413322733.png "alt=" Wkiol1jbd43cszxoaaejevuhg40077.png-wh_50 "/>

9. Finally, the installation of the Autodesk 3ds max software test effect, feel good overall, the operation is relatively smooth, of course, only the single-machine load is not heavy under the circumstances of the simple test. For reference only.

650) this.width=650; "title=" 3dmaxtest.png "src=" https://s5.51cto.com/wyfs02/M01/8E/75/ Wkiol1jbeg2hz440aaomxrw0qjw570.png-wh_500x0-wm_3-wmp_4-s_1712727498.png "alt=" Wkiol1jbeg2hz440aaomxrw0qjw570.png-wh_50 "/>

This article is from the "servers in the Cloud" blog, so be sure to keep this source http://yddfwq.blog.51cto.com/4016432/1904830

Small test--enable REMOTEFX-GPU virtualization in Windows Server 2016