S4726 VIRTUALIZATION 101

- AN INTRO TO VIRTUALIZATION
Luke Wignall & Jared Cowart
Senior Solution Architects | GRID
AGENDA
§  Virtualization 101
—  The Definition
—  The History
—  The Benefits
§  Fundamentals of virtualization technology
—  Servers (VMs)
—  Desktops (VDI)
—  Applications
§  Why does NVIDIA care about virtualization?
—  The power of GPUs
§  ROI examples
VIRTUALIZATION 101:
WIKIPEDIA DEFINITION…
§  Virtualization, in computing, refers to the act of creating
a virtual (rather than actual) version of something, including
but not limited to a virtual 
computer hardware platform, operating system (OS), 
storage device, or computer network resources.

§  The term "virtualization" traces its roots to 1960s mainframes,

during which it was a method of logically dividing the
mainframes' resources for different applications. Since then,
the meaning of the term has evolved to the aforementioned.
VIRTUALIZATION 101:
SIMPLE DEFINITIONS…
§  Server virtualization allows you to run multiple virtual
machines on a single physical server.

§  Desktop virtualization allows you to run multiple desktop

machines on a single physical server, and distribute them.

§  Application virtualization allows you to distribute multiple

copies of an application from a single physical server.
VIRTUALIZATION 101:
A SIMPLE VISUAL…
 VIRTUALIZATION 101:
A LITTLE HISTORY…

1960 1970 1980 1990 2000 2010 Today

The age of the Mainframe The PC arrives Things get complicated The cloud moves in… again
§  Centralized computing §  Decentralized §  PC sprawl §  Centralized computing
§  First virtualization computing
§  Bubble bursts §  Return to Virtualization
§  Thin Clients and Thin Clients
§  The Internet of Things,
then the Internet of
Everything!
SO WHY VIRTUALIZE:
RESOURCE OPTIMIZATION!
§  Increased density
§  Improves resource optimization but without sacrificing performance

Physical World Virtual World

1:1
1:1

1:1 1:1

1:1
Many:1
1:1
SO WHY VIRTUALIZE:
RESOURCE OPTIMIZATION!
§  Underutilized hardware
—  VMware in 2007: +20% of physical servers at <0.5% of util, 75% at <5%

140.00%
120.00%
100.00%
80.00%
60.00% Actual Use

40.00% Forecast Use

20.00% Cost

0.00%
Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7
 " 

SO WHY VIRTUALIZE:
THE OTHER ADVANTAGES…
VMware

§  Partitioning
—  Run multiple operating systems on one physical machine
—  Share physical resources between virtual machines
§  Portability
—  Entire virtual machine is saved as a file, so… "  E
—  Move, copy, or export as easily as a file b
§  Security "  M
—  Hardware is isolated from the operating system e
—  Recovery as easily as restoring a file
§  Agnostic 14

—  Migrate a virtual machine between similar, or different, physical servers

SO WHY VIRTUALIZE:
BUT WHAT ABOUT DESKTOPS?
§  We thought in terms of the personal computer
—  1:1 computer to worker
—  Refreshed every 3-5 years
§  We were happy in our cubes
—  It was the only place we could connect
§  IT budgets grew with PC sprawl
SO WHY VIRTUALIZE:
BUT WHAT ABOUT DESKTOPS?
§  Resource management issues
—  Order in bulk, homogony saves money
—  Buy for the most demanding group of users, overkill for rest
—  Satisfying end user experience
§  High end users
—  Each one is custom
—  Chained to desk
—  Required GPU
§  IT operations staff to manage it all
—  Security/Anti-virus/Updates/Patches
—  Hardware issues
—  Distributed/Geography
SO WHY VIRTUALIZE:
BUT WHAT ABOUT DESKTOPS?
§  Business demanded:
—  Cost savings
—  Flexibility
—  Mobility
§  End users demanded:
—  Frequent refresh
—  More “power”
—  Mobility
—  BYOD
—  Graphics
SO WHY VIRTUALIZE:
AND WHAT ABOUT APPS?
§  Application virtualization allows distribution of multiple
copies of an application from a single physical server.
—  Streamed to BYOD
—  Centrally managed
—  Ease of support
§  Typical solutions:
—  Citrix Metaframe…Presentation Server…now XenApp
—  VMware ThinApp
—  Microsoft App-v
—  Others…
HOW DOES IT WORK:
IT STARTED WITH SERVERS
§  Eureka! We just lie to the Operating system!
§  We insert a hypervisor to manage the host hardware
§  We load “servers” as guests on the host hardware
—  Para-virtualized vs. Full
—  Enlightened
§  The hypervisor will tell the guest OS whatever we want
—  Vanilla drivers
—  Flexibility
…its like magic!
THE HOW:
SERVERS, GOING FROM PHYSICAL TO VIRTUAL
§  Same hardware
§  Tiny hypervisor
§  Flexibility
Virtual Virtual
Server Server §  Scalability
§  Security
Physical
Server §  Recoverability

Hypervisor of choice

Same Physical Hardware

THE HOW:
POWER OF BEING VIRTUAL – MOTION!

Virtual Virtual Virtual

Server Server Server

Same Hypervisor of choice Same Hypervisor of choice

Same Physical Hardware Same Physical Hardware

THE HOW:
POWER OF BEING VIRTUAL – MOTION!

Virtual Server
Virtual Server
Virtual Server

Virtual Server
Hypervisor Hypervisor Hypervisor

Host Host Host

SAN Attached storage holds vDisks

Adds more flexibility (motion)
BACK TO WHY:
WHAT ABOUT DESKTOPS THEN?
§  If servers, why not desktops?
—  Administration: Cat herding
—  Security: No moat big enough
—  Budget: The cost of one of everything
§  End users…they are NOT virtual!
—  The power of “more”
§  Multi-media is only increasing
—  The power of “mine!”
§  Huge mistake to take things away from end users
—  The power of “meh”
§  Their home PC with Win7 looks better than VDI
§  Huge project dies thanks to CEO receptionist
THE HOW:
DESKTOPS, GOING FROM PHYSICAL TO VIRTUAL
§  Server hardware
§  Density math
§  Like VM’s
Physical Virtual
Virtual
Virtual Virtual
Virtual Virtual
Virtual —  Flexibility
Workstation Workstation Workstation
Workstation
Workstation
Workstation Workstation
Workstation
—  Scalability
—  Security
—  Recoverability

Hypervisor of choice

Server Physical Hardware

PITFALLS OF VIRTUALIZATION
THE DARK SIDE…
§  Planning
—  Devil in the details (SOLUTION: Start simply!)
§  Implementation
—  KISS (SOLUTION: Start simply!)
—  Over deploy to group (GPU)
—  Metrics/Monitor, optimize after acceptance
§  Resource contention
—  Density issues (SOLUTION: Add resources)
§  Adoption
—  “meh” will kill the whole project (SOLUTION: GPU!)
WHY DOES NVIDIA CARE?
END USER EXPERIENCE!
§  Users expect as good or better than physical
—  “meh” earns a FAIL
§  Designers require 3D High Definition graphics
—  Highly paid employees
—  Core of the business
—  Previously NOT an option for VDI
§  CPU is simply not a GPU
§  Future will be more visual, not less!
WHY DOES NVIDIA CARE?
CPU VS. GPU

GPU Accelerator
CPU Optimized for Many
Optimized for Parallel Tasks §  Physical CPU in host
Serial Tasks —  Shared
—  Doing networking
—  NOT a GPU!
§  Impacts density!
 WHY DOES NVIDIA CARE?
VISUAL REALISM AND ACCURACY

Complex materials surfaces, reflections and shadows

Fast and Interactive Performance
Without RealView (without GPU) With RealView (with GPU)
 SEGMENTING THE USER POPULATION
DESIGNER

Tier 1 (e.g. design engineers)

Designing / Rendering 3D High Definition Graphics
POWER USER

Tier 2 (viewing/editing of 3D drawings)

Viewing or working with 3D HD Graphics
KNOWLEDGE
WORKER

Tier 3 (typical knowledge workers)

Becoming more visual!
 DESIGNER IMPORTANCE OF GPU

VIRTUAL WORKSTATION
Nice to Have GPU Needs GPU

3D Engineering & Design Apps

POWER USER

Office Productivity PLM & Volume Design

VDI / Virtual App

KNOWLEDGE WORKER
Windows 7 Web
 NVIDIA GRID K2

DESIGNER

NVIDIA GRID K1

POWER USER

GPU 4 Kepler GPUs 2 High End Kepler GPUs

CUDA Cores 768 (192/GPU) 3072 (1536/GPU)

Memory Size 16GB DDR3 (4GB/GPU) 8GB GDDR5 (4GB/GPU)

KNOWLEDGE
WORKER Max Power 130 W 225 W

Equivalent Quadro
Quadro K600 (entry) Quadro K5000 (high end)
with Pass-through
1 Number of users depends on software solution, workload, and screen resolution
DELIVERING GPU:
THE MISSING INGREDIENT FOR VDI!
§  NVIDIA Quadro for professional graphics
—  The trusted industry standard
—  ISVs look for NVIDIA driver
§  All users expect a great visual experience!
§  The challenge: How to deliver in a virtual environment?
—  Avoid physical desktop issues
—  Take advantage of virtual benefits
GPU PASS-THROUGH (VDGA)
NVIDIA
App App App VDA
App
SOFTWARE Accelerated Capture
GUEST OS

Virtual Virtual Virtual Virtual NVIDIA Client

Driver Driver Driver Driver Driver

VIRTUAL MACHINE
VIRTUALIZATION

vCPU vMemory vStorage vNetwork GPU

NVIDIA
HYPERVISOR Pass-Through
HARDWARE

GRID K1
GRID K2
CPU Memory Storage Network GPU Quadro 2000-6000
Quadro K5000
SERVER
 GPU VIRTUALIZATION (VGPU)

App App App VDA

App
Standard NVIDIA Driver
Software

Guest OS

Client
Citrix XenServer
Virtual Virtual Virtual Virtual NVIDIA
Driver Driver Driver Driver Driver

VIRTUAL MACHINE NVIDIA GRID software

from NVIDIA
Virtualization

vCPU vMemory vStorage vNetwork vGPU

HYPERVISOR GRID vGPU

Manager GRID K1, K2
Hardware

CPU Memory Storage Network GPU

Server
Graphics Options in Virtualization
A TYPICAL VIRTUALIZATION PROJECT
§  Phase 1: Analysis & Planning
§  Phase 2: Design
§  Phase 3: POC
§  Phase 4: Rollout
§  Then let it bake…
§  …if that goes well then expand.
 A TYPICAL VIRTUALIZATION PROJECT

Use Case Analysis:

User groups, application sets,
workflows, peripherals, network
Implementation — connections, and locations
Analysis & Planning User Segmentation
Phase Designers and Engineers —
use vDGA, vGPU
Editors and Viewers —
use vDGA, vSGA, vGPU
 A TYPICAL VIRTUALIZATION PROJECT

Design Focus
Network — type, bandwidth, latency, QoS

Implementation — VM Configuration — vCPU allocation

User Density per physical or virtual server
Design Phase Phase VM Density per hypervisor host
Hypervisor configuration
Storage infrastructure
 A TYPICAL VIRTUALIZATION PROJECT

Proof of Concept
Select user group
Common set of simple apps
Implementation — Measurable expectations
POC Phase Phase Capacity Planning and Sizing
Use POC Results
Use Lakeside, SysTrack
 A TYPICAL VIRTUALIZATION PROJECT

Monitor and Tune

Implementation — VM Configuration (vCPU allocation,
memory allocation, etc.)
Rollout Phase Phase VM Density per Host, decrease or increase
number of VMs
DENSITY MATH
§  Bottlenecks
—  IOPS?
—  CPU?
—  Networking?
—  GPU?
§  Breathing room
—  Plan for spikes!
§  Babysitting
—  Monitoring (Lakeside promo, Tuesday PM session)
—  Metric tracking
THE WHAT:
VIRTUALIZATION INGREDIENTS
§  Server, er…HOST hardware
—  RAM, RAM, and more RAM: When to over subscribe
—  NICs: Must have clean networking
—  Local storage, or no local storage (IOPS?)
§  Hypervisor
§  Storage
—  SAN
—  NAS
—  NFS
§  Server, er…GUEST operating system
—  i.e. Workloads
§  GPU – the missing ingredient!
CASE STUDY
ALL SITUATIONS ARE UNIQUE…
§  … but the math is similar
§  Knowledge Worker GPU upgrade
—  EU Bank
—  400 Users
—  Knowledge Workers (tellers, loan officers, etc.)
CASE STUDY:
VDI FOR KNOWLEDGE WORKERS
§  Knowledge Workers are typical POC starting point
—  Less costly downtime
—  Typically simple apps, common builds
§  Greatest number of desktops to manage
—  High help desk needs
§  Becoming graphics users
—  Office 2013 (PowerPoint)
—  Flash, HTML5, etc.
—  Perception is GPU is too costly
§  Many existing deployments stalled
—  Poor adoption, why? GPU!
CASE STUDY:
ASSUMPTIONS
§  Customer is needing to improve EUC experience in existing
VMware deployment for 400 users
§  VMware Horizon View is in place, so not factoring that cost.
§  So, also not factoring in physical PC costs like 400 antivirus
licenses
§  ESXi is included in View licensing
§  vSGA is the GPU sharing method
§  vMotion is a requirement, downtime is unacceptable
§  64 VDI’s, using 512MB of FB RAM, per server is max.
§  What if we gave them high end solution!
CASE STUDY:
TYPICAL KNOWLEDGE WORKER PHYSICAL PC
§  Mini Tower or similar
§  Quad Core i5
§  4GB RAM
§  Integrated HD Graphics
§  Windows 7/8 Pro
§  24” Monitor
§  Cost: ~$830/user

§  400 users x $830 = $332,000

§  400 physical PC’s needing 1:1 admin
§  Distributed security concerns
CASE STUDY:
SERVER DISTRIBUTION OF VDI’S
Server w/ Server w/ Assumption: The
64 Users on 64 Users on recommended number
2x K1’s 2x K1’s of users/desktops on a
server is 64. There is
Server w/ Server w/ room for some growth
64 Users on 64 Users on on the 7th server.
2x K1’s 2x K1’s
400 Total
End Users Server w/ Server w/
64 Users on 16 Users on
2x K1’s 2x K1’s
High Availability:
Server w/ Server w/ Allows for all users on
64 Users on 0 Users on 2x
one host to be
2x K1’s K1’s vMotioned to this host.
CASE STUDY:
CUTTING EDGE KNOWLEDGE WORKER VDI
HP DL380p
2 Socket, 8 core CPUs
256GB RAM
2TB Local storage
2x GRID K1 GPU cards
Cost: ~$21,000
8 servers = $168,000

Windows 7/8 Pro Licenses

400 x $130 = $52,000

HP t410 AiO Thin Client

Cost: ~$420/ea
400 users x $420 = $168,000

Total: $388,000 ($970/user)

1 master image to manage
Centralized Security
 CASE STUDY - 10 YEAR CAPEX
$1,400,000
Phy PC VDI PC Total Exp VDI Total Exp
$1,200,000

$1,000,000

$800,000

$600,000

$400,000

$200,000

$0
Year Year Year Year Year Year Year Year Year Year Year
0 1 2 3 4 5 6 7 8 9 10
QUESTIONS
THANK YOU!
§  Keep learning!
—  Subsequent sessions:
S4783 - Virtual is Better than Physical – Delivering a Delightful User
Experience from a Virtual Desktop - NEXT!

S4725 - Delivering High-Performance Remote Graphics with NVIDIA GRID

Virtual GPU

S4686 - NVIDIA GRID for VDI: How To Design And Monitor Your Implementation

S4948 - If You Build It, Will They Come? Better Question Is, Will They Stay?
…and so much more, keyword “GRID”!