- #VMWARE HORIZON VIEW CLIENT DUAL MONITOR HOW TO#
- #VMWARE HORIZON VIEW CLIENT DUAL MONITOR INSTALL#
- #VMWARE HORIZON VIEW CLIENT DUAL MONITOR DRIVER#
- #VMWARE HORIZON VIEW CLIENT DUAL MONITOR WINDOWS 10#
- #VMWARE HORIZON VIEW CLIENT DUAL MONITOR LICENSE#
Just as with other processes, you can use the ControlUp Console to control GPU processes. If you have multiple virtual desktops using GPU, then you will be able to monitor and sort all of the processes running on those virtual desktops. In the information grid in the screenshot below, for instance, you can see that viewperf, VMBlastW and dwm are using GPU resources and that the VMBlastW is using the GPU decoder. To do this, select the Processes tab from the navigation bar.Īgain, the default view doesn’t display any GPU information, so you will need to select GPU Info from the Column Presets drop-down menu on the ribbon bar. Not only can you see the overall GPU activity on a virtual desktop, but you can also dive in further and see what specific processes are consuming the GPU. The right section of the grid shows information about GPU usage on the virtual desktop.
#VMWARE HORIZON VIEW CLIENT DUAL MONITOR LICENSE#
The middle section on the grid shows information about the GPU and its license server. The grid’s left section shows general information about the virtual desktop. The information grid will now show information about the GPU. To get to a ControlUp information grid that shows GPU metrics, double-click on a virtual desktop or a folder with GPU-enabled desktops, and select the Machines tab from the navigation bar.Īlthough the default view doesn’t display any GPU information, you can configure it to do so by selecting Detailed View – NVIDIA GPU from the Column Presets drop-down menu on the ribbon bar.
#VMWARE HORIZON VIEW CLIENT DUAL MONITOR INSTALL#
One of great things about using ControlUp to monitor GPU activity on a virtual desktop is that you don’t need to install or enable anything extra as long as you have the CUp agent running, you will be able to see the GPU information.
Monitoring GPU Using the ControlUp Console The T4 GPU attached to it had 256 MB of video memory and 512 MB of 3D memory. The virtual desktop was running Windows 10, and had 4 vCPUs, 16 GB of RAM, a 64 and 200 GB virtual disk. To verify that the T4 was installed and configured correctly, I examined it with the vSphere Web Client. The server had VMware ESXi 6.7U1 installed on it and was being managed by a 6.7 vCenter server. For persistent storage for the virtual desktop, I used a single SSD-based datastore which was directly attached to the server. The ESXi host I used was a Dell PowerEdge R740xd with two Intel Xeon Gold 6248 CPU 2.50GHz, 256GB of DDR4 2667MHz RAM, and with the NVIDIA Turing T4 GPU installed in it.
The T4 connects to the server via a x16 PCIe Gen3 interface, and is capable of 65 TFLOPS of mixed-precision (FP16/FP32) calculations and of handling the most demanding of VDI workloads. The GPU I used was an NVIDIA Turing T4 GPU with 320 Turing Tensor Cores and 16 GB of GDDR6 RAM. This VDI client can have up to 6 monitors attached to it, but for this article I attached a single 4K monitor.
#VMWARE HORIZON VIEW CLIENT DUAL MONITOR WINDOWS 10#
Windows 10 Enterprise 2016 LTSB 64-bit was also preinstalled on the device. The VDI client was a Wyse 5070 equipped with an Intel Pentium Silver J5005 CPU, 8 GB DDR4 RAM, Intel UHD Graphics 605, an AMD Radeon 9173 PCI-e graphics card in the extended chassis, and a 64GB SSD drive. The GPU environment that I used for this article consisted of a Wyse VDI client, a NVIDIA GPU, and a VMware Horizon virtual desktop running on a local server. This allows graphics commands to be passed directly to the GPU without first having to be translated by the hypervisor.
#VMWARE HORIZON VIEW CLIENT DUAL MONITOR DRIVER#
In order to use it, you must first install a vSphere Installation Bundle (VIB) on the ESXi host and a vendor driver on the virtual desktops. VMware Horizon has various technologies to allow GPUs to be used by virtual desktops, the most common of which being Virtual Shared Passthrough Graphics Acceleration, which is what I used when I wrote this article.
#VMWARE HORIZON VIEW CLIENT DUAL MONITOR HOW TO#
Then, I will explain how to monitor GPU usage using the ControlUp Console and tell you about a couple of gotchas that I discovered when I first tried to use ControlUp with GPU-enabled desktops. In this article, I will give a brief overview of using GPUs in virtual desktops and the setup that I used with my GPU. As these cards are an expensive and scarce resource, they must be monitored to ensure that they are being used as efficiently as possible. GPUs can either be dedicated to a specific virtual desktop or shared between multiple desktops, with shared cards being the most popular option. Fortunately, modern virtual desktop infrastructures (VDI), such as VMware Horizon, support virtual desktops with graphic cards. Virtual desktops are becoming more common in firms within industries like engineering, medical, and entertainment, where users view and process visual images or video – and need the power of a graphics processing unit (GPU) to accomplish their daily tasks. Share: Twitter Facebook LinkedIn Introduction