Tag: NVIDIA GRID K1

NVIDIA GRID vGPU 352.83-354.80

NVIDIA GRID – vGPU 352.83-354.80

Hi All

Its time to update your NVIDIA GRID K1, K2, M6, M60 environment.

NVIDIA have released new drivers that supports Windows 10 + fix several bugs.

If you want to test Server 2016 then the new Windows 10 drivers works, I have just tried and they work but they are not “certified” so test this with your own risk, please. Always test this in a test environment and this is not for production environments, unless you want to be early innovators 😉

#HINT – Windows 10 is not supported on Citrix XenServer 6.2 only on Citrix XenServer 6.5.
## HINT – Linux drivers are only available with Tesla M6, M60.

Whats new in vGPU 352.83-354.80

NVIDIA have released a new version of vGPU 352.83-354.80 for NVIDIA GRID 1.0 (K1, K2) GRID 2.0 Tesla M6 and Tesla M60 platform.

Included in this release is

NVIDIA GRID Virtual GPU Manager versions 352.83 for Citrix XenServer 6.5 SP1
NVIDIA GRID Virtual GPU Manager versions 352.83 for Citrix XenServer 6.2 SP1 with hotfixes XS62ESP1009 and XS62ESP1011
NVIDIA GRID Virtual GPU Manager version 352.83 for VMware vSphere 6.0 Hypervisor (ESXi)
NVIDIA Windows drivers for vGPU version 354.80
NVIDIA Linux drivers for vGPU version 352.83.

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

Update existing vGPU GRID Manager (Hypervisor)

GRID vGPU Manager 352.83 upgrade for Citrix XenServer 6.2

If you have a NVIDIA GRID K1, K2 vGPU GRID manager installed in Citrix XenServer. Upgrade with below methodology:

Methodology 1 – the manual way “No GUI”

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

If you have NVIDIA GRID K1 / K2

[root@localhost ~]# rpm -Uv NVIDIA-vGPU-kepler-xenserver-6.2-352.83.i386.rpm 
Preparing packages for installation...

If you have NVIDIA GRID TESLA M6 / M60

[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-6.2-352.83.i386.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

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 352.83, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 352.83 for Citrix XenServer 6.5

If you have a NVIDIA GRID K1, K2, M6, M60 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 K1 / K2

[root@localhost ~]# rpm -Uv NVIDIA-vGPU-kepler-xenserver-6.5-352.83.x86_64.rpm 
Preparing packages for installation...

If you have NVIDIA GRID TESLA M6 / M60

[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-6.5-352.83.x86_64.rpm 
Preparing packages for installation...

[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-352.83.x86_64-supplemental-pack.tar.bz2 ”

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

“NVIDIA-vGPU-xenserver-6.5-352.83.x86_64-supplemental-pack.tar.bz2 ”

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

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

GRID vGPU Manager 352.83 for VMware vSphere 6.x

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

To uninstall the currently installed VIB:

Stop all virtual machines using 3D acceleration.
Place the ESXi host into Maintenance mode.
Open a command prompt on the ESXi host.
Stop the xorg service by running the command:/etc/init.d/xorg stop
Remove the NVIDIA VMkernel driver by running the command:vmkload_mod -u nvidia
Identify the NVIDIA VIB name by running this command:esxcli software vib list | grep NVIDIA
Remove the VIB by running the command:esxcli software vib remove -n nameofNVIDIAVIBYou can now install a new NVIDIA GPU VIB
Use the esxcli command to install the vGPU Manager package:

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

[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-kepler-VMware_ESXi_6.0_Host_Driver_352.83-1OEM.600.0.0.2494585.vib

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

[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-VMware_ESXi_6.0_Host_Driver_352.83-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

Check driver version is 352.83, 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.

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 🙂

New driver functionality with 354.80

354.80_grid_win8_win7_64bit_international.exe
354.80_grid_win8_win7_international.exe
354.80_grid_win10_64bit_international.exe
354.80_grid_win10_international.exe
NVIDIA-Linux-x86_64-352.83-grid.run

#1 Linux driver is not available with Citrix XenServer 6.2 or 6.5 and ESX for K1/K2. This is only available with GRID vGPU for M60

Linux support in only available with GRID Tesla M6 / M60

GRID vGPU with Linux guest VMs is supported on Tesla M60 and M6, with the following distributions:

Red Hat Enterprise Linux 6.6, 7
CentOS 6.6, 7
Ubuntu 12.04, 14.04 LTS

Source

GRID K1/K2 – sources

Download vGPU 352.83-354.80 for XenServer 6.2 for GRID K1 / K2 her

Download vGPU 352.83-354.80 for XenServer 6.5 for GRID K1 / K2 her

Download vGPU 352.83-354.80 for vSphere 6 for GRID K1 / K2 here

Tesla M6/M60 – sources

vGPU Grid Manager + Drivers are only available to customers and NVIDIA NPN partners.

Download if you are a NPN partner

Download if you are a GRID 2.0 customer

vGPU 352.83-354.80 for XenServer 6.2 for Tesla M6 / M60

vGPU 352.83-354.80 for XenServer 6.5 for Tesla M6 / M60

vGPU 352.83-354.80 for vSphere 6 for Tesla M6 / M60

For more information about the update from NVIDIA GRID – vGPU 352.83-354.80 contact me.

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

NVIDIA GRID 2.0 integrated in Microsoft Azure

At Microsoft Azurecon 2015, NVIDIA announced that Microsoft will offer NVIDIA GPU-enabled professional graphics applications and accelerated computing capabilities to customers worldwide through its cloud platform, Microsoft Azure.

Deploying the latest version of NVIDIA GRID^™ in its new N-Series virtual machine offering, Azure is the first cloud computing platform to provide GRID 2.0 virtualized graphics for enterprise customers.

For the first time, businesses will have the ability to deploy NVIDIA Quadro® grade professional graphics applications and accelerated computing on-premises, in the cloud through Azure, or via a hybrid of the two using both Windows and Linux virtual machines. Azure will also offer customers supercomputing-class performance, with the addition of the Tesla Accelerated Computing Platform’s flagship Tesla® K80 GPU accelerators, for the most computationally demanding data center and high performance computing (HPC) applications.

Unprecedented Virtualized Graphics Performance

With NVIDIA GRID enterprises can deliver graphics intensive applications from companies such as Autodesk, ESRI and Siemens from the cloud to their users. Announced last month, NVIDIA GRID 2.0 provides the NVIDIA Quadro GPU driver support, features and performance that graphics-intensive applications require, as well as other enhancements including double the application performance of the previous generation of GRID GPUs and Linux OS support.

Supercomputing in the Cloud

The Tesla Accelerated Computing Platform is designed from the ground up for power-efficient, high performance computing (HPC), computational science, supercomputing, data analytics and deep learning applications.

Powering some of the world’s highest performance supercomputers, the Tesla platform delivers dramatically higher performance and energy efficiency than a CPU-only approach and unprecedented application throughput in the data center.

By deploying the Tesla K80 GPU accelerator in its N-Series virtual machines, Azure dramatically expands access to supercomputing-class performance, enabling enterprises worldwide to accelerate their most demanding workloads, without requiring them to invest in, build and maintain dedicated computing resources.

Azure N-series, a new family of Azure Virtual Machines

Available in preview within the next few months, the N-series will feature the NVIDIA Tesla Accelerated Computing Platform as well as NVIDIA GRID 2.0 technology, providing the highest-end graphics support available in the cloud today.

Source

NVIDIA

Microsoft

NVIDIA GRID 2.0

NVIDIA have released the next generation of GRID 2.0. GRID 2.0 is based on the Maxwell architecture and the GRID 1.0 (K1/K2) was based on the Kepler architecture. I have been working with the GRID 1.0 technology since 2012 and it have matured alot in its 2 years of history. When the K1/K2 was released they was first working with GPU pass-through and then vGPU got introduced and you could virtualize the GPUs and increase density, which people wanted. Citrix was with their hypervisor the first company that supported NVIDIA GRID 1.0 and they was also the first company integrating vGPU into their Citrix Studio, so companies could easier provisioning machines with either MCS technology or PVS technology. VMware supported GRID 1.0 vGPU technology in 2015 in their hypervisor VMware vSphere 6.0 and fully integrated with their EUC stack VMware View, so companies can fully provisioning machines. The great thing about GRID 2.0 is that there is no need for a conversation when to choose either a K1 or a K2, if you required GPU compute or GPU framebuffer, M60 are being added to the tope end of the range and bringing 2x the performance, and if you have bladeserver’s, you can add the powerfull vGPU technology into the bladeserver’s with the M6.

Please notice that M6 will 0nly be supporting newer architecture of vendors not old platforms.

Maxwell architecture

Maxwell architecture is the new architecture of GPUs and a powerful GPU you might know is the Titan X

New GPUs GRID 2.0 and specifications

In GRID 2.0 NVIDIA now have a GPU for blade servers a MXM single socket, High-end GPU called M6

In GRID 2.0 NVIDIA replaces K1/K2 with the new PCIe 3.0 Dual Socket, Dual High-end GPU called M60
The M60 delivers 4096 CUDA or compute and 16GB GDDR5 memory/framebuffer

The M60 has 6x the h.264 encoders of the K2, and also Maxwell supports 4:4:4 chroma sub sampling, which is great news for encoders.

Certified GRID 2.0 servers

Click the link to see which servers are certified for M60 and M6
http://www.nvidia.com/object/grid-certified-servers.html

M6 have following servers supported:

M60 have following servers supported:

vGPU software editions and license

NVIDIA GRID 2.0 software is available in three editions that deliver accelerated virtual desktops to support the needs of your users. These editions include Virtual PC, Virtual Workstation, and Virtual Workstation Extended. GRID perpetual licenses are sold by Concurrent User (CCU).

NVIDIA GRID 2.0 (CCU) stands for ConCurrent User. So basically, per running VM as regardless of whether the user is connected to the VM or not, the VM is connected to the GPU and so consumes a license

NVIDIA GRID 2.0 software is much more than a “driver”. While the software package does include a guest driver for Windows and Linux, it also includes the NVIDIA GRID vGPU manager for VMware vSphere and Citrix XenServer, as well as the license server and M6/M60 mode switching utility.

NVIDIA Tesla M6 and M60 profiles are specific to the M6 and M60. There will be similar profiles as to what NVIDIA had on K1 and K2 (512 MB through 4 GB), all with twice the number of users on M6/ M60 compared to K1/K2. Plus, there is an additional 8 GB profile on M6/M60 which also adds support for CUDA, which wasn’t available on K1/K2.

NVIDIA GRID 2.0 is Maxwell only. If you are an existing customer K1/K2 are unchanged and will remain as a parallel option.

The NVIDIA GRID 2.0 solution

Summary

GA of NVIDIA GRID 2.0 (M60 and M6) will be 15 September 2015.

To get NVIDIA GRID 2.0 if you are a Citrix customer you need:
Server hardware that supports NVIDIA GRID 2.0 +NVIDIA GPU M60 or M6 + NVIDIA vGPU Software license + Citrix XenDesktop or XenApp License (XenServer is included in XD/XA licenses)

To get NVIDIA GRID 2.0 if you are a VMware customer you need:
Server hardware that supports NVIDIA GRID 2.0 +NVIDIA GPU M60 or M6 + NVIDIA vGPU Software license + VMware Horizon license (Horizon includes vSphere for Desktop)

If you are a Citrix customer that wants to run on VMware vSphere you need:

Server hardware that supports NVIDIA GRID 2.0 + NVIDIA GPU M60 or M6 + NVIDIA vGPU Software license + Citrix XenDesktop or XenApp License + VMware vSphere Enterprise Plus license or vSphere for Desktop license

Source

NVIDIA GRID Test Drive

NVIDIA GRID Website

NVIDIA GRID News

NVIDIA GRID YouTube Channel

Questions? Ask on our Forums

NVIDIA GRID on LinkedIn

Follow NVIDIAGRID on Twitter

Citrix License FAQ regarding vGPU

Vmware License FAQ regarding vGPU

Lakeside Case Study – sizing NVIDIA GRID vGPU

Hi all

I am very proud to share the results of the work I did with my friend and coworker Magnar Johnsen from FirstPoint. We have been developing for a long time a smart new way of analyzing data (iOPS, CPU, Memory, GPU, Latency..) and different pieces of software was evaluated and Lakeside Software was the product we decided to go with and both our companies Poppelgaard.com and Firstpoint who are a Lakeside partner so we are legit to make assessments for clients using Lakeside Software. Below article helps you if you are about to size a NVIDIA GRID vGPU solution using either Citrix XenServer or VMware vSphere. If you have been at NVIDIA GTC, Citrix Synergy, BriForum, E2EVC or seen me talking at a Citrix User Group you might have seen the results of the work we did, thats changing on how we think applications are impacting that requires a GPU.

Magnar and I go way back.

Magnar and I have a long past with remote graphics and when we put our minds together we create something that is beautiful. Last year at Citrix Synergy audience could see how people could virtualize 3d remote graphics from Virtual Reality solution using Oculus Rift “Facebook” from the cloud. This was showed for the first time for audience and Citrix loved the idea and redesigned their exhibit about HDX 3D Pro next to FrameHawk, and sorry FrameHawk we stole all the attention with everybody wants to try the VR solution. The cool thing was VR was cool, but me and Magnar worked months “hard” to analyze the data we find at Aibel and we did very successful assessment and we shared the findings at Brian Madden BriForum in May 2014, just after Citrix Synergy, and the audience could for the first time learn the lessons we experienced and we could see applications behavior is not “just” what you might think or expect it to be. Analytics is the key to understand your app. Lets talk about why…

Lets dig into the case study we did at Aibel

Aibel is an industrial pioneer with a history dating back more than a century. With around 5,500 employees worldwide the company is a leading supplier of engineering services related to oil, gas and renewable energy.

Aibel is a huge user of desktop virtualisation technology and is currently delivering virtual desktops to around 4,500 users. The challenge was to work out what to do with the remaining 1500 CAD/CAM workstations where graphics intensive modelling of 3D designs tied them to powerful physical workstations.

With projects occurring at the eight Aibel locations in Norway as well as at the Aibel offices in Thailand and Singapore the amount of data flowing across the WAN was increasing and becoming unwieldy. Large engineering models needed to be accessed on location and shared with engineers and designers in all Aibel office locations.

Virtualisation was seen as the solution to these issues but the challenge was how to virtualise graphics intensive workloads without impacting user experience or drive uneconomic datacentre specifications.

Partner Expertise

Firstpoint AS, a trusted Citrix Gold partner and virtualisation specialists, were brought in to advise Aibel on how to best virtualise this tricky user group.

They teamed up with Thomas Poppelgaard, an independent expert in virtualisation and GPU technologies and together they started an initial survey of Aibel’s situation.

GPU Acceleration Approach

It became quickly clear that the only way to successfully virtualise the 3D graphics workstations in an economically viable fashion was to deploy GPU acceleration technology in the datacentre. NVIDIA’s GRID cards would allow dedicated and shared GPU accelerators to be placed in the datacentre to be used by virtual desktops offloading server CPUs and removing user experience impact for other virtual desktop users.

The Challenge

Having identified the technology approach the challenge now was to work out how to size the workload of these 1500 users and design a solution that would deliver user experience at least as good as their current physical desktop experience. In order to do that the team needed to work out:

What graphics applications are in use today
Who is using which applications and workstations
What GPU processor power is being consumed today by application, user and workstationPoppelgaard.com and FirstPoint brought in Lakeside Software’s SysTrack to do this job. Using SysTrack’s granular data collection model they could model a complete picture of application and GPU workload across all the users and workstations in use at Aibel today.

The Outcome

Using SysTrack the team has been able to build a complete inventory of the existing application and workstation estate and user behaviour. Using these analytics and SysTrack technologies a detailed specification and design for the future NVIDIA GRID based desktop virtualisation infrastructure has been created. Aibel is able to trust this design

as it is completely based on observed data captured from their existing estate and modelled using industry leading technologies from Lakeside and NVIDIA to create the optimal solution for Aibel’s situation. Key in any design is to not over provision the solution and thereby inflate the cost of the solution. On the other hand under provisioning will lead to a poor user experience and potential project failure. SysTrack ensures the right data is used to make the right decision for the future estate.

The assessment was primarily executed to understand Aibel engineers CAD applications such as Aveva PDMS, Bentley Microstation, etc. Shown below is a summary of average GPU usage for 1500 physical machines which revealed surprisingly that internet browsers are very GPU intensive compared to other applications.

Another benefit of leveraging SysTrack was the SysTrack MarketPlace report that had been co-authored by Lakeside and NVIDIA which allowed the team to convert all the data collected into accurate sizing of the number of NVIDIA GRID cards by model number required to offload the GPU workload.

The output from SysTrack also showed how GPUs were being used across the existing estate and how hard they were being utilised. Using jointly authored Lakeside/NVIDIA reports this data was then used to calculate estimated vGPU profiles.

Source

VMware Horizon View 6.1.1

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.

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