Skip to main content

Tag: Citrix XenServer 6.2

NVIDIA GRID vGPU 352.83-354.80

NVIDIA GRID update - 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...

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-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

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 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:

  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 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

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.

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.

thomas poppelgaard CTP & MVP

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

Citrix HDX 3D Pro beyond limits part 1

Citrix HDX 3D Pro beyond limits part 1

Hi All

This is a video blog post series I am creating to show you as an audience how powerful remote graphics is from Citrix & NVIDIA.
You are now able to work from anywhere, any time, any device. You just need an internet connection (Satellit, Edge/3G)

This video shows the user experience with Citrix XenDesktop 7.6 VDI workload (virtualized Windows 8.1 64bit) The workload have a NVIDIA GRID K2 vGPU K220Q GPU profile assigned.

The workload is running in a datacenter in EMEA and secured by Citrix Netscaler and SMS Passcode.

The end device that is used to connect to the Citrix workload is a Microsoft Surface Pro 3 using Windows 10 and Citrix Receiver 14.3

Video is recorded by Apple iPhone 6+

Microsoft Surface Pro 3 is connected using my Phones internet connetion which was at that time switching between “EDGE” and “3G”. Bandwidth was 300KB-5Mbit and latency is from 500MS-7000MS, jitter is not meassured.

Please notice this video is recorded on a boat sailing between Denmark and Sweden in Europe, this trip took place July 2015.

Purpose of this video:

Show the audience how powerful Citrix HDX 3D Pro is using NVIDIA GRID in extreme conditions with latency I have never tried it on and I was still able to interact realtime with computer graphics thats running securely in a datacenter in EMEA.

This technology is so powerful and can be used in critical conditions where an employee can access graphics, (2D, 3D) or even rich graphics such as browsers, viewers, office productivity, erp systems. Imagine an engineer on an Oil rig requires to see a critical component that requires to be changed and the data can be accesable connected to a datacenter thousands of kilometers away securely and remotely. This is the future of working, making you work on any device, any where, any place.

More about Citrix HDX 3D Pro
https://www.citrix.dk/products/xendes…

More about NVIDIA GRID
http://www.nvidia.com/object/grid-tec…

GPUperf2 – FREE Community tool
http://www.virtualexperience.no/sdm_d…

Used for realtime your GPU usage and remote protocol bandwidth usage

/poppelgaard

thomas poppelgaard CTP & MVP