Roadmap for Challenging Times System Virtualiztion

Roadmap for Challenging Times System Virtualiztion

Most people thinking VIRTUALIZION as a strategy to CONSOLIDATE systems and reduce cost

System Virtualization Grid Control Plane Virtualized Storage Resources Business Service 1 Business Service 3 Business Service 2 Virtualized Compute Resources Directory Security Policy Virtualized Network Resources Management

Virtualization Benefits Less hardware (multiple systems implemented within a single server) Relatively simple Applications are effectively partitioned from each other no chance of application conflicts Ideal for hosting managed test and development environments or for legacy applications requiring non standard configuration Easily provision new servers

Virtualization Issues Limited return on investment software and support costs are not changed. Does not simplify overall system management number of operating systems remain the same Support - Microsoft will not support Windows running within a VMWare virtual machine. Many ISVs do not currently support this configuration.

Virtualization Issues (continue) May complicate management of environment VMWare ESX uses non-standard device drivers Scalability not suitable for applications requiring high levels of system resource Performance overhead associated with emulation of hardware

How Can Operations Fail the?business Agility Performance Security Cost

What is a Virtual Machine Monitor (VMM)? Software that emulates the underlying computer system. This abstraction is done by a virtual machine monitor. Classes of Virtual-machine Monitor (VMM s) - Based on level of Virtualization Full Virtualization Guest OS is hosted without change VMWare ESX Server. Paravirtualization Changes made to the Guest OS. VMWare Workstation, Disco, UMLinux, User-Mode Linux.

Classes of Virtual-machine Monitor (contd.) - Based on the Platform they are built upon Type I Host platform is the hardware. VMware s ESX Server. Type II Host platform is the host operating system. UMLinux, User-Mode Linux. Hybrid VMWare Workstation.

What is Virtual Infrastructure? Virtualization VMWare IBM LPAR Linux XEN - Microsoft Virtual Server - Sun Container - More to Come. Blade Servers Shared network and SAN connectivity Advance Architecture Infiniband switch More scalable and robust operating systems Storage vitualiztion

The Foundation of Virtual Infrastructure Virtualization takes an application and its operating system and wraps them into a transportable virtual machine Physical Machine Virtual Machine Breaks hardware dependencies Multiple applications on a single system

The Foundation of Virtual Infrastructure Virtualization takes an application and its operating system and wraps them into a transportable virtual machine Physical Machine Application Operating System Hardware Virtual Machine Breaks hardware dependencies Multiple applications on a single system

Windows Support For Partitioning Software Partitions Hardware Partitions App App App App App App NT4 Win2K Win2K3 NT4 Win2K Win2K3 Virtual Server Windows Host OS Win2K3 Volume 32-bit application solution Out of the box consolidation Heterogeneous OS/App consolidation Highly flexible and configurable solution Supported on standard servers Windows Host OS Windows compliant partitionable server Windows compliant server Virtual Server App Hardware partitioning provides physical isolation Software partitions may be used in a partition Enables software partitions and scale up application consolidation on a single server Requires a partitionable server

Server Consolidation Tool Best for Limit Hardware partitioning (HP, IBM, Unisys) Very high-throughput applications Complete isolation of applications Re-sizing partitions requires a reboot Capacity in 4-proc increments Resource Management (WSRM) Medium-high throughput applications Manages resource usage All applications must run on same OS level OS/HW single point of failure Virtualization (Virtual Server) Low-throughput applications Legacy applications More complex management Performance tax

Solaris Containers Container Container { Container <1% Overhead Single OS instance Solaris 10 OS Kernel SPARC or x86

Solaris 10 / Volumes vs DynFS Pools Traditional volumes Partition per filesystem; painful to manage Block-based FS/Volume interface slow, brittle FS FS FS Volume Volume Volume Pooled Storage Filesystems share space; easy to mange Transactional ZPL/DMU interface fast, robust FS (DynPL) FS (DynPL) Storage Pool (DMU/SPA) FS (DynPL)

Tools Dynamic resource allocation Instant provisioning Secure access control API for automation Performance monitoring

Microsoft Virtual Server 2005 (Connectix technology)

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

Virtual Server 2005 Architecture Application Guest OS Virtual H/W Application Guest OS Virtual H/W x86/x64 server 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)

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

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

Virtual Server 2005 Architecture Application Guest OS Virtual H/W Application Guest OS Virtual H/W x86/x64 server Industry-standard device models Intel 440BX motherboard Intel 21141 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

Virtual Server 2005 Architecture Application Guest OS Virtual H/W Application Guest OS Virtual H/W 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. x86/x64 server Supported Guest OS Windows Server 2003 Windows 2000 Server NT 4.0 Server Guest applications: NO rewriting, retraining.

Applications And Drivers 32-bit Application 32-bit Application 64-bit Application 32-bit Windows 64-bit Windows 64-bit Windows 32-bit Drivers 64-bit Drivers 32-bit 64-bit Drivers 32-bit Devices x64 Drivers 32-bit Drivers Devices Devices x64 and Itanium x64 and Itanium systems each require different binary version of 64-bit Windows and 64-bit drivers; Drivers written for x64 work on both AMD and Intel implementations

IBM Micropartitions & LPAR

Optional OpenPower Virtualization* Capabilities Includes: 1 CPU I/O Hosting partition 2 CPUs Linux (SLES 9) 1 CPU Linux (RHEL AS 3) POWER Hypervisor - Static LPAR - Dynamic LPAR (SLSE 9) - Virtual I/O server - Micro-Partitioning with shared processor pools - Requires an HMC console * Function included in Advanced OpenPower Virtualization option planned to be announced and available by 4Q04

Operating system support; AIX 5L, i5/os, and Linux Dynamic LPAR Memory Dynamic LPAR I/O Simultaneous multi-threading Virtual Ethernet & SCSI VLAN N N AIX 5L V5.3 ( 1/10th ) Large Page Support Concurrent Diagnostics PCI Hot-plug Micropartitions Dynamic LPAR Processors AIX 5l V5.2 N i5/os V5R3 SLES 9 RHEL AS 3 N ( 1/10th ( Static N N N N ( (1 ( 1/10th ( Static Static N

VMWare

VMware GSX Server - Hosted Architecture Extend existing Host OS to support virtual machines in addition to applications Installs and runs like an application Use Host OS services to implement virtual I/O devices Highly portable, easy to configure resources

VMware ESX Server - Bare-Metal Architecture Runs directly on hardware Manages resource allocations Strong fault and security isolation Shared data clusterready Virtual SMP for large virtual machines and high performance

Sun Microsystems

Server Virtualization GRANULARIT AT EVER LEVEL: H/W, OS, APPS BUILDING BLOCKS ARE AVAILABLE TODA Increase Utilization from 15% up to 80% A P P S A P P S A P P S A P P A S P P S Containers A P P S A P P S A P P S A P P S Dynamic System Domains Solaris 8 Solaris 9 Solaris 10 Fault Isolation Domain 1 Domain 2 Domain 3 Secure Hardware System

Solaris 10 / Server Virtualization Solaris Zones Zone 0 (global zone: serviceprovider.com) Zone 1 (blueslugs.com) Zone 2 (dot.net) Zone 3 (beck.org) login services web services (Apache 1.3.22, J2SE) (OpenSSH sshd 3.4) enterprise services network services (Oracle 8i, IAS 6) core services (ypbind, automountd) web services (Apache 2.0) network services (BIND 8.3, sendmail) (BIND 9.2, sendmail) core services core services (ypbind, inetd, rpcbind) hme0:1 hme0:2 (inetd, nis_cachemgr ) hme0:3 zone management (zonecfg(1m), zoneadm(1m), zlogin(1),...) core services (inetd, rpcbind, nscd, automountd, snmpd, dtlogin, ldap_cachemgr, sshd,...) remote admin/monitoring (SNMP, SunMC, WBEM) network device (hme0) platform administration (syseventd, devfsadm,...) storage complex

Xen and the Art of Virtualization

Control Management Separation of policy and mechanism Domain0 hosts the application-level management software Creation and deletion of virtual network interfaces and block devices

The Cost of Porting an OS to Xen Privileged instructions Page table access Network driver Block device driver <2% of code-base

UMLinux

UMLinux Structure UMLinux uses ptrace to intercept system calls from the user processes. p t r a c e UM User Process 1 UMLinux Kernel MMU OS Kernel Device Drivers Hardware Process 2 Device Drivers

UMLinux VMM System Structure Guest OS and all applications execute as a single process. The VMM runs as another process. Guest OS s machine dependant code has to be modified to use the VMM interface. - e.g. assembly instructions need to be redirected to the VMM code. Guest app. Guest app. Applications are shielded from the change. Guest OS VMM process Guest machine process UMLinux Kernel Host operating system Host hardware

Relative Performance 1 1 0.9 0.9 0.8 0.8 0.7 0.7 0.6 0.6 0.5 0.5 0.4 0.4 0.3 0.3 0.2 0.2 0.1 0.1 0 Linux Xen VMWare UML 0 Linux Xen VMWare UML SPEC INT2000 score SPEC WEB99 CPU Intensive 180Mb/s TCP traffic Little I/O and OS interaction Disk read-write on 2GB dataset

Concurrent Virtual Machines Multiple Apache processes in Linux vs. One Apache process in each guest OS

Q&A Shlomo@emet.co.il