Microsoft Virtual Server 2005 Technical Overview John Howard, IT Pro Evangelist, Microsoft UK

Agenda Virtual Server 2005 Scenarios Virtual Server Migration Toolkit (VSMT) Virtual Server 2005 Architecture Demonstrations

Agenda Virtual Server 2005 Scenarios Virtual Server Migration Toolkit (VSMT) Virtual Server 2005 Architecture Demonstrations

Microsoft Virtual Server 2005 The most cost-effective virtual machine solution designed for Windows Server 2003 to increase operational efficiency Migration and consolidation Legacy custom applications Legacy custom applications Departmental/branch office servers Departmental/branch office servers Disaster recovery sites Disaster recovery sites Software test/development Consolidation/automation of a centrally managed server farm Consolidation/automation of a centrally managed server farm Simulation of distributed applications/services on a single system Simulation of distributed applications/services on a single system VM Key Benefits: Improved hardware efficiency and increased productivity

Test/Development Scenario No packets hit the production network Uniform regression testing WITH developer flexibility “Dev/Test-in-a-box” Fully-patched suite of test servers deployed from centrally-managed VM library New application/service regression- tested across distributed interactivity prior to staging and production Customer benefit: lower risk, higher quality, faster deployments

Branch Office Scenario “Branch-in-a-box” Single Server in a Branch running various services. File and Print, DC, LOB applications. DC in a virtual machine on a guest operating system with application services running on the host operating system DC on the host operating system with application services running in a virtual machine on a guest operating system DC and applications running in virtual machines on separate guest operating systems with host operating system for administration only

Agenda Virtual Server 2005 Scenarios Virtual Server Migration Toolkit (VSMT) Virtual Server 2005 Architecture Demonstrations

VSMT Scenarios Application Rehosting Allows application to be moved to new hardware for better performance, reliability, and maintainability. Server Consolidation Consolidate multiple physical servers onto a smaller number of physical servers Each of the original physical servers runs in its own Virtual Machine to maintain application isolation, security, and operating system environment VSMT enables both scenarios by automating the migration of the operating system and installed applications from a physical server to a Virtual Server

VS Migration Toolkit “Old” Server W2K3 Server With Virtual Server 2005 & VSMT W2K3 Server with ADS 1.0 & VSMT  Run gatherhw.exe  Move output XML file to ADS controller  Run VMScript.exe to validate HW config and generate custom scripts  Run generated capture.cmd  Manually PXE boot to ADS Deployment Agent, causing image to be captured  Power off old hardware (Automatic)  Run generated CreateVM.cmd, which executes a task sequence to create a Virtual Server on the Virtual Server Host  Run generated DeployVM.cmd, which executes a task sequence to deploy the captured image to the new Virtual Server  Configure VM settings, network and storage configuration & VM additions Task sequence execution

VSMT Toolkit Functionality Migrates physical server to Virtual Server (P2V) Migrates physical server to Virtual Server (P2V) Moves entire operating system and installed applications by moving disk images Moves entire operating system and installed applications by moving disk images Server retains its identity after the move Server retains its identity after the move Actual process takes around an hour per server after the planning and infrastructure setup is complete Actual process takes around an hour per server after the planning and infrastructure setup is complete Targeted for use by IT professionals or by MCS Targeted for use by IT professionals or by MCS Requires some scripting knowledge and Windows Server expertise Requires some scripting knowledge and Windows Server expertise Requires DHCP and ADS infrastructures Requires DHCP and ADS infrastructures

VSMT Prerequisites Microsoft ADS, runs on Windows Server 2003 Enterprise Edition Sufficient disk space on ADS Server to store images of servers during migration process Microsoft Virtual Server 2005 Sufficient resources (memory, disk, network) on the Virtual Server to support migrated systems Virtual Server and VSMT (with ADS) can be on the same box.

VSMT Requirements Physical source machine requirements Operating Systems NT Server 4.0 SP6a Windows 2000 Windows Server 2003 Minimum of 96MB of physical memory installed WMI must be installed and functional Primary NIC must be PXE 0.99c compatible and system must be able to perform a PXE boot, via ROM or RBFG disk

Migration Tips Before you start a migration, always: Verify adequate disk resources are available on the VS Host and ADS Image Servers Verify adequate memory resources are available on the VS Host Have access to a local admin-level account on the machine to be migrated Decide on a retention plan for the physical server and image captures

VSMT Limitations Limitations Servers with hardware not emulated in VS cannot be moved – E.G.: Parallel port dongle, USB, HBAs Physical servers with less than 96MB of memory cannot run migration tools (160MB if FAT partitions) Cannot migrate SAN data - must be copied manually Some hardware configurations will require manual intervention in the migration process, particularly with NT 4.0 Targeted for IT-Pros or consultants Requires some scripting knowledge Requires DHCP, PXE and ADS knowledge

Virtual Server Migration Toolkit Demo

Agenda Virtual Server 2005 Scenarios Virtual Server Migration Toolkit (VSMT) Virtual Server 2005 Architecture Demonstrations

x86/x64 server x86/x64 server Application Guest OS Virtual H/W Virtual Server 2005 Architecture Up to 32 host CPUs Up to 64GB host RAM VS leverages existing system storage, networking and security infrastructure Teamed NICs, teamed HBAs VS Standard Edition Optimized for Windows Server 2003 Standard Edition (2-4P/32GB) VS Enterprise Edition Optimized for Windows Server 2003 Enterprise Edition (<8P/64GB) Support for X64 OS due in Virtual Server SP1 (32bit Guests) Up to 32 host CPUs Up to 64GB host RAM VS leverages existing system storage, networking and security infrastructure Teamed NICs, teamed HBAs VS Standard Edition Optimized for Windows Server 2003 Standard Edition (2-4P/32GB) VS Enterprise Edition Optimized for Windows Server 2003 Enterprise Edition (<8P/64GB) Support for X64 OS due in Virtual Server SP1 (32bit Guests)

x86/x64 server x86/x64 server Application Guest OS Virtual H/W Virtual Server 2005 Architecture VS works with Windows: Heartbeat from kernel/ scheduler Windows Device drivers VS works with Windows: Heartbeat from kernel/ scheduler Windows Device drivers

x86/x64 server x86/x64 server Application Guest OS Virtual H/W Virtual Server 2005 Architecture Virtualisation infrastructure VM monitor COM API Resource management WMI/event log integration Multiple Threaded Support Virtualisation infrastructure VM monitor COM API Resource management WMI/event log integration Multiple Threaded Support

x86/x64 server x86/x64 server Application Guest OS Virtual H/W Virtual Server 2005 Architecture Industry-standard device models  Intel 440BX motherboard  Intel NIC  S3 Trio64 SVGA with 2D hardware acceleration  IDE/ATAPI controller  Adaptec 2940 SCSI controller  Legacy devices  KBD, Mouse, COM, LPT ports. NO custom drivers in guest Industry-standard device models  Intel 440BX motherboard  Intel NIC  S3 Trio64 SVGA with 2D hardware acceleration  IDE/ATAPI controller  Adaptec 2940 SCSI controller  Legacy devices  KBD, Mouse, COM, LPT ports. NO custom drivers in guest

x86/x64 server x86/x64 server Application Guest OS Virtual H/W Virtual Server 2005 Architecture Guest OS: Runs all major x86 OSes 3.6GB RAM 4 NICs 56.5TB storage (IDE -SCSI) 2-N failover MSCS clustering VM to VM same VS Host Server SCSI limits cluster size ISCSI will support more cluster nodes and VM to VM clusters across hosts. Supported Guest OS Windows Server 2003 Windows 2000 Server (NT 4.0 Server ) Guest applications: NO rewriting, retraining. Guest OS: Runs all major x86 OSes 3.6GB RAM 4 NICs 56.5TB storage (IDE -SCSI) 2-N failover MSCS clustering VM to VM same VS Host Server SCSI limits cluster size ISCSI will support more cluster nodes and VM to VM clusters across hosts. Supported Guest OS Windows Server 2003 Windows 2000 Server (NT 4.0 Server ) Guest applications: NO rewriting, retraining.

Virtual Server 2005 Components The Virtual Server 2005 user Interface is Web-based and has two components The Web Server – a CGI file uses the VS COM API to create the UI content The Administration Interface – a standard browser that displays the UI These components can reside remotely or locally to the VS service Can use HTTPS to communicate to web service VM user interaction is remoted using a Virtual Machine Remote Control (VMRC) link Uses NTLM or Kerberos authentication VS Service Web Server Administrative Interface VMRC HTTPS HTTPS DCOM DCOM VM 1 VM 2 VM 3 IIS Service Virtual Server CGI Internet Explorer VMRC Client

CPU resource allocation policies max: 20% min: 5% wt: 100 max: 20% min: 10% wt: 100 max: 50% min: 25% wt: 100 Web server Business logic Database VMVMVM Workload management features Weighting policy enforces database SLA Weighting policy enforces database SLA vis-à-vis other VMs Minimum reserve policy: other VMs not CPU-starved  balanced workload Recommend reserve 1 CPU for VS host

1GB Total RAM: 4GB 512K 1.5GB Web server Business logic Database VMVMVM Memory features in action No memory overcommit: running VMs’ RAM cannot exceed physical RAM Dynamic memory add/delete not currently supported Recommend 512MB VS host + 15MB for VS service

Virtual Disk Drives IDE Up to four IDE drives (128GB per drive) SCSI Up to four SCSI controllers Up to seven drives per controller (2TB max per drive) Maximum 56 TB per VM.VHD files on host Created using Virtual Disk Manager

Virtual Disk Drives Dynamically expanding Fixed size Difference drive Read only parent file Changes written to a difference file Linked drive – Uses a physical drive Undo capability Saves all drive updates in special case, difference drives Updates committed or discarded at shutdown

Virtual Disk Drives Base virtual hard disk types Dynamically expanding vhds Default type: grows as needed Fixed size virtual hard disksHighest performance type Linked virtual hard disksLinks a physical data disk to a virtual hard disk State drive types Undo virtual hard disksNon-persistent, per-VM Differencing virtual hard disks Persistent parent-child hierarchy Saved statesFlush memory to disk (like hibernation) Host Guest Host 2TB 1GB 2TB 2TB HostGuest VMHost Base SP1SP2 Base Session

Virtual Networks (VNs) Virtual networks with no NIC connected (Guests Only) All routing is performed local to Virtual Server A virtual DHCP server provides IP addresses to VMs on the network VM1 Physical 1 VM2VM3 Physical 2 Default Networks User created Networks Example VM1 – the default internal and NIC1 networks VM2 – new internal network created; connects to it and the default NIC2 network VM3 – the default internal network, the NIC1 network and the new internal network Internal User Max four Virtual Networks per VM Default installation One per physical NIC One with no NIC (Internal) Create your own

Virtual Networking features Private virtual network Virtual NICS Virtual NICs Virtual Networks in action Hardware server Private internal network Public external network Virtual DHCP Server Web server Business logic Database VMVMVM Virtual Switch

Virtual Server Manageability Microsoft Operations Manager 2005 with the Management Pack for Virtual Server 2005 provides industry-leading Windows health and performance monitoring capabilities—a familiar interface that your staff already knows. Microsoft Automated Deployment Services—included with Windows Server 2003 Enterprise Edition— provides a powerful unified interface for automated provisioning and deployment of both host and guest Windows OSes.

Summary Scenarios Test & Development RehostingFlexible Capable of complex modelling scenarios Manageable VMRC/Admin Interface remote control Resource management Scripting Microsoft Operations Manager Management Pack

© 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.

Microsoft Virtual Server 2005 Technical Overview John Howard, IT Pro Evangelist, Microsoft UK