NVIDIA GRID 5.0 released (384.73/385.41)

Written by Thomas Poppelgaard. Posted in CentOS, Citrix, dVGA, GRID, Horizon, Linux, Maxwell, Microsoft, NVENC, NVIDIA, Pascal, Quadro, RDS, RemoteFX, RHEL, Tesla, Ubuntu, vGPU, VMware, vSphere, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008R2, Windows Server 2012R2, Windows Server 2016

nvidiagrid

Hi All

Its time to update your NVIDIA TESLA M6, M10, M60 environment or start using the new TESLA P4, P6, P40, P100 with GRID 5.0.

NVIDIA have released new drivers for NVIDIA GRID 5.0 for September 2017.

This release includes the following software:

  • NVIDIA GRID Virtual GPU Manager version 384.73 for the Citrix XenServer, VMware vSphere, Huawei UVP
  • NVIDIA Windows driver version 385.41
  • NVIDIA Linux driver version 384.73

New in this Release:

  • Support for GPUs based on the NVIDIA® Pascal™ architecture
  • Compute mode support for GRID vGPU and pass-through GPU on GPUs based on the NVIDIA Pascal architecture
  • New GRID vGPU schedulers for GPUs based on the NVIDIA Pascal architecture
  • Support for NVML and nvidia-smi on 32-Bit Windows VMs
  • Application-level monitoring of GRID vGPU engine utilization
  • Encoder session monitoring
  • Support for NVENC on Linux GRID vGPUs
  • Removal of support for GRID K1 and GRID K2 GPUs
  • Software enforcement of licensing requirements
  • Miscellaneous bug fixes

Supported NVIDIA GPUs with GRID 5.0

  • Tesla M6
  • Tesla M10
  • Tesla M60
  • Tesla P4
  • Tesla P6
  • Tesla P40
  • Tesla P100

Supported Hypervisors with GRID 5.0

  • Citrix XenServer
    Citrix XenServer 7.0, 7.1, 7.2 (supported with Tesla M6, M10, M60, P4, P6, P40, P100)
    Citrix XenServer 6.5 (supported with Tesla M6, M10, M60)
  • VMware vSphere
    VMware vSphere 6.5 (supported with Tesla M6, M10, M60, P4, P6, P40, P100)
    Vmware vSphere 6.0 update3, update 2, update 1, RTM b2494585 (supported with Tesla M6, M10, M60, P4, P6, P40, P100)
    VMware vSphere 5.5 (supported with Tesla M6,M10,M60)
  • Microsoft Hyper-V 2016
    Microsoft Windows Server 2016 with Hyper-V role (supported with Tesla M6, M10, M60, P4, P6, P40, P100)
    note: Microsoft Windows Server with Hyper-V role supports GPU pass-through over Microsoft Virtual PCI bus. This bus is supported through paravirtualized drivers. 
  • Red Hat Enterprise Linux with KVM
    Red Hat Enterprise Linux with KVM 7.2, 7.3 (supported with Tesla M6, M10, M60, P4, P6, P40, P100)
    Red Hat Enterprise Linux with KVM 7.0, 7.1 (supported with Tesla M6,M10,M60)
  • Huawei UVP
    Huawei UVP RC520 (supported with Tesla M60)

Whats new in GRID 5.0 – 384.73-385.41

NVIDIA have released a new version of GRID 5.0 – 384.73-385.41 for NVIDIA GRID  (Tesla M6, M10, M60, P4, P6, P40, P100 platform)

Included in this release is

  • NVIDIA GRID Virtual GPU Manager versions 384.73 for Citrix XenServer 6.5 SP1
  • NVIDIA GRID Virtual GPU Manager versions 384.73 for Citrix XenServer 7
  • NVIDIA GRID Virtual GPU Manager versions 384.73 for Citrix XenServer 7.1
  • NVIDIA GRID Virtual GPU Manager version 384.73 for VMware vSphere 6.0 Hypervisor (ESXi)
  • NVIDIA GRID Virtual GPU Manager version 384.73 for VMware vSphere 6.5 Hypervisor (ESXi)
  • NVIDIA Windows drivers for vGPU version 385.41
  • NVIDIA Linux drivers for vGPU version 384.73.

Important:

The GRID vGPU Manager and Windows guest VM drivers must be installed together. Older VM drivers will not function correctly with this release of GRID vGPU Manager. Similarly, older GRID vGPU Managers will not function correctly with this release of Windows guest drivers

Windows Guest OS support in vGPU 385.41

GRID vGPU 385.41 supports following Windows release as a guest OS

  • Microsoft Windowss 7 (32/64bit)
  • Microsoft Windows 8 (32/64bit)
  • Microsoft Windows 8.1 (32/64bit)
  • Microsoft Windows 10 (32/64bit)
  • Microsoft Windows Server 2008R2
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2016

Linux Guest OS support in vGPU 384.73

GRID vGPU 384.73 supports following Linux distributions as a guest OS only on supported Tesla GPUs

  • Red Hat Enterprise Linux 7.0-7.3
  • CentOS 7.0-7.3
  • Ubuntu 16.04 LTS
  • Ubuntu 14.04 LTS

Important driver notes to GRID 5.0

  • In pass-through mode, GPUs based on the Pascal architecture support only 64-bit guest operating systems. No 32-bit guest operating systems are supported in pass-through mode for these GPUs.
  • ESXi 6.0 Update 3 is required for pass-through mode on GPUs based on the Pascal architecture.
  • Windows 7 and Windows Server 2008 R2 are not supported in pass-through mode on GPUs based on the Pascal architecture.
  • Only Tesla M6 is supported as the primary display device in a bare-metal deployment.
  • 32-bit Windows 10 is supported only on Tesla M6, Tesla M10, and Tesla M60 GPUs.
  • Red Hat Enterprise Linux with KVM 7.0 and 7.1 are supported only on Tesla M6, Tesla M10, and Tesla M60 GPUs.
  • Red Hat Enterprise Linux with KVM supports Windows guest operating systems only under specific Red Hat subscription programs. For details, see Certified guest operating systems for Red Hat Enterprise Linux with KVM.
  • Windows 7, Windows Server 2008 R2, 32-bit Windows 10, and 32-bit Windows 8.1 are supported only on Tesla M6, Tesla M10, and Tesla M60 GPUs.

Guide – Update existing vGPU GRID Manager (Hypervisor)


 

GRID vGPU Manager 384.73 for Citrix XenServer 6.5

If you have a NVIDIA GRID M6, M10, M60, P4, P6, P40, P100 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 6.5, use the rpm -U command to upgrade:

If you have NVIDIA GRID TESLA M6 / M10 / M60 / P4 / P6 / P40 / P100
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-6.5-384.73.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

If you have NVIDIA GRID K1 / K2 select following file:

“NVIDIA-vGPU-kepler-xenserver-6.5-384.73.x86_64.iso ”

If you have NVIDIA GRID M10/ M6/M60 select following file:

“NVIDIA-vGPU-xenserver-6.5-384.73.x86_64.iso ”

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 384.73 for Citrix XenServer 7

If you have a NVIDIA GRID M6, M10, M60, P4, P6, P40, P100 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 7, use the rpm -U command to upgrade:

If you have NVIDIA GRID TESLA M6 / M10 / M60 / P4 / P6 / P40 / P100
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-7.0-384.73.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

 

If you have NVIDIA GRID M6/M10/M60/P4/P6/P40/P100 select following file:

“NVIDIA-vGPU-xenserver-7.0-384.73.x86_64.iso ”

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 384.73, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 384.73 for Citrix XenServer 7.1, 7.2

If you have a NVIDIA GRID M6, M10, M60, P4, P6, P40, P100 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 7.1, use the rpm -U command to upgrade:

If you have NVIDIA GRID TESLA M6 / M10 / M60 / P4 / P6 / P40 / P100
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-7.1-384.73.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

 

If you have NVIDIA GRID M6/ M10/M60/P4/P6/P40/P100 select following file:

“NVIDIA-vGPU-xenserver-7.1-384.73.x86_64.iso ” if XenServer 7.1

“NVIDIA-vGPU-xenserver-7.2-384.73.x86_64.iso ” if XenServer 7.2

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 384.73, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 384.73 for VMware vSphere 6.0

To update the NVIDIA GPU VIB, you must uninstall the currently installed VIB and install the new VIB.

To uninstall the currently installed VIB:

  1. Stop all virtual machines using 3D acceleration.
  2. Place the ESXi host into Maintenance mode.
  3. Open a command prompt on the ESXi host.
  4. Stop the xorg service by running the command:/etc/init.d/xorg stop
  5. Remove the NVIDIA VMkernel driver by running the command:vmkload_mod -u nvidia
  6. Identify the NVIDIA VIB name by running this command:esxcli software vib list | grep NVIDIA
  7. Remove the VIB by running the command:esxcli software vib remove -n nameofNVIDIAVIBYou can now install a new NVIDIA GPU VIB
  8. Use the esxcli command to install the vGPU Manager package:
If you have NVIDIA GRID TESLA M6 / M10 / M60 / P4 / P6 / P40 / P100 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-VMware_ESXi_6.0_Host_Driver_384.73-1OEM.600.0.0.2494585.vib

After the ESXi host has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

[root@lesxi ~]# vmkload_mod -l | grep nvidia 
Preparing packages for installation...

Validate

run nvidia-smi

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 384.73, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 384.73 for VMware vSphere 6.5

To update the NVIDIA GPU VIB, you must uninstall the currently installed VIB and install the new VIB.

To uninstall the currently installed VIB:

  1. Stop all virtual machines using 3D acceleration.
  2. Place the ESXi host into Maintenance mode.
  3. Open a command prompt on the ESXi host.
  4. Stop the xorg service by running the command:/etc/init.d/xorg stop
  5. Remove the NVIDIA VMkernel driver by running the command:vmkload_mod -u nvidia
  6. Identify the NVIDIA VIB name by running this command:esxcli software vib list | grep NVIDIA
  7. Remove the VIB by running the command:esxcli software vib remove -n nameofNVIDIAVIBYou can now install a new NVIDIA GPU VIB
  8. Use the esxcli command to install the vGPU Manager package:
If you have NVIDIA GRID TESLA M6 / M10 / M60 / P4 / P6 / P40 / P100 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-VMware_ESXi_6.5_Host_Driver_384.73-1OEM.650.0.0.2494585.vib

After the ESXi host has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

[root@lesxi ~]# vmkload_mod -l | grep nvidia 
Preparing packages for installation...

Validate

run nvidia-smi

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 384.73 if it is then your host is ready for GPU awesomeness and make your VM rock.

Update existing vGPU Driver (Virtual Machine)

When the hypervisor vGPU GRID manager is updated next is updating the Virtual Machines vGPU driver.

  • 385.41_grid_win8_win7_32bit_international.exe
  • 385.41_grid_win8_win7_server2012R2_server2008R2_64bit_international.exe
  • 385.41_grid_win10_32bit_international.exe
  • 385.41_grid_win10_server2016_64bit_international.exe
  • NVIDIA-Linux-x86_64-384.73-grid.run (only available with M10/M6/M60)

The vGPU driver for Windows 7, 8, 8.1, 10 is available with NVIDIA GRID vGPU download. This is available for both M6/M10/M60/P4/P6/P40/P100

The vGPU driver for Linux is only available for vGPU with following Tesla GPU M10/M6/M60

Update your Golden Images and reprovisioning the new virtual machines with updated vGPU drivers, if you have stateless machines update vGPU drivers on each.

#HINT – Express upgrade of drivers is the recommended option according to the setup. If you use the “Custom” option, you will have the option to do a “clean” installation. The downside of the “clean installation” is that it will remove all profiles and custom settings. The pro of using the clean installation option is that it will reinstall the complete driver, meaning that there will be no old driver files left on the system. I most of the time recommends using a “Clean” installation to keep it vanilla 🙂

#HINT (Citrix XenDesktop 7.6-7.11 customers)

The NVIDIA GRID API provides direct access to the frame buffer of the GPU, providing the fastest possible frame rate for a smooth and interactive user experience. If you install NVIDIA drivers before you install a VDA with HDX 3D Pro, NVIDIA GRID is enabled by default.

To enable NVIDIA GRID on a VM, disable Microsoft Basic Display Adapter from the Device Manager. Run the following command and then restart the VDA: Montereyenable.exe -enable -noreset

If you install NVIDIA drivers after you install a VDA with HDX 3D Pro, NVIDIA GRID is disabled. Enable NVIDIA GRID by using the Montereyenable tool provided by NVIDIA.

To disable NVIDIA GRID, run the following command and then restart the VDA: Montereyenable.exe -disable -noreset

#HINT (Citrix XenDesktop 7.12/7.13/7.14/7.15 customers)

The NVIDIA GRID API provides direct access to the frame buffer of the GPU, providing the fastest possible frame rate for a smooth and interactive user experience. If you install NVIDIA drivers before you install a VDA with HDX 3D Pro, NVIDIA GRID is enabled by default.

To enable NVIDIA GRID on a VM, disable Microsoft Basic Display Adapter from the Device Manager. Run the following command and then restart the VDA: NVFBCEnable.exe -enable -noreset

If you install NVIDIA drivers after you install a VDA with HDX 3D Pro, NVIDIA GRID is disabled. Enable NVIDIA GRID by using the NVFBCEnable tool provided by NVIDIA.

To disable NVIDIA GRID, run the following command and then restart the VDA: NVFBCEnable.exe -disable -noreset

 

docs.nvidia.com

NVIDIA have done a great job creating a documentation portal for all their products including NVIDIA GRID.

the url is https://docs.nvidia.com

Source

NVIDIA Virtual GPU Software Documentation

https://docs.nvidia.com/grid/index.html

NVIDIA Virtual GPU Software Supported Products

NVIDIA Virtual GPU Software Quick Start Guide

Tesla M6/M10/M60/P4/P6/P40/P100 – sources

vGPU Grid Manager + Drivers are only available to customers and NVIDIA NPN partners for M6/M10/M60/P4/P6/P40/P100

Download if you are a NPN partner

Download if you are a GRID M6, M10, M60, P4, P6, P40, P100 customer

 

VMware Horizon View 6.1.1

Written by Thomas Poppelgaard. Posted in CentOS, dVGA, GRID, Linux, NeoKylin, NVIDIA, RHEL, Ubuntu, vSphere

VMware Horizon View 6.1.1 has been released

This is my first blogpost about VMware EUC product and VMware is investing alot in end user computing space and making this GPU enabled.

In release 6.1.1 VMware have enabled GPU pass-through (vDGA) to Linux virtual machines that run on following OS (Ubuntu, RHEL, CentOS, or NeoKylin) this technology can be used with NVIDIA GRID

This means with 1 physically NVIDIA GRID K1 you could have 4 linux VMs with GPU pass-through,k cause a K1 have 4 physically GPUs. With 1 physically NVIDIA GRID K2, you can have 2 linux VMs with GPU pass-through, cause a K2 have 2 physically GPUs

Below gives you an understand which GPU methodology I am talking about with what you can do with vDGA.
FYI – VMware View 6.1.1. supports NVIDIA GRID vGPU but only with Windows OS.
KUDUS goes to TeamRGE, for using their graphics.

vDGA_GPU_pass-through

 

vDGA_GPU_pass-through_2

What’s New in This Release of VMware Horizon View 6.1.1

VMware Horizon View 6.1.1 resolves known issues in previous releases and provides the following new features and enhancements:

  • Client Drive Redirection
    Users can share folders and drives on their local client systems with remote desktops and applications. Client Drive Redirection is supported on VDI desktops that run on single-user machines and on RDS desktops and applications. The feature is supported on Windows clients and, as a Tech Preview, on Mac OS X clients.
  • Horizon 6 for Linux Desktops
    You can now deploy Horizon 6 desktops on Linux virtual machines. With the View Agent for Linux installer, you can set up parent virtual machines or templates that run on Ubuntu, RHEL, CentOS, or NeoKylin and deploy Linux-based VDI desktop pools in View Administrator. You can configure Linux virtual machines to use vDGA to support 3D graphics applications running on NVIDIA GRID GPU cards. Some features such as SSO, automated provisioning, and local device redirection are not supported in this release. For details, see Setting Up Horizon 6 for Linux Desktops guide.
  • Serial Port Redirection
    With serial port redirection, users can redirect locally connected serial (COM) ports such as built-in RS232 ports or USB to Serial adapters. Devices such as printers, bar code readers, and other serial devices can be connected to these ports and used in the remote desktops.
  • Support for Windows Media Multimedia Redirection (MMR) for RDS Desktops
    Windows Media MMR is now supported for videos playing on RDS desktops. In past releases, this feature was supported only on VDI desktops that run on single-user machines. For details about supported desktops, see see System Requirements for Windows Media MMR in the Setting Up Desktop and Application Pools in View guide.
  • HTML Access Support for Hosted Apps
    Users can now connect to Hosted Apps from HTML Access Web clients. To take advantage of this feature, you must download and install a separate HTML Access installer from the Horizon 6 version 6.1.1 download page. For details, see To use HTML Access with Hosted Apps.

Source

VMware Horizon 6.1.1 release notes

 

Citrix technology professional – CTP, and Microsoft Most Valuable Professional MVP, Thomas Poppelgaard provides professional services. Write to me on my email thomas@poppelgaard.com or call on my cell +45 53540356

VMware officially supports vDGA (GPU Pass-through) in vSphere/View

Written by Thomas Poppelgaard. Posted in Citrix, dVGA, GRID, NVIDIA, View, VMware, XenServer

At VMworld in Barcelona, October 15th 2013, Vmware officially now support vDGA in vSphere 5.5. vDGA is a graphics acceleration capability that is offered by VMware with NVIDIA GPUs and is enabled by Horizon View 5.3 for delivering high-end Workstation Class 3D Graphics for use cases where a discrete GPU is needed.

The vDGA graphics adapters are installed in the underlying vSphere host and are then assigned to virtual desktops using VMware DirectPath I/O. Assigning a discrete NVIDIA GPU to the virtual Machine dedicates the entire GPU to that desktop and enables for CUDA and OpenCL compute.

With vDGA officially supported you can also used with Citrix XenDesktop or other technologies that requires a dedicated GPU in a Virtual Machine.

Bellow graphics shows how you now with either Vmware or Citrix can build a virtual desktop with GPU pass-through on either vSphere with View or vSphere with XenDesktop or XenServer with XenDesktop as a technology stack.

virtualization_of_GPU_vmware-citrix

GPU pass-through is now fully supported on View 5.3 and Citrix also have support for this in XenDesktop. Summary it means both Vmware and Citrix are now fully supported with GPU Passthrough with NVIDIA certification program, see below.

citrix_and_vmware_gpu_pass-through2

Source

NVIDIA

Reviewer’s Guides for HDX 3D Pro Graphics, on both XenServer and vSphere

Written by Thomas Poppelgaard. Posted in Citrix, dVGA, GRID, HDX 3D, HDX 3D Pro, NVIDIA, sVGA, vGPU, VMware, vSphere, XenApp, XenDesktop

Hi All

A good friend of mine from Citrix, Mayunk Jain & Pushpal have created these reviewers guide for Citrix XenDesktop 7 HDX 3D Pro.

The guides will help you how to either configure GPU pass-through on XenServer or VMware vSphere with Citrix XenDesktop 7 HDX 3D Pro.

He is using following hardware: Dell R720 with NVIDIA GRID K1 and K2, just like I have been using in many of the articles and videos I have shared to the community, and solutions I have build at customers.

In the first guide, they cover physical installation of GPU cards in a server, and how to enable GPU pass-through in XenServer 6.2. High-end graphics apps running on Windows Server VMs can share GPU among multiple user-sessions when delivered using XenDesktop 7 Apps or XenApp 6.5 FP2.

In part two, they see a similar use case on VMware vSphere platform. It describes the steps to enable GPU pass-through feature in vSphere 5.1, called virtual Dedicated Graphics Acceleration (vDGA). You learn how to set up XenDesktop 7 Apps and access 3D graphics using Citrix Receiver.

Part three walks through the steps to deliver virtualized access to a class of high performance graphics-intensive applications, which haven’t previously been considered virtualization friendly. Known as the vGPU feature in XenServer, this will be released as a tech preview later this month.

Part four looks at a different use-case on VMware vSphere, where the GPU is shared between several desktop VMs using software emulation. Called virtual Shared Graphics Acceleration (vSGA), this feature allows desktops published in XenDesktop 7 to deliver hardware-accelerated graphics apps on a vSphere platform.

HDX 3D Comparison (GPU pass-through vs vGPU, sVGA, dVGA)

The table above summarizes at a high-level, the key differences between the XenServer and vSphere technologies.

HDX-3D-Comparison

 

Reviewers Guide for Delivering 3D Graphics

A 4-part series of easy to follow, step-by-step instructions that guide you to building a 3D enabled virtual app infrastructure using Nvidia GRID cards, compatible servers, XenServer and/or vSphere, with HDX 3D Pro feature in XenDesktop 7.

Reviewer’s Guide for Delivering 3D Graphics Apps: Part 1

Part 1 discusses the physical installation of Nvidia GRID GPU cards in compatible hardware, and enabling GPU pass-through in XenServer. Refer the guide for links to other parts in the series.

Reviewer’s Guide for Delivering 3D Graphics Apps: Part 2

Part 2 discusses the GPU pass-through feature in VMware vSphere, called vDGA. This allows XenDesktop 7 Apps to share a single GPU on vSphere platform, when running Windows Server RDS workloads. Refer the guide for links to other parts in the series.

Reviewer’s Guide for Delivering 3D Graphics Apps: Part 3

This is a placeholder for the vGPU guide on XenServer. It will be activated at the time of launching Tech Preview later this month. Refer article 12010 for the first part in the series

Reviewer’s Guide for Delivering 3D Graphics Apps: Part 4

Part 4 describes the steps to enable software-based GPU sharing in VMware vSphere, called vSGA. This allows graphics apps running on multiple Windows desktops to share a single GPU on vSphere platform, delivered using XenDesktop 7. Refer the guide for links to other parts in the series.

Source

Download Reviewer’s Guide for Delivering 3D Graphics Apps: Configure GPU pass-through Part 1 here

Download Reviewer’s Guide for Delivering 3D Graphics Apps: Configure vDGA – Part 2 here

Download Reviewer’s Guide for Delivering 3D Graphics Apps: Configure vGPU – Part 3 (Available in end of September 2013)

Download Reviewer’s Guide for Delivering 3D Graphics Apps: Configure sVGA – Part 4 here

Read the full blog from Mayunk at Citrix blogs

Recent Comments

Server 2016 Migration

|

Hello I wish to to share a comment here concerning you to definitely be able to inform you just how much i personally Loved this particular study. I have to elope in order to aTurkey Day time Supper but desired to leave ya an easy comment. We preserved you Same goes with be returning subsequent function to read more of yer quality articles. Keep up the quality work.

Server 2016 Migration

MarilynToush

|

This message is posted here using XRumer + XEvil 3.0
XEvil 3.0 is a revolutionary application that can bypass almost any anti-botnet protection.
Captcha Recognition Google, Facebook, Yandex, VKontakte, Captcha Com and over 8.4 million other types!
You read this – it means it works! 😉
Details on the official website of XEvil.Net, there is a free demo version.

Server 2016 Support

|

Wonderful website. A lot of useful info here. I am sending it to a few friends ans also sharing in delicious. And obviously, thanks for your sweat!

Server 2016 Support

Thomas Poppelgaard

|

Thanks Jose, I have corrected the map plus updated the map so 29 datacenters are now alive.

Jose Brenes

|

Your map of Australia is wrong. You have put the state of Victoria inside the West Australian state.