hardware platform (cpu, amd-v or intel – vt) hypervisor parent partition (windows with hyper-v...

40

Upload: lee-lloyd

Post on 24-Dec-2015

213 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver
Page 2: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Hyper-V & Cluster Shared Volume

Vijay TewariPrincipal Program ManagerVirtualizationMicrosoft Corporation

Page 3: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Agenda

Microsoft Server Virtualization Windows Server 2008 Hyper-V

Microsoft Hyper-V ServerWindows Server 2008 R2

Hyper-VCluster Shared Volumes

Q & APlease keep questions to the end

Page 4: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Windows Server 2008 Hyper-V

DescriptionHypervisor based virtualization platform

Windows Server 2008 x64 Edition technology

Standard, Enterprise and Datacenter Editions

Hardware Requirementsx64 server with hardware assisted virtualization

AMD AMD-V or Intel VT

Hardware enabled Data Execution Prevention (DEP) required

AMD (NX no execute bit)

Intel (XD execute disable)

Note: Enabling these BIOS features requires powering down (not rebooting) the server to take effect

Page 5: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Hyper-V Architecture

Hardware Platform(CPU, AMD-V or Intel – VT)

Hypervisor

Parent partition (Windows with

Hyper-V Role enabled)

VM Worker processes

VMBUSDevice Driver

Child partition (Windows or Linux)

Guest OS Kernel

User space

…..

Child partition (Windows or Linux)

VSP

VSCStorage,

networking

Page 6: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Windows Server 2008 Hyper-V Capabilities

32-bit (x86) & 64-bit (x64) VMs

Large memory support (64 GB) per VM

SMP VMs (up to 4 cores)

Integrated cluster support for HA & Quick Migration

BitLocker: Seamless, secure data encryption

Live Backup: Volume Shadow Service integration

Pass-through disk access for VMs

Virtual Machine snapshots

New hardware sharing architecture (VSP/VSC/VMBus)

Disk, networking, input, video

Robust networking: VLANs and NLB

Based on DMTF for WMI management interface

Support for Full or Server Core installations

Page 7: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Windows Server 2008 Hyper-V

demo

Page 8: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Hyper-V: Production ScalabilityHyper-V Powering Microsoft Internet

PropertiesTechNet: 100% Hyper-Vhttp://technet.microsoft.com~1 million hits a DAY

Microsoft.com: >50% Hyper-V and growinghttp://www.microsoft.com~1 Billion hits a month

MSDN: 100% Hyper-Vhttp://msdn.microsoft.com~3 million hits a DAY

Page 9: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Microsoft Hyper-V Server

Page 10: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Microsoft Hyper-V ServerMicrosoft Hyper-V Server is available as a free download: http://www.microsoft.com/hyper-VServer

Memory support: Up to 32GB of physical memory per system

Support for servers with up to 4 physical processors CPUs (sockets)

Guest SMP support Up to 4 virtual processors

Flexible disk format

Fixed/Dynamically Expanding, Differencing, Pass-through

Management Interfaces

WMI for virtualization platform management

Heterogeneous guest support

Native 32/64 bit guest support side by side

Linux and Windows supported with ICs

Virtual Switch, VLAN, PXE support

Hvconfig utility for quick/easy setup

Page 11: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Windows Server 2008 R2 Hyper-V

Page 12: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Windows Server 2008 R2 Hyper-V

Building on the rock-solid architecture of Windows Server 2008 Hyper-V

Integration with new technologies

Enabling new dynamic scenarios:Increased Server Consolidation

Dynamic Data Center

Virtualized Centralized Desktop

Page 13: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Windows Server 2008 R2 Hyper-V – Features

All features in Windows Server 2008 Hyper-V plus

Live migration

New processor feature support

Hot add and remove of VHD

NetworkingChimney and VMQ

Support for Virtual Desktop Infrastructure (VDITerminal Server Broker

Page 14: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Live Migration

Page 15: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Live MigrationMoving a virtual machine from one server to another without dropped network connection or user perceived downtime

Failover Clustering is the foundation that enhances Hyper-V

High Availability

Disaster Recovery

Quick Migration

Live Migration

Live migration enables dynamic datacenter scenariosServicing

Load balancing VMs for power

Load balancing VMs for CPU

Page 16: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Live Migration process1. Initiated via in-box cluster UI or System Center Virtual Machine

Manager2. VM State/Memory Transfer

a) Create VM on the targetb) Move memory pages from the source to the target via Ethernet

3. Final state transfer and virtual machine restorea) Pause virtual machineb) Move storage connectivity from source host to target host via Ethernet

4. Un-pause & Run

Host 1 Host 2

Blue = StorageYellow = Networking

Shared Storage

Page 17: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Clustering & Storage todayToday: Windows Server 2008 Hyper-V

Current Failover Clustering has a “shared nothing” storage model

Each Disk is owned by a single node at any one time, and only that node can perform I/O to it

Management Overhead one VM per LUN

100 VMs = 100 LUNs

Drive letter limitations

Solutions:

Use drive GUIDs

Use partner solutions

Shared Storage

Only one node accesses a LUN at a

time

SAN

Page 18: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Clustering & StorageWindows Server 2008 R2 Failover Clustering

NEW Cluster Shared Volume (CSV)

Implemented as a mini-filter driver (Upper file system mini-filter at an altitude of 404900)

Required for Live Migration

CSV provides a single consistent file name space; All Windows Server 2008 R2 servers see the same storage

Easy setup; Uses NTFS

No reformatting SANs

Create one big data store

No more drive letter problems

Existing tools just work

Improves Hyper-V Live Migration times

Simplifies SAN/VM management

Improved Fault Tolerance Single Volume VHD VHD VHD

SAN

Concurrent access to a single file system

Single LUN for all hosts and performance enhancement for storage switchover

Page 19: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

New Processor Feature Support

Page 20: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

New Processor Feature Support

Second Level Address Translation (SLAT)

Uses new processor features to improve performance and reduce load on Windows Hypervisor

AMD: Rapid Virtualization Indexing (RVI)

Intel: Extended Page Tables (EPT)Benefits

Improve memory management performanceReduce in memory copiesMemory usage will decrease from ~5% to 1% of total physical memoryMost improvement with large working sets (TS/SQL)

Page 21: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Windows Server 2008 R2Core Parking

OverviewScheduling virtual machines on a single server for density as opposed to dispersion

This allows “park/sleep” cores by putting them in deep C states

BenefitsSignificantly enhances Green IT by being able to reduce power required for CPUs

Page 22: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Windows Server 2008 R2 Core Parking 16 LP Server

Processor is

“parked”

Processor is

“parked”

Page 23: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Virtual Storage

Page 24: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Hot Add/Remove Storage

OverviewAdd and remove VHD and pass-through disks to a running VM without requiring a reboot.

Hot-add/remove disk applies to VHDs and pass-through disks attached to the virtual SCSI controller

BenefitsEnables storage growth in VMs without downtime

Enables additional datacenter backup scenarios

Enables new SQL/Exchange scenarios

Page 25: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Hot add/remove VHD

demo

Page 26: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Networking

Page 27: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

NetworkingExtending TCP Offload support for Virtual machines

TCP/IP traffic in a VM can be offloaded to a physical NIC on the host computer.

BenefitsReduce CPU burdenNetworking offload to improve performance

Live Migration is supported with TCP Offload

Page 28: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

NetworkingVirtual Machine Queue (VMQ) Support

Overview

NIC can DMA packets directly into VM memory

VM Device buffer gets assigned to one of the queues

Avoids packet copies in the VSP

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

Page 29: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Networking

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

Page 30: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Hosted Desktops (VDI)

Page 31: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Terminal Services –Virtualization

Overview

TSV - Virtualized “Centralized Desktop” provisioning, access and management solution on top of Hyper-V

Unified user and admin experience for traditional TS (session per user) and TSV (VM per user).

Deployment Scenarios

Temporary (until Logoff) VM per user Assignment

Permanent VM per user assignment

Built-in solution for low complexity deployments

Features and management are tuned for Entry Level deployments. Example: 4 TS/TSVM Servers with few apps.

Page 32: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Connection Broker Infrastructure

TS Session Broker

TS Farm

TS Users

TS UsersRemote

Hosted Desktop Users

Hyper-V Farm

Hosted DesktopUsers (Remote)

TS Gateway

Storage

Page 33: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Summary

Large scale production environments running Hyper-V

Scalable and high performance architecture

Driving demand for higher end servers for VirtualizationCSV provides consolidation of storage with fewer LUNs

Simplifies Storage and Server Management

Removes barriers to Live Migration times

Page 34: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Call To Action

Ensure drivers installation package work with Server CoreValidate drivers work on Windows Server 2008 R2 with Hyper-V roleStorage vendors

Test your storage solutions with clustering (CSV) and Hyper-V

Page 35: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Online ResourcesMicrosoft Virtualization Home: http://www.microsoft.com/virtualization

Windows Server Virtualization Blog Site: http://blogs.technet.com/virtualization/default.aspx

Windows Server Virtualization TechNet Site: http://technet2.microsoft.com/windowsserver2008/en/servermanager/virtualization.mspx

Virtualization Solution Accelerators http://technet.microsoft.com/en-us/solutionaccelerators/cc197910.aspx

How to install the Hyper-V role http://www.microsoft.com/windowsserver2008/en/us/hyperv-install.aspx

Windows Server 2008 Hyper-V Performance Tuning Guide http://www.microsoft.com/whdc/system/sysperf/Perf_tun_srv.mspx

Using Hyper-V & BitLocker White Paper

http://www.microsoft.com/downloads/details.aspx?FamilyID=2c3c0615-baf4-4a9c-b613-3fda14e84545&DisplayLang=en

Windows Server 2008 Failover Clustering http://www.microsoft.com/Windowsserver2008/en/us/clustering-home.aspx

Build High-Availability Infrastructures with Windows Server 2008 Failover Clustering

• http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032364827&Culture=en-US

• Cluster Validation in Windows Server

• http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032336490&CountryCode=US

Page 36: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

Page 37: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Backup

Page 38: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Filter Driver Interoperability

Do you have a filter driver above or below?Virus Scanners, etc…

http://msdn.microsoft.com/en-us/library/aa488218.aspx

CSV is incompatible with data transformation drivers

Encryption or compression filters

Filter Manager

CSVFilter.sys

Upper FS mini-filter

Altitude of 404900

Page 39: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Replicated Storage Considerations

CSV is not compatible with replicated storage as all nodes assume they can simultaneously write to a LUN

Windows Server 2008 R2 will continue to support the storage model of the past, which will work with multi-site clusters

Live Migration is not dependent on CSVSite A Site B

Replica

Read/Write Read/Only

Sync/Async Replication

Page 40: Hardware Platform (CPU, AMD-V or Intel – VT) Hypervisor Parent partition (Windows with Hyper-V Role enabled) VM Worker processes VMBUS Device Driver

Call To Action

IHV’sReplication vendor considerations

ISV’s – Test, Test, Test…

Filter DriversDepending on where you are on the stack, you may be impacted

Backup/RestoreCSV will introduce new considerations

Call PrepareVolumeForSnapshotSet() for all scenariosReplaces GetVolumePathName() and GetVolumeNameForVolumeMountPoint()