Session 1 – Hyper-V as a Platform for VDI

Virtualization Overview

Virtualization isolates and abstracts computing resources

Virtual Presentation

Presentation layer separate from process

Virtual StorageStorage and backup over the network

Virtual NetworkLocalizing dispersed resources

Virtual MachineOS can be assigned to any desktop or

server

Virtual ApplicationsAny application on any computer, on

demand

Interface bound to process

Storage assigned to specific locations

Network assigned to specific locations

Operating system assignedto specific hardware

Applications installed to specific hardware and OS

Virtualization results in more efficient resource utilization, and supports greater flexibility and simplified change management

Traditional Servers Virtualized Servers

Benefits of Virtualization

Server Consolidation– Smaller OS footprint– Virtualize hardware

Reduce Costs– Space / Facilities– Physical Hardware– Maintenance– Cooling / Electricity– Green IT initiatives

High-Availability

Application Compatibility– OS Isolation– Run legacy OS / Apps– Run incompatible OS / Apps

Easier Management– Centralized Management– Fast Installation & Deployment– Templates– Dynamic Provisioning

“Why is virtualization such a big deal? A lot of people understand, and they think it's about saving money, it's about saving power, it's about green IT, it's about space, and that's certainly true. But in our perspective, it's much, much bigger than that, and people are just now beginning to understand that. We think that there's a major transformation taking place in IT. This major transformation that's been taking place for years is starting to accelerate, and we believe that virtualization is a major enabler and catalyst of that transition that's taking place.” - Tom Bittman, Gartner VP and Chief of Research of Infrastructure and Operations

Changing Market LandscapeVirtualization growth is significant and climbing

Y2005 Y2006 Y2007 Y2008 Y2009 Y2010 Y2011 Y20120

2,000,000

4,000,000

6,000,000

8,000,000

10,000,000

12,000,000

14,000,000

Physical Units Logical Units

IDC Server Virtualization Forecast

Architecture Planning

Microsoft’s Virtualization and Management Strategy– Windows Server 2008 R2 SP1 with Hyper-V role– Hyper-V Server 2008 R2 SP1– SC Virtual Machine Manager (VMM) 2008 R2 / 2012

Architecture involves planning – Hardware– Capacity– Networks– Storage– High-Availability

Host Sizing

Determine multiple workloads that will be combined– Processor, memory, network and storage I/O are critical

Benchmark performance of physical versus virtual

Use this information during assessment phase to correctly determine they number of Hyper-V hosts required for the consolidation project

Remember that if you are using clustering to keep enough spare capacity for VMs when hosts are unavailable

VM Hardware Profiles

Can be leveraged when creating VM templates

Define a set of hardware profiles– Number of Processor Cores– Amount of RAM– Number of network adapters and VLANs– Number of SCSI adapters

Example– 2 cores– 4GB RAM– 1 NIC– Boot Disk on IDE– 1 SCSI adapter with data disk

Network Architecture

Network I/O is key to consolidated workloads

Leverage multiple NICs and multi-port NICs– Public VM Traffic– VM Guest Management– Cluster: Live Migration– Cluster: Internal Communication / CSV / Heartbeats– Optional: iSCSI– Optional: Backup

Ensure that network switches are not over subscribed on the backplane

Can use VLANs for traffic separation

Can use NIC teaming for redundancy

Storage Planning

Host storage architecture includes– System drive– VM storage– Cluster Storage

System Drive– Boot and logs– Default VM storage location

VM Storage– VHDs– AVHDs– Snapshot files

Cluster Storage– Shared disks accessible by all nodes for VM storage– Clustered Shared Volumes (CSV)

Storage – VM Storage

Disk Type– Fixed – All sectors allocated at creation– Dynamic – Expanded as needed in 2MB chunks– Differencing – Overlay approach using

parent/child linking– Pass-through – dedicated LUN

When you power on a VM the snapshot files are allocated– File for storing memory contents– File for storing current state information

Storage - Architecture

DAS– Ideal for standalone hosts or hosts in remote offices where it is not

cost effective to have iSCSI or SAN

iSCSI– Great lower cost alternative form of SAN– Must leverage multiple NICS and MPIO in load balancing configuration

for maximum throughput

SAN– Requires dedicated Fiber Channel HBA– Supports tiered storage– Serial-Attached SCSI also supported

Pick the best storage based on location, number of hosts, network capabilities, or storage standards

Introduction to Hyper-V

Microsoft’s Virtualization History2003 – Microsoft acquires Connectix for virtual PC & server technologies

2004– Microsoft Virtual Server 2005

2005– Microsoft Virtual Server 2005 R2

2008– Windows Server 2008 Hyper-V– Microsoft Hyper-V Server 2008

2009– Windows Server 2008 R2 Hyper-V– Microsoft Hyper-V Server 2008 R2

2011– Windows Server 2008 R2 SP1 Hyper-V– Microsoft Hyper-V Server 2008 R2 SP1

Windows Server 2008 R2 Hyper-V

Built on Windows Server 2008 Hyper-V architecture– 400+ case studies: www.microsoft.com/virtualization

– 1 million+ downloads of Hyper-V RTM in 12 months

– Fastest growing bare metal hypervisor in x86 history

Microsoft.com running on Hyper-V R2– ~15,000 requests per second

– Over 40 million hits per day

– Over 1.2 billion page hits per month

Enabling new dynamic scenarios– Dynamic Data Center

– Virtualized Centralized Desktop

Customer Driven Design

Guest OS Support

Windows Server– Windows Server 2000– Windows Server 2003– Windows Server 2008– Windows Server 2008

R2

Windows Client– Windows XP Pro

SP2/SP3

– Windows Vista– Windows 7

Non-Microsoft– SLES 10– SLES 11– RHEL 5.2/5.3

Apps Running Inside the Guest

See KB 957006 for more informationMicrosoft Application Virtualization (App-V) Microsoft Operations Manager (MOM) 2005

Microsoft BizTalk Server Microsoft Search Server

Microsoft Commerce Server Windows SBS / EBS 2008

Microsoft Dynamics AX, CRM, GP, NAV Microsoft SQL Server 2005, 2008

Microsoft Exchange Server Microsoft System Center Configuration Manager

Microsoft Forefront Client Security Microsoft System Center Data Protection Manager

Microsoft Intelligent Application Gateway (IAG) Microsoft System Center Essentials

Microsoft Forefront Security for Exchange (FSE) Microsoft System Center Operations Manager

Microsoft Forefront Security for SharePoint (FSP) Microsoft System Center Opalis Integration Server

Microsoft Host Integration Server Microsoft System Center Virtual Machine Manager

Microsoft Internet Security and Acceleration (ISA) Microsoft Systems Management Server (SMS)

Microsoft Office Communications Server R2 Microsoft Visual Studio Team System

Microsoft Office Groove Server Microsoft Windows HPC Server 2008

Microsoft Office PerformancePoint Server Windows Server 2003 Web Edition

Microsoft Office Project Server Microsoft Windows Server Update Services (WSUS)

Microsoft Office SharePoint Server and WSS Windows Web Server 2008

64 Logical Processor Support

Overview– 4x improvement over Hyper-V R1– Hyper-V can take advantage of larger scale-up systems with

greater amount of compute resources

Up to 384 Running Virtual Machines & Support for up to 512 Virtual Processors (VPs) PER SERVER– 384 single VP VMs OR – 256 dual VP VMs (512 Virtual Processors) OR – 128 quad VP VMs (512 Virtual Processors) OR – any combination so long as you're running up to 384 VMs and

up to 512 Virtual Processors– 1000 VMs per Cluster

Processor Compatibility Mode

Overview– Allows live migration across different CPU versions

within same processor family– Configure compatibility on a per-VM basis– Abstracts VM down to the lowest common denominator

(instruction sets available to VM)

Benefits– Greater flexibility within clusters– Enables migration across a broader ranger of Hyper-V

host hardware

Forward & Backward Compatibility

When a VM is started the hypervisor exposes guest visible processor features

With Processor Compatibility Enabled, the guest processors is normalized and the following processors features are “hidden” from the VM

Host running AMD based processor Host running Intel based processor

SSSE3, SSE4.1, SSE4.A, SSE5, POPCNT, LZCNT, Misaligned SSE, AMD 3DNow!,

Extended AMD 3DNow!

SSSE3, SSE4.1, SSE4.2, POPCNT, Misaligned SSE, XSAVE, AVX

Second Level Address Translation (SLAT)

Intel: Extended Page Tables (EPT)AMD: Nested Page Tables (NPT) or Rapid Virtualization Indexing (RVI)Processor provides two levels of translation

– Walks the guest OS page tables directly– No need to maintain Shadow Page Table– No hypervisor code for demand-fill or flush operations

Resource savings– Hypervisor CPU time drops to 2%– Roughly 1MB of memory saved per VM

Installation Options

Full Installation– Post Windows Server 2008 R2 installation– Add Hyper-V role using Server Manager– Includes Hyper-V Manager and Virtual Machine Connection

tools– Local or remote management

Server Core– Minimal server configuration– Subset of binaries required for Hyper-V role– Minimal attack footprint– Fewer updates– Command line or remote management

Deployment Tools

Unattended installation– UNATTEND.XML answer file for customization– Windows System Image Manager (WSIM) to create

and manage answer file

Microsoft Deployment Toolkit 2010– Task sequence created for customization– Integration with System Center ConfigMgr

System Center VMM 2008 R2 / 2012– Hyper-V role enabled when host is added– VMM 2012 also supports bare-metal deployment

Hyper-V Management

Hyper-V Manager

Command Line

WMI

Integrated Tool Experience

Numerous Management Options

SCVMM

SCOM

Failover Cluster Manager

PowerShell

RSAT

Hyper-V Manager

PowerShell Support

Server Core, Hyper-V Server 2008 R2 & RSAT

Find a VM

Connect to a VM

Discover a VM

Change VM State

Backup a VM

Add / Remove VM

Manage VMs on Clusters

Change VM Storage

Change VM Networks

Manipulate VHD Files

Security Best Practices

Secure VHDs and snapshots files

Define networks or VLANs to isolate traffic

Only add required hardware to VM

Harden the OS in the VMs using security compliance toolkits

Install the latest Integration Services

Leverage firewalls, anti-virus and intrusion protection as appropriate

Keep VMs patched– Remember the VMs that are offline or templates

Hyper-V Networking & Storage

Virtual Switch Architecture

Implemented as an NDIS 6.0 MUX Driver– Binds To Network Adapters as a Protocol Driver– Can Enumerate A Single Host Interface

Basic Layer-2 Switch Functionality– Dynamically “Learns” Port to MAC Mappings– Implements VLANs– Does Not Implement Spanning Tree– Does Not Implement SPAN/Monitor Mode– Does Not Implement Layer 3

Virtual Network Adapters Synthetic Adapters

No Physical Device

Communicates via VMBus to vmswitch.sys

Does Not Support PXE Boot

Significantly higher performance vs. Emulated

Drivers Exist Only For Supported OS’s– Windows Server 2003 SP2– Windows Server 2008– Windows Server 2008 R2– Windows XP– Windows Vista– Windows 7– Linux (SLES 10, 11). RHEL 5.x

Emulated AdaptersEmulates a physical DEC21140 chipset

Communicates via Interrupts to vmwp.exe then to vmswitch.sys

Supports PXE Boot

Drivers Exist For Most OS’s

Virtual LAN (VLAN)

IEEE 802.1Q - Layer 2 Extension Of Ethernet To Allow Multiple Bridged Networks to Share A Common Physical Link

Egress (outbound) Network Frames Are “tagged” With a VLAN Identifier (tag)

Ingress (inbound) Network Frames Are Stripped of there VLAN Identifier (tag)

VLAN Tagging Methods

Virtual NIC Tagging– VLAN Specified Per Virtual NIC– Configured In Hyper-V/SCVMM UI/API’s

Static Switch Port Tags– VLAN Specified Per Physical Switch Port– Configured On Physical Network Switch

MAC Address Tagging– MAC Address to VLAN Mapping Created– Configured On Physical Network Switch

Physical NIC Tagging– VLAN Specified On The Physical NIC

Network Teaming

Failover Teaming– Typically Two Interfaces– Typically Connected To Different Switches– Provides Redundancy For NIC Card, Cable or Switch Failure

Aggregation/Load Balancing Teams– Two or More Interfaces– Divides Network Traffic Between Active Interfaces By

MAC/IP Address or Protocol – Redundancy for NIC Card or Cable Failure

Support provided by hardware vendors

VM Chimney (TCP Offload Support)

Overview– TCP/IP traffic in a VM can be offloaded to a physical

NIC on the host computer.

Benefits– Reduce CPU burden– Networking offload to improve performance– Live Migration is fully supported with Full TCP

Offload– Works best with long-lived connections with large

data transfers

Virtual Machine Queue (VMQ)

Overview– NIC can DMA packets directly into VM memory

VM Device buffer gets assigned to one of the queuesAvoids packet copies in the VSPAvoids route lookup in the virtual switch (VMQ Queue ID)

– Allows the NIC to essentially appear as multiple NICs on the physical host (queues)

Benefits– Host no longer has device DMA data in its own buffer

resulting in a shorter path length for I/O (performance gain)

Jumbo Frame Support

Jumbo Frame Support– Ethernet frames >1,500 bytes

– Ad hoc standard is ~9k

Overview– Enables 6x larger

payload per packet

Benefits– Improves throughput

– Reduce CPU utilization of large file transfers

Storage

Physical– DAS (SATA, eSATA, PATA, SAS, SCSI, USB, Firewire)– SAN (Fibre Channel, iSCSI, SAS)

Virtual Adapters– IDE, SCSI– Boot – IDE only

VHD– Fixed, dynamic, differencing– Pass-through– iSCSI Direct (Applicable to running iSCSI in guest OS)

MPIO and MCS

Microsoft MPIO and MCS (Multiple Connections for iSCSI) work transparently with Hyper-V

MPIO supported with Fibre Channel, iSCSI, SAS

Two Options for multi-paths with iSCSI– Multiple Connections per Session– Microsoft MPIO (Multipathing Input/Output)

When using iSCSI direct, MPIO and MCS work transparently with VMQ

Hot Add/Remove Storage

Overview– Add and remove VHD and pass-through disks to

a running VM without requiring a rebootHot-add/remove disk applies to VHDs and pass-through disks attached to the virtual SCSI controller

Benefits– Enables storage growth in VMs without downtime– Enables additional datacenter backup scenarios– Enables new SQL/Exchange scenarios

Other Hyper-V Features

Core Parking

Scheduling VMs on a single server for density as opposed to dispersion

Allows “parking” or “sleeping” of cores by putting them in deep C states

Reduces CPU power consumptionProcesso

r is “parked”

Data Protection

Windows Server Backup– Small to medium environment solution– VM, files, folders, volumes, application, system state– VSS support– No CSV support

System Center DPM 2010– Backs up running VMs without downtime– Host and guest-based protection– Bare metal recovery – CSV support

Dynamic Memory

Hyper-V Memory enhancement in 2008 R2 SP1

Memory is pooled and dynamically distributed across VMs to allow it to easily grow or shrink

Higher VM consolidation ratios on same hardware

Memory is dynamically allocated/removed based VM usage with no service interruption

Minimal performance impact or overhead

Works well for both server and desktop

VM Guests are enlightened– VM Guests & Hyper-V work together

Memory is added and removed via synthetic memory driver (memory VSC) support

Dynamic Memory SettingsStartup RAM: Memory needed to boot VM– Guest OS + Apps– Default: 512MB

Maximum RAM: Memorylimit for the VM– Default: 64GB

Memory Buffer: Free memory to try to maintain in the VM– Enables responsiveness for workload

bursts– Allows use for file cache

Memory Priority: Order in which VMs may be allocated memory– Range: 1-10,000– Default: 5,000

RemoteFX Support

3D GPU Host side Rendering

Improved Encode/Decode Pipeline

USB Redirection– Enable RemoteFX

on a VM– Client must support

RDP 7.1– USB redirection must

be enabled via GP– GP update and

reboot required

SCVMM 2008 R2

Remote Management

Introduction to SCVMM

Maximize Resources– Centralized virtual machine deployment and management for Hyper-V, Virtual

Server, and VMware ESX servers– Intelligent placement of virtual machines– Fast and reliable P2V and V2V conversion– Comprehensive application and service-level monitoring

with Operations Manager

Increase Agility– Rapid provisioning of new and virtual machines with templates– Centralized library of infrastructure components– Leverage and extend existing storage infrastructure and clusters– Allow for delegated management and access of VMs

Leverage Skills– Familiar interface, common foundation – Monitor physical and virtual machines from one console – Fully scriptable using Windows PowerShell

Enterprise Topology

London

Windows PowerShell

Administrator Console

Web-based Delegated

Provisioning UIExternal Network (DMZ) Brisbane

Remote Library Server

Remote Library Server

Remote Library Server

Virtual Machine

Hosts

Virtual Machine

Hosts

Virtual Machine

Hosts

Overview of SCVMM Architecture

Virtual Machine Manager (VMM) Engine Server– VMM Engine running on dedicated server– VMM System Console

VMM Agent– Installed on the Virtual Server host machines– Communicates with VMM Engine

Library Server– File store for the virtual infrastructure building blocks

SQL Server– Stores the configuration and discovery information

Interfaces– Admin UI; Web; Command line

SCVMM Administration Tools

VMM Scripting Through PowerShell

Microsoft’s command shell for scripting and development

Consistent scripting syntax– Encapsulate platform differences

VMM PowerShell Snap-in– 170+ command-line functions– Foundation for VMM administrator’s

console and Self Service Portal– All PowerShell operations are logged and

audited

Self Service Portal

Authorized users can provision new virtual machines without directly involving IT staff– This capability especially targets software

test and development teams, which often set up temporary virtual machines to try out new software

IT administrators retain control over access to resources

Deployment & Management of Agents

In order to manage the virtual infrastructure, SCVMM installs software agents on each host server

The management agents gather data from the host server’s Windows Server operating system and feed that information back to SCVMM

Managing Hyper-V HostsWizard-based experience for adding hosts– Remote installation and configuration of virtualization software and

management interfaces– Remotely enable the Hyper-V role

Easy management of Hyper-V host clusters– Add entire Hyper-V host cluster in a single step– Automatic detection of node additions/removals

Management of Windows Server 2008 failover clusters for Hyper-V– Specify number of node failures you want to sustain but still have all your

high availability (HA) VMs running– Intelligent Placement ensures that new HA VM creation will not

overcommit the cluster– Node failures automatically trigger overcommit re-calculation

Quick Storage Migration (QSM)Cluster and CSV are not required for QSM

Allows migration of a running virtual machine’s files to a different storage location on the same host with minimal service outage– Live migration and quick migration move where VM is hosted– QSM moves the disks themselves

Advantages of QSM– Ability to migrate a VM from a LUN to a CSV volume in cluster

QSM can migrate the storage with minimal downtime– VM now resides on CSV volume and can participate in faster

live migration

Maintenance Hosts and ModeA maintenance host is one dedicated for VM maintenance tasks, such as patching stored VMs and templates before moving the VMs into your production environment

Enabling Maintenance Mode– On a stand-alone host, places all running virtual machines into a saved state– On a Windows-based host cluster that is capable of live migration, gives you

the option to do one of the following:Live migrate all running highly available virtual machines to other hosts in the cluster, and place any running virtual machines that are not highly available in a saved statePlace all running virtual machines into a saved state

– Blocks all virtual machine creation operations on the host– Excludes the host from the host ratings during placement– Displays a host status of In Maintenance Mode in Hosts view of the VMM

Administrator Console

Working with the LibraryRepository for all VM building blocks– VHDs– Offline VMs– ISOs– Sysprep Answer Files– PowerShell Scripts with Run option– Templates

Use centralized or distributed Windows files servers as libraries– Move/copy/delete/modify files directly in the file system– VMM tracks changes and provides physical and logical view– VMM stamps objects with a Id to uniquely track the object

Working with TemplatesA virtual machine template is a library resource consisting of the following parts: – Hardware profile– Virtual hard disk– Guest operating system profile

ReportingVirtual Machine Manager leverages the monitoring and reporting capabilities of System Center Operations Manager 2007 to provide the reports for virtual machines and hosts The reports are available from the Reporting view of the VMM Administrator Console and from the Operations Manager consoleTo enable reporting and display Reporting view, first configure Operations Manager integration with VMM, then set up reporting in VMM

Performance & Resource Optimization (PRO)

Supports workload- and application-aware resource optimization within a virtualized environment

Based on performance and health data provided by PRO-enabled management packs in SCOM, PRO can automatically or manually implement recommendations for minimizing downtime and accelerating time to resolution

Before you can enable PRO, you must integrate Operations Manager 2007 SP1 or Operations Manager 2007 R2 with VMM

Conclusion

Deploy your virtualized environment and manage your datacenter using best practices

Hyper-V’s integrated architecture, management, networking and storage leads to a great virtualization solution

There are many Hyper-V features designed to optimize, secure and manage your datacenter

©2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista, Windows Azure, Hyper-V and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this

presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.

MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.