NVIDIA GRID 2.0
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 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
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
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
NVIDIA GRID YouTube Channel
NVIDIA GRID on LinkedIn
Follow NVIDIAGRID on Twitter
Citrix License FAQ regarding vGPU
Vmware License FAQ regarding vGPU
Wow, NVIDIA is now making you pay for licenses to use this technology? Not sure why I didn’t see that coming. I mean withteh GRID 1.0 vGPUs, you never needed a license to use this with XenServer 6.x
Minor correction but not your fault – NVIDIA are currently listing Amulet Hotkey in the wrong section; we actually OEM the Dell PowerEdge M630 blade with the M6 module, not the M60. That’s 32 Xeon processors and 16 GRID cards in 10U.
Also a slight correction on the HP numbering; their support of the M6 is dependent on the expansion blade, which drags the blade density down to 8 in 10U. It’s a lot of GPUs in 10U but a very different GPU/CPU balance to the Dell platform. Otherwise a great write-up!
I was surprised and confused by what NVIDIA now appears to be stating about needing NVIDIA CCU licenses to use GRID 2.0 M6/M60 instances. Seealso http://www.nvidia.com/object/nvidia-grid-buy.html which implies that this licensing is needed above and beyond what licenses are needed from Citrix or VMware to access various features. Can someone perhaps provide better clarification? As far as I can tell, the GRID K1 and K2 units are exempt from this, so it would appear this is something new and specific to the M6/M60 models. If this is really true, the pricing structure could be a major factor in the decision to go with these newer models vs. the K1/K2 options.
CCU for Maxwell (M6/M60) not for Kepler (K1/K2)
+ SUMS = % Sotfware maintenance per year related CCU licenses
Pricing structure will reach new heights………..