Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Hyper-V Architecture, Scenarios And Networking Jeff Woolsey Senior Program Manager Windows Virtualization Microsoft Corporation VIR358.

Similar presentations


Presentation on theme: "1 Hyper-V Architecture, Scenarios And Networking Jeff Woolsey Senior Program Manager Windows Virtualization Microsoft Corporation VIR358."— Presentation transcript:

1 1 Hyper-V Architecture, Scenarios And Networking Jeff Woolsey Senior Program Manager Windows Virtualization Microsoft Corporation VIR358

2 2 Objectives And Takeaways Objective(s) Windows Server 2008 Hyper-V Architecture Why is there a parent partition? Hyper-V Isolation Virtualization Demo Hyper-V Networking Hyper-V on Laptops, Demo Configs and Considerations Virtualization Comparison

3 3 Hyper-V Beta In The Press “My experience has left me extremely impressed. Windows Server 2008 on large- scale, virtualized enterprise servers will make alternatives a very hard sell.” - Infoworld “Microsoft's virtualization has three unique advantages: It costs nothing, its administration is integrated into Microsoft's other server management tools, and Windows Server 2008 is the only host OS it needs to support. In that last case, Windows shops derive a serious performance and scalability kick...” - Infoworld “Hyper-V is free as a built-in feature in Server 2008 Standard and ESX Server costs several thousand dollars per copy, depending on the features purchased, so on a pure bang per buck and ease of use basis, it beats ESX and dare I say it – the Xen solutions built into Linux distros – hands down. - ZDNet “Even though Hyper-V is still pre-1.0 code, I think Microsoft has done a bang-up job with its hypervisor, and it may just turn this Linux freak into a Windows 2008 junkie for running his own personal virtualization needs.” - ZDNet “Yes, jaws actually dropped when it [Hyper-V] was installed in the Test Center.” - CRN

4 4 Virtualization In The Industry

5 5 Virtualization Market Today Computerworld “Although virtualization has been the buzz among technology providers, |only 6% of enterprises have actually deployed virtualization on their networks, said Levine, citing a TWP Research report. That makes the other 94% a wide-open market.” The Rise of the Virtual Machine and the Real Impact It Will Have “We calculate that roughly 6% of new servers sold last year were virtualized and project that 7% of those sold this year will be virtualized and believe that less than 4% of the X86 server installed base has been virtualized to date.

6 6 Virtualization 2010 Information Week Oct “The [virtualization field] is nowhere near saturated. IDC estimates that only 17% of the worldwide server market will be virtualized by 2010, up from 5% in 2005.”

7 7 Microsoft IT Going Green Production Use Virtual Server in heavy use for 18+ months 2,500+ virtual machines ~100 new VMs per month Consolidation Ratios 8 servers to 1 server Test/Development Savings Test/Development Use Virtual Server in heavy use for 18+ months 500+ virtual machines Consolidation Ratios 16 servers to 1 server ItemPhysical System CostVirtual Server Build CostSavings Number of servers required477 a cost of $5k each Total $2.3 million 16 physical host $20k each Total: $320 thousand Just under 2 million dollars Hard drive space19 terabytes8 terabytes11 terabytes Rack space30 racks2 racks28 racks

8 8 Windows Server 2008 Hyper-V

9 9 Windows Hyper-V Requirements Description Hypervisor based virtualization platform Windows Server 2008 x64 Edition technology Standard, Enterprise and Datacenter Editions Hardware Requirements x64 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

10 10 Architecture

11 11 Windows Server 2008 VSP Windows Kernel Hyper-V Architecture Applications Non- Hypervisor Aware OS Windows Server 2003, 2008 Windows Kernel VSC VMBus Emulation “Designed for Windows” Server Hardware Windows hypervisor Xen-Enabled Linux Kernel Linux VSC Hypercall Adapter Parent Partition Child Partitions VM Service WMI Provider VM Worker Processes OS ISV / IHV / OEM Microsoft Hyper-V Microsoft / XenSource User Mode Kernel Mode Provided by: Ring -1 IHV Drivers VMBus Applications

12 12 Why Not Get Rid Of Parent Partition? No defense in depth Entire hypervisor running in the most privileged mode of the system Scheduler Memory Management Storage Stack Network Stack VM State Machine Virtualized Devices Drivers Management API Hardware Ring -1 User Mode Kernel Mode User Mode Kernel Mode User Mode Kernel Mode Ring 0 Ring 3 Virtual Machine Virtual Machine Virtual Machine

13 13 Micro-kernelized Hypervisor Defense in depth Using hardware to protect Hyper-V doesn’t use ring compression, uses hardware assists Further reduces the attack surface Scheduler Memory Management Hardware VM State Machine Virtualized Devices Management API Ring -1 Storage Stack Network Stack Drivers User Mode Kernel Mode User Mode Kernel Mode Ring 0 Ring 3 Parent Partition Virtual Machine Virtual Machine

14 14 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 DMTF standard for WMI management interface Support for Full or Server Core installations

15 15 Windows Server Core Server Core: New minimal installation option Provides essential server functionality Command Line Interface only, no GUI Shell Benefits Less code results in fewer patches and reduced servicing burden Low surface area server for targeted roles More secure and reliable with less management

16 16 Security Isolation No sharing of virtualized devices Separate VMBus instance per vm to the parent No sharing of memory Each has its own address space VMs cannot communicate with each other, except through traditional networking Guests can’t perform DMA attacks because they’re never mapped to physical devices Guests cannot write to the hypervisor Parent partition cannot write to the hypervisor

17 17 Hyper-V RC0 It Just Works TAP, RDP & MSIT Hyper-V Deployments Thousands of Hyper-V VMs in PRODUCTION Windows Server 2003/2008 Roles: File, Print, AD, RODC, IIS/Web, TS, Application Services, DHCP, DNS, WSS and more… Microsoft Server Products SQL, Exchange, HPC, ISA, Sharepoint, Project Server, VSTS, Configuration Manager, Ops Manager, VMM & more… Hyper-V Stats Performance Blockers: ZERO Deployment Blockers: ZERO Application Compatibility Bugs: ZERO Scalability Blockers: ZERO

18 18 Hyper-V Demo Mike Sterling Program Manager Windows Virtualization Microsoft Corporation

19 19 Hyper-V Networking

20 20 Hyper-V Networking Two physical network adapters at minimum One for management One (or more) for VM networking Dedicated NIC(s) for iSCSI Connect parent to back-end management network Only expose guests to internet traffic

21 21 Hyper-V Network Configurations Example 1 Physical Server has 4 network adapters NIC 1: Assigned to parent partition for management NICs 2/3/4: Assigned to virtual switches for virtual machine networking Storage is non-iSCSI such as Direct attach SAS or Fibre Channel

22 22 Hyper-V Setup And Networking 1

23 23 Hyper-V Setup And Networking 2

24 24 Hyper-V Setup And Networking 3

25 Windows Server 2008 Each VM On Its Own Switch… VM 2VM 1 “Designed for Windows” Server Hardware Windows hypervisor VM 3 Parent Partition Child Partitions User Mode Kernel Mode Ring -1 Mgmt NIC 1 Mgmt NIC 1 VSwitch 1 NIC 2 VSwitch 1 NIC 2 VSP VSwitch 2 NIC 3 VSwitch 2 NIC 3 VSwitch 3 NIC 4 VSwitch 3 NIC 4 Applications VM Service WMI Provider VM Worker Processes Windows Kernel VSC Windows Kernel VSC Linux Kernel VSC VMBus

26 26 Hyper-V Network Configurations Example 2 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

27 27 Hyper-V Setup, Networking And iSCSI

28 Windows Server 2008 Now With iSCSI… VM 2VM 1 “Designed for Windows” Server Hardware Windows hypervisor VM 3 Parent Partition Child Partitions User Mode Kernel Mode Ring -1 Mgmt NIC 1 Mgmt NIC 1 iSCSI NIC 2 VSP VSwitch 1 NIC 3 VSwitch 1 NIC 3 VSwitch 2 NIC 4 VSwitch 2 NIC 4 Applications VM Service WMI Provider VM Worker Processes Windows Kernel VSC Windows Kernel VSC Linux Kernel VSC VMBus

29 29 Networking Parent Partition

30 30 Networking Virtual Switches

31 31 VM With Legacy And Synthetic NIC

32 32 Don't forget The ICs! Emulated versus VSC

33 33 Hyper-V Laptops And Demo Configs And Consideration

34 34 Hyper-V And Laptops No support for wireless networking Can’t sleep/hibernate system Use multiple spindles Disk for system Disk for virtual machines Intel Note: Santa Rosa Chipset and later Supports 4 GB and greater

35 35 Disk 1, Partition 1: ~70 GB Vista SP1 RTM Hyper-V Laptop Configuration Disk 2, Partition 1: ~65 GB Virtual Machines Laptop Disk 1: Two Partitions Vista SP1 & Windows 2008 Disk 2: Two Partitions VMs & Storage Disk 1, Partition 2: ~24 GB Windows Server 2008 x64 Edition Disk 2, Partition 2: ~84 GB StorageISOs

36 36 Inexpensive Dev/Demo System Single Proc Quad Core 2.4 GHz 300 GB Drive DVD-RW Burner 1 Gb NIC $700 8 GB DDR2 800 MHz $ GB SATA disks $200 ($99 x 2) Total: $1050

37 37 Creating Virtual Machines Steps 1.Create virtual machine 2.Install guest operating system 3.Install integration components 4.Install anti-virus 5.Install management agents 6.SYSPREP 7.Add it to the SCVMM Library Windows Server 2003 Create vms using 2-way to ensure an MP HAL

38 38 Microsoft System Center

39 39 System Center Hardware Provisioning Workload Provisioning PatchingMonitoring Disaster Recovery Backup Virtual machine management Server consolidation and resource utilization optimization Conversions: P2V and V2V Virtual machine management Server consolidation and resource utilization optimization Conversions: P2V and V2V Patch management and deployment OS and application configuration management Software upgrades Patch management and deployment OS and application configuration management Software upgrades Live host level virtual machine backup In guest consistency Rapid recovery Live host level virtual machine backup In guest consistency Rapid recovery End to end service management Server and application health monitoring and management Performance reporting and analysis End to end service management Server and application health monitoring and management Performance reporting and analysis

40 40 What About… Heterogeneous Virtualization Management Physical to Virtual Conversion (P2V) Virtual to Virtual Conversion (V2V) Virtual Server to Hyper-V VMware to Hyper-V Virtual Machine Library PowerShell Scripting Delegated Administration Virtual Machine Authoring VM Templates/Cloning Failover Cluster Integration

41 41 Virtualization Comparison

42 42 Virtual Server 2005 versus Hyper-V Virtualization Feature Virtual Server 2005 R2 Hyper-V 32-bit Virtual MachinesYes 64-bit Virtual MachinesNoYes Multi Processor Virtual MachinesNoYes, 4 core VMs Virtual Machine Memory Support3.6 GB per VM64 GB per VM Managed by System Center Virtual Machine Manager Yes Support for Microsoft Clustering ServicesYes Host side backup support (VSS)Yes Scriptable / ExtensibleYes, COMYes, WMI User InterfaceWeb InterfaceMMC 3.0 Interface

43 43 Microsoft Virtualization… Microsoft Provides a Multilevel Approach Infrastructure Management Applications Interoperability Management Unified Physical and Virtual Virtual Machines Virtual Only MigrationQuick Migration WAN Disaster Recovery Live Migration ($$) Local Disaster Recovery ($$) Guest Multi-processing2/4-core support (free)2/4-core ($$) Large Memory Support64 GB per VM Architecture Supportx86 & x64 Hyper-V VMWare ESX 3.5 Server

44 Microsoft Roadmap Windows® Server RTM Hyper-V Release Within 180 days of Windows Server 2008 RTM System Center Virtual Machine Manager 2008 System Center Virtual Machine Manager 2008 Beta Adds support for managing Hyper-V Adds support for managing VMware Windows® Server Hyper-V RC Windows Server Hyper-V Beta With Windows Server 2008 RTM System Center Virtual Machine Manager 2007 Support for Virtual Server System Center Operations Manager 2007 System Center Configuration Manager 2007 System Center Data Protection Manager 2007 Virtual Server R2 SP1 Now

45 45 Microsoft Virtualization APIs Virtual Server COM Interface us/library/bb309134(VS.85).aspx Virtual Hard Disk Format ver/techinfo/vhdspec.mspx Beta Hyper-V WMI Provider APIs us/library/cc136992(VS.85).aspx Beta Hyper-V Hypercall Interface =91E2E518-C62C-4FF2-8E50-3A37EA4100F5&displaylang=en

46 46 Online Resources Microsoft Virtualization Home Windows Server Virtualization Blog Site Windows Server Virtualization TechNet Site virtualization.mspx Windows Server 2008 Hyper-V Release Candidate Windows Server 2008 Hyper-V RC Installation Guide install.aspx System Center Virtual Machine Manager 2008 Beta

47 47

48 Tech·TalksTech·Ed Bloggers Live SimulcastsVirtual Labs Evaluation licenses, pre-released products, and MORE! Resources for IT Professionals

49 Resources For virtualization Events Whitepapers Downloads Case Studies Visit:

50 1 Year Subscription! Complete an evaluation on CommNet and enter to win!

51 51 © 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.

52


Download ppt "1 Hyper-V Architecture, Scenarios And Networking Jeff Woolsey Senior Program Manager Windows Virtualization Microsoft Corporation VIR358."

Similar presentations


Ads by Google