1 / 95

IT Virtualization Boot Camp Saskatoon, March 30-31, 2012

IT Virtualization Boot Camp Saskatoon, March 30-31, 2012. Mitch Garvis, MCT, VCP Virtual Partner Technology Advisor, Microsoft Canada Senior IT Pro & Trainer, SWMI Consulting Group mitch@swmi.ca Twitter: @ MGarvis / Blog: www.garvis.ca http://blogs.technet.com/b/canitpro.

moira
Download Presentation

IT Virtualization Boot Camp Saskatoon, March 30-31, 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IT Virtualization Boot CampSaskatoon, March 30-31, 2012 Mitch Garvis, MCT, VCP Virtual Partner Technology Advisor, Microsoft Canada Senior IT Pro & Trainer, SWMI Consulting Group mitch@swmi.ca Twitter: @MGarvis / Blog: www.garvis.ca http://blogs.technet.com/b/canitpro

  2. IT Virtualization Boot CampCincinnati, April 28, 2012 Mitch Garvis, MCT, VCP Virtual Partner Technology Advisor, Microsoft Canada Senior IT Pro & Trainer, SWMI Consulting Group mitch@swmi.ca Twitter: @MGarvis / Blog: www.garvis.ca http://blogs.technet.com/b/canitpro

  3. Goals for today • PrepareWindows Server-based computers for virtualization • Configure an iSCSI storage server • Create a Windows Failover Cluster • Make Hyper-V virtual machines highly available • UseLive Migration to move running workloads between hosts with no loss in client connectivity • Integrate non-Microsoft-based virtual machines into your cluster • See how Windows Failover Clustering can help to make dealing with hardware failure easier

  4. Prerequisites • Understanding and ability to manage • Windows Server 2008 R2-based hosts • Active Directory Domain Controllers • Networking on Windows-based computers

  5. Microsoft Virtualization Platform

  6. 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

  7. Virtual Machine Overview VMs or “Guests” • Virtual Machine components • Memory • Virtual processors (compute) • Network Adapters (network) • Virtual Disks (storage) • VM guest OS • Windows Server 2008 and Windows Server 2008 R2 • Windows Server 2003 SP3 and Windows Server 2003 R2 SP3 • Windows 2000 Server SP4+ • Windows Home Server 2011, Small Business Server 2011 • Windows 7, Windows Vista and Windows XP SP2+ • CentOS 5.2+, Redhat 5.2+ and SUSE Linux Server 10 SP4+ • Full list: http://technet.microsoft.com/en-us/library/cc794868(WS.10).aspx Host Server

  8. Hyper-V Architecture

  9. Requirements and Limits Host computer components Virtual machine components

  10. Hyper-V Editions

  11. 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 • SUSE Linux Enterprise Server 10/11 • RHEL 5.2/5.3 • CentOS

  12. Apps Running Inside the Guest • See KB 957006 for more information

  13. Hardware & BIOS • X64 Hardware Assisted Virtualization • AMD Virtualization (AMD-V) • Intel Virtualization Technology (Intel VT) • Hardware enabled Data Execution Prevention (DEP) required • AMD (NX no execute bit) • Intel (XD execute disable) • Second Level Address Translation (SLAT) • AMD Nested Page Tables (NPT) or Rapid Virtualization Indexing (RVI) • Intel Extended Page Tables (EPT) • Hyper-V does not support Itanium (IA-64) processors • Must use 3rd party hypervisor Enabled from the BIOS

  14. Enabling Hyper-V • Hyper-V is enabled as a server role (restart required) • Hypervisor must be enabled and running to start virtual machines • Verify the status of the Hyper-V Virtual Machine Management Service

  15. Enabling by Server Manager • Server Role

  16. Enabling by CLI (Server Core) • CMD • > DISM /online /enable-feature /featurename:Microsoft-Hyper-V • > start /w ocsetup Microsoft-Hyper-V • PowerShell • > Add-WindowsFeature Hyper-V • Server Manager GUI available with remote management

  17. Enabling on Hyper-V Server • Hyper-V enabled automatically!

  18. Configuring Virtual Networks • Configured from Virtual Network Manager • External Networks • VMs can communicate with other computers on the network • Only 1 per physical NIC • Internal Networks • VMs can communicate with only other VMs on the same host, and with the host computer • Private Networks • VMs can communicate only with other VMs on the same host

  19. Enabling Virtualization Configuring Hyper-V Role Resources: • Enable Hardware settings in BIOS to run Hyper V • Getting to Know Hyper-V: A Walkthrough from Initial Setup to Common Scenarios • Install the Hyper-V Role on a Full Installation of Windows Server 2008 • Configuring Virtual Networks

  20. Managing Hyper-V

  21. Hyper-V Manager

  22. VM Connection Application • Is used to manage localor remote virtual machines • Is installed with Hyper-Vor RSAT • Uses RDP on port 2179 • Uses the mstsc.exe Active X control • Requires port 2179open on Windows Firewall

  23. Remote Server Admin. Tools • RSAT allows server management on Client • Connect to Hosts • Free download: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=7887 • Must enable feature on Client • Select Role Administration Tools • Select Hyper-V Tools

  24. Remote Desktop Connection Manager • Remote desktop connection management at scale • Connect to hosts or VMs • Runs on Server & Client • Free download: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=21101

  25. Remote Connections • Remote Desktop Protocol • Launch MSTSC(.exe) • Connect to Hosts or VMs • Hyper-V Manager • Right-click Hyper-V Manager • Select “Connect to Server…” • Connect to hosts • Similar experience with RSAT

  26. RemoteFX Support • New in Windows Server 2008 R2 SP1 • 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 26

  27. Dynamic Memory • Hyper-V memory enhancement in Windows Server 2008 R2 SP1 • Higher VM consolidation ratios on same hardware with minimal performance impact • Memory is pooled and dynamically distributed across VMs to allow it to easily grow or shrink with no service interruption • Active Memory addition • Memory is added immediately when VM needs it • Passive Memory reclamation • Unutilized memory is collected every 5 minutes • Supports both server and desktop • VM Guests are enlightened • Guest Integration Components installed • Must be updated to SP1 • Memory is added and removed via synthetic memory driver (memory VSC) support

  28. Dynamic Memory Settings • Startup RAM: Memory needed to boot VM • Guest OS + Apps • Default: 512MB • Maximum RAM: Memory limit 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 are allocated memory • Range: 1 (highest) - 10,000 • Default: 5,000

  29. Root Memory Reserve • Root memory reserve is kept for the parent partition • Host Reserve amount is automatically calculated based on SLAT capability, total size of host RAM, NUMA architecture • New registry key override added • Allows you to reserve static memory for the parent partition • May result in less memory being available for VMs • DM allows VMs to push up against the reserve consistently • New behavior better protects parent partition from VMs taking too much memory Host Reserve VM Overhead Memory utilized by VMs VM Reserve

  30. Import Virtual Machines Configure VM Memory Settings Configure VM Startup Options

  31. Join VM Hosts to ITCAMP Domain

  32. Hyper-V Storage

  33. Host Computer with VHDs • Implement storage solutions with multiple hard drives to distribute disk I/O • Use fast hard drives • Consider deploying a SAN for VHD storage • Implement iSCSI SANs for a less expensive storage solution • Avoid scanning virtual hard disk files with anti-virus software

  34. Storage • Virtual machines require storage for Virtual hard disk files, snapshots, Failover Clustering, and the application’s data files • Physical • DAS (SATA, eSATA, PATA, SAS, SCSI, USB, Firewire) • SAN (Fibre Channel, FCoE, iSCSI, SAS) • Required for Failover Clustering so all nodes can access a disk • Host Clustering: Fibre Channel, FCoE, Serial-Attached SCSI (SAS), iSCSI • Guest Clustering: iSCSI • Virtual Adapters • IDE, SCSI • Boot – IDE only • VHD • Fixed, dynamic, differencing • Pass-through • iSCSI Direct (Applicable to running iSCSI in guest OS)

  35. IDE SCSI Storage Options for Virtual Machines • Two IDE controllers • Two devices each • Methods supported • Pass-through • Fixed-disk • Dynamic • Emulated/synthetic • Must be used for boot partition • Four SCSI controllers • 256 devices each • Methods supported • Pass-through • Fixed-disk • Dynamic • Synthetic

  36. Creating VHDs • Use the Virtual Disk Wizard • Disk Type: Fixed, Dynamically Expanding, Differencing • Name & Location • Configure Disk: Size, Contents can be copied from another location • Configuration can be changed using the VM settings • IDE Controller(s) & Location • SCSI Controller(s) & Location • Media: VHD, Physical hard drive • Diskette Drive

  37. Choosing VM Locations • VM Storage • VHDs: C:\Users\Public\Documents\Hyper-V\virtual hard disks • VMs (configuration): C:\ProgramData\Microsoft\Windows\Hyper-V • Virtual Machines • Snapshots • Considerations • Performance • Hard Drive Space • Security • Shared Storage for Failover Clustering

  38. Hot Add/Remove Storage • Overview • Add 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 • Benefits • Enables storage growth in VMs without downtime • Enables additional datacenter backup scenarios • Enables new SQL/Exchange scenarios

  39. Microsoft iSCSI Software Target • iSCSI is a cheap SAN solution • Support Failover Clustering • Required for Guest Failover Clustering • Uses the existing IP network • Can be a storage array or DAS on a server • Free download: http://www.microsoft.com/download/en/details.aspx?id=19867

  40. iSCSI Initiator • Initiator connects to the iSCSI Target • Target must be configured • Should use a dedicated NIC • Can use any iSCSI Target

  41. Configuring iSCSI • Target: Create virtual disks • Initiator(s): Request access to disks • Target: Accept access request from initiator(s) • Initiator(s): Refresh configuration to check connection • Initiator(s): Login to the target • Enable automatic reconnections • Servers: Initialize, format and bring disks online • Now you can use these disks for your VMs or cluster

  42. Configure iSCSI Target Create iSCSI LUN & VHDs Connect Hosts to iSCSI LUN Resources: • Creating a SAN using Microsoft iSCSI Software Target 3.3

  43. Windows Failover Clustering

  44. Failover Clustering & Hyper-V • VM High-Availability • Automatic failover & recovery • Hardware health detection • Host OS health detection • VM health detection • Application/service health detection • VM Mobility • Live migration • Quick migration • Failover • Deployment Flexibility • VM not bound to a single host

  45. Failover Clustering SKUs • Windows Server 2008 R2 • Enterprise • Datacenter • Itanium • Microsoft Hyper-V Server 2008 R2 • FREE Host OS – Download it today! • Built on Server Core for even higher availability from fewer updates • Failover Clustering, Hyper-V, CSV, Live Migration • More information: http://www.microsoft.com/hvs * Itanium requires a 3rd party hypervisor

  46. Failover Clustering Basics • Deploy redundant hardware everywhere • “Shared” storage accessible by all nodes • Clustered application writes data to shared storage so all nodes can assess it • A registry hive containing current cluster configuration information is replicated to each node • Nodes monitor the health of other nodes • If a node fails, the health check will fail, and a failover will happen • Another node knows what the failed node was hosting through the registry and start that application • The application reads its saved data from the shared storage • Client connects to app on new node • Clients may experience a slight interruption in service during failover but none during a live migration (of a VM)

  47. Simulated Failover Public Shared Storage VMs & Workloads

  48. Cluster Storage Fibre Channel (FC) Fibre Channelover Ethernet (FCoE) Serial-Attached SCSI (SAS) iSCSI • Requires a Storage Area Network (SAN) • SCSI-3 Commands • Basic GPT and MBR disks supported • Multipath IO (MPIO) recommended • Persistent Reservations (PRs) required

  49. Cluster Networking • Integrated with Windows Server TCP/IP Stack • Multiple networks for added redundancy • Separate networks by function • Public Network • Internal Cluster Network (health checks, cluster communication) • Hyper-V Live Migration & Management • Storage (iSCSI, FCoE) • Backup • IPv4, IPv6 & IPv6 Tunneling • DHCP or Static IP Addresses

  50. Guest Clustering Host Clustering Host vs. Guest Clustering • Cluster service runs inside (physical) host and manages VMs • VMs move between cluster nodes • Cluster service runs inside a VM • Apps and services inside the VM are managed by the cluster • Apps move between clustered VMs Cluster Cluster SAN iSCSI

More Related