Eitan spector OS & Virtualization practice leader

Agenda

Discuss Hyper-V ArchitectureHyper-V Storage Best PracticesHyper-V Networking Best PracticesVirtualization and High AvailabilityHyper-V BackupHyper- V performance SCVMM Deployment

Windows Server 2008

VSPVSPWindows Kernel

Applications

Applications

Applications

Non-Hypervisor Aware OS

Supported Windows OS

Windows Kernel VSC

VMBusVMBus Emulation

Emulation

“Designed for Windows” Server Hardware

Windows hypervisor

Xen-Enabled

Linux KernelLinux

VSCLinux VSC

Hypercall Adapter

Hypercall Adapter

Parent Partition

Child Partitions

VMMSVMMS

WMI Provider

WMI Provider

VM Worker

Processes

Microsoft Hyper-VMicrosoft / Citrix

(XenSource)

User ModeRing 3

Kernel ModeRing 0

Ring -1

IHV Driver

s

VMBusVMBus

VMBusVMBus

Applications

OS

ISV / IHV / OEM

Provided by:

Hyper-V Architecture

Windows Server 2008 with Hyper-V Technology

A role of Windows Server 2008 (Std, EE, DC)• Can be installed on both Windows Server

2008 Full and Core• Production servers can be configured as

a minimal footprint Server Core roleHypervisor based architectureFlexible and dynamic virtualization solutionManaged by the Microsoft System Center family of products

64-Bit processors with hardware virtualization extensions enabled• Intel-VT• AMD-V• Hardware enabled Data Execution Prevention (DEP) required

• AMD (NX no execute bit)• Intel (XD execute disable)

RAM• Parent Partition 1GB• Each Guest + ~21MB overhead

Disk• Parent partition• Space to store VHDs• Space to store VSS snapshots• Space to store VM snapshots

Network• 1 NIC for parent partition management• 1+ NICs for Virtual Networks Guest usage• 1 NIC for iSCSI (optional)

Balanced system Best PracticesWindows Server 2008 x64 Edition EE/DTC

Server Core Installation

Quad processor/Quad Core (16 cores)

AMD-V or Intel VT

Memory2 GB per core minimum (32 GB)4 GB per core recommended (64 GB)

Storage4 Gb Fibre Channel

Networking1 Gb/E NIC (onboard) for VM management/cluster heartbeat/migration1 quad-port Gb/E PCI-E for VMs

Windows Server Core

Windows Server frequently deployed for a single role

• Must deploy and service the entire OS in earlier Windows Server releases

Server Core a new minimal installation option• Provides essential server

functionality• Command Line Interface only,

no GUI ShellBenefits• Fundamentally improves

availability• Less code results in fewer

patches and reduced servicing burden

• Low surface area server for targeted roles

• More secure and reliable with less management

Hyper-V Storage Best PracticesPerformance wise from fastest to slowest…

Fixed Disk VHDs/Pass Through Disks• Slight performance difference

Dynamically Expanding VHDs• Grow as needed• Do not use for production workloads

Pass Through DisksVM writes directly to a disk/LUN without encapsulation in a VHDCons:• You can’t use VM snapshots• Dedicating a disk to a vm

Hyper-V Storage Best Practices

Leverage MPIO solutions to provide SAN path and bandwidth advantagesUse Pass thru disks for I/O intensive workloads• Database workloads OLTP/DSS• File Servers

Leverage ISCSI on the Host (Best Performance)• Leverage TOE and offload cards• Use ISCSI in the guest for guest clusters

Hyper-V Networking

Parent PartitionVirtual networks bound to physical NICs• External – limited by the

number of NICs• Internal - unlimited• Private - unlimited

Ethernet NICs onlyNetwork teamingVLAN Support• Trunking

No Wireless NIC support

Virtual machineSynthetic NICLegacy NIC12 NICs per VM• 8 synthetic• 4 legacy

Up to 10Gb/sVLAN support

Parent Partition: TCP/IP Properties

Virtual Switch ConfigurationParent Partition LAN Configuration

Hyper-V Best Practices Network Configurations

Example:• Server has 4 physical network adapters• NIC 1: Assigned to parent partition for

management• NIC 2: Assigned to parent partition for

iSCSI• NICs 3/4: Assigned to virtual switches for

virtual machine networking

Hyper-V Setup, Networking & iSCSI

Windows Server 2008

VM 2VM 1

“Designed for Windows” Server Hardware

Windows hypervisor

VM 3

Parent Partition

Child Partitions

User Mode

KernelMode

Ring -1Mgmt

NIC 1MgmtNIC 1

iSCSI NIC 2

iSCSI NIC 2

VSPVSPVSPVSP

VSwitch 1

NIC 3

VSwitch 1

NIC 3

VSwitch 2

NIC 4

VSwitch 2

NIC 4

Applications

Applications

Applications

VM ServiceVM Service

WMI Provider

WMI Provider

VM Worker

Processes

Windows Kernel VSC Window

s KernelVSC Linux

Kernel VSC

VMBusVMBus VMBusVMBus VMBusVMBusVMBus

VMBus

Microsoft Hyper-V Quick Migration

Provides solutions for both planned and unplanned downtime

Planned downtime• Quickly move virtualized workloads to

service underlying hardware• More common than unplanned

Unplanned downtime• Automatic failover to other nodes

(hardware or power failure)• Not as common and more difficult

Quick MigrationFundamentals – Planned Downtime

1.Save statea) Save entire virtual

machine state

2.Move virtual machinea) Move storage

connectivity from origin to destination host

3.Restore state and Runa) Restore virtual

machine and run

VHDsVHDs

Network ConnectivityNetwork Connectivity

Shared StorageShared Storage

Quick Migration Storage Best Practices

Pass-through Disks in a cluster• Provides enhanced I/O performance• Requires VM configuration file to be stored

separate from the virtual machine file• Create file share on the cluster and store VM

configuration files for virtual machines that use pass-thru.

VHD Based• One LUN per VM best practice• Ability to provision more then one VM per LUN

but all failover as a unit• 3rd part solutions offer the ability to provision a

LUN with multiple virtual machines with granular failover

Hyper-V Backup Best Practices

Ensure your backup solution supports VSS• Support for the VSS writer in Hyper-V

specificallyVirtual Machine Backup Best practices• Leverage the Hyper-V VSS writer to take

online snapshots of virtual machinesSystem Center Data Protection Manager• Will provide Hyper-V VSS snapshots• Ability to quickly recover virtual

machines• Replicate snapshots to backup location

for DR

Looking at Hyper-V Performance

Guest OS processors/cores are not bound to physical processors/coresPhysical Memory Must match the Combined Memory of All of the Guest Computers• 1GB for parent partition + memory of VM

+21MB

The parent partition is a Virtual Machine• Only run Ecosystem applications (backup,

Antivirus)

Measure Hyper V and Virtual machine performance using new Hyper Performance counters• 29 new Hypervisor related performance

counters

Looking at Hyper-V PerformanceMeasuring Processor Usage• Measuring the physical host computer’s

(Root Partition) Processor Capacity• Hyper-V Hypervisor Logical Processor(*)\% Total Run

Time: The percentage of time spent by the processor in guest and hypervisor code.

• Measuring Guest Computer Processor Utilization• \HyperVisor Hyper-V Logical Processors(*)\% Guest Run

Time:

Looking at Hyper-V PerformanceMeasure Memory usage• Measuring Available Memory on the

Hyper-V Host Computer:• \Memory\Available MBytes: Available MBytes

is the amount of physical memory available to processes running on the computer, in Megabytes.

• Same for measuring memory usage in the Virtual machine

Operations Manager Server

Virtual Machine Manager

Server

ConnectorWindows® PowerShell

Self Service Web Portal

Administrator’s Console

Virtual Center Server

VM VM VM VM

Management Interfaces

SAN Storage

VM

VM

VMM Library Server

VM Template

ISO ScriptVHD

Operator’s Console

Web Consol

e

Windows PowerShe

ll

VMware VI3

ESX HostVM VM VM VM

VM VM VM VM

VMM 2008 VMM 2008 ArchitectureArchitecture

VM

VM

VMM 2008 VMM 2008 RequirementsRequirements

VMM 2008 Server requires Windows Server 2008 x64 for installation

VMM 2008 Console will install on Windows Server 2003, Windows Vista, and Windows Server 2008 x86/x64

VMM 2008 Agent install on Windows Server 2003/2008.

VMM 2008 VMM 2008 InstallationInstallation

VMM 2008 Server requires Active Directory for security• Can manage non-AD computers, but

needs AD for installationEach VMM 2008 component can be separate servers or on a single server (demo/test)

VMM 2008 can be run inside a VM• Just be aware of the chicken & the egg

issue (understand you will need Server Manager to start the VMM VM)

VMM 2008 ScalabilityVMM 2008 Scalability

Support 400 hosts 8000 virtual machines per VMM Server.Best practice VMM server per datacenter• Split host management by location

Create library servers close to hosts• In branch offices load the library server on the

VM host• Assign to separate spindles for I/O

Replication of library servers • VMM does not provide a built in replication

mechanism• Leverage DFS-R• 3rd party replication tools (Doubletake)

Thank You Thank You

eitansp@glasshouse.com