Red Hat Enterprise Linux 5 Virtualization Best Practices

Reviews

Tags

Red Hat Enterprise Linux 5 Virtualizatio..., Red Hat, Red Hat Enterprise Linux, open source, Enterprise Linux, the Red Hat, Red Hat Linux, Enterprise Middleware, Red Hat Network, Red Hat Enterprise

Stats

views:: 265
rating:: not rated
reviews:: 0
posted:: 7/30/2009
language:: English
pages:: 0

Public Domain

Red Hat Enterprise Linux 5 Virtualization Best Practices Jan Mark Holzer (jmh@redhat.com) D. John Shakshober (dshaks@redhat.com) Red Hat Outline • Supported Configurations Red Hat Enterprise Linux − Guest / HyperVisor Support − Guest Operating Systems • Best Practices − Guest Configuration Limits and Sizing − Infrastructure & Management − Performance • Q&A Guest/Hypervisor Matrix (RHEL5.2) 32bit PAE paravirt Guest 32bit (PAE) Hypervisor / dom0 64bit Hypervisor / dom0 32bit HVM Guest 64bit paravirt Guest 64bit HVM Guest  For Paravirtual, the guest has to be equal to dom0  Limited support for 32bit on 64bit dom0 (no pause/save/migration)     For HVM, the guest has to be equal or less than dom0 RHEL5/Virt Hypervisor itself must be EQUAL to dom0 Can install para-virt drivers for 32bit and 64bit guests for improved performance Support for 32bit para-virt drivers on 64bit HyperVisor/dom0 Preliminary RHEL 5.1 Virtualization Matrix Host Kernel & Processor Architecture Guest Operating System Supported Enterprise Linux Combinations Red Hat Enterprise Linux 3 x8664 FV Red Hat Enterprise Linux 3 x8632 FV Red Hat Enterprise Linux 3 IA64 FV Red Hat Enterprise Linux 4 x8664 PV Red Hat Enterprise Linux 4 x8664 FV Red Hat Enterprise Linux 4 x8632 PV Red Hat Enterprise Linux 4 x8632 FV Red Hat Enterprise Linux 4 IA64 PV Red Hat Enterprise Linux 4 IA64 FV Red Hat Enterprise Linux 5 x8664 PV Red Hat Enterprise Linux 5 x8664 FV Red Hat Enterprise Linux 5 x8632 PV Red Hat Enterprise Linux 5 x8632 FV Red Hat Enterprise Linux 5 IA64 PV Red Hat Enterprise Linux 5 IA64 FV Windows Server 2000 32Bit Windows Server 2000 64Bit Windows Server 2000 IA64 Windows Server 2003 32Bit Windows Server 2003 64Bit Windows Server 2003 IA64 Windows XP 32Bit Windows XP 64Bit Windows Vista 32Bit Windows Vista 64Bit Optimized2 Optimized N/A Optimized Optimized2 3 2 x8664 x8632 PAE N/A Optimized N/A N/A N/A Optimized2 N/A N/A N/A N/A 3 2 IA64 N/A N/A Supported N/A N/A N/A N/A Optimized Supported N/A N/A N/A N/A Optimized Supported 1) Red Hat Enterprise Linux 2.1 curently is not generally supported to be run as a guest on Red Hat Virtualization. 2) PV FV ParaVirtualized: Guest kernel optimized for virtualization. FullyVirtualized: Unmodified guest kernel, requires virtualization hardware support. Supported and PV or optimized PV drivers provided. Supported but no optimized PV drivers available. Not supported and may not work. Not a valid combination. Technically possible, but not yet supported. Tech Preview Optimized Optimized2 N/A N/A Optimized Optimized Optimized N/A N/A Supported N/A Supported N/A Supported Supported Supported 4 5 4 4 5 2 Optimized Supported Unsupported N/A Tech Preview Tech Preview Optimized 2 Optimized N/A N/A Supported N/A N/A Supported N/A N/A Supported N/A Supported N/A 2 Optimized PV drivers for Enterprise Linux 3,4, and 5 are currently being beta Supported 3rd Party Operating Systems 4 tested and will be released within the next couple of months. N/A N/A Supported 4 3) Unsupported Support for paravirtualized x8632 guests on a x8664 host environment is planned to be fully supported in Enterprise Linux 5.2. 4) Red Hat is actively working an optimized PV drivers for Windows guests. These drivers will lead to a significant improvement in the performance of Windows guests and move the support level to “Optimized”. Red Hat will announce details on the availability at later point in time. 5) N/A N/A Supported Unsupported5 4 N/A N/A N/A N/A Unsupported 4 4 64Bit Windows guests have not been tested and considered lower priority than 32Bit guests due to a lack of visible adoption. Red Hat plans to add support at a later point in time. 4 Best Practices Basic Information and Hints Prerequisites for RHEL5/Virt  Plan your hardware/software architecture well ahead  Servers to be deployed (use of HVM, IO, Memory, CPU)    For live migration use same server vendor Migration will work from old to new , but can fail from new to old Multiple network cards/connections for management, migration and application traffic Shared storage for ease of management and migration Consider IO demands Unified namespace for shared directories (guests, config files)  Usually not a good idea to share /etc/xen as it includes system specific files  Rather share config files via softlinks from a common location Unique volume group names for guest deployment  Allow for mounting the guest file based image on the host/dom0  Storage Infrastructure (FC, iSCSI, NFS, NetAPP)    Naming conventions, filesystem layout    Take some time and read the Virtualization Guide and associated docs Prerequisites for RHEL5/Virt  Always use RHEL5.1/5.2 Virt (matching) packages, DO NOT install Xen RPMs from XS !!  If you need to “add” virtualization capabilities after the initial installation always use # yum groupinstall Virtualization to install packages to track dependencies VNC for remote desktop access VSFTP for access to local/remote para-virt installation tree  Install VNC and VSFTP packages    At least 2GB of memory for a “working” system  Plan at least a minimum of 512MB-1024MB for dom0  See sizing guidelines later on for fully-virt/para-virt environments Guest Sizing and Limits  RHEL 5.0  i686    dom0/HV Para-virt guest Fully-virt/HVM guest dom0/HV Para-virt guest Fully-virt/HVM 32 cpus, 16GB memory 32 cpus, 16GB memory 1 cpu, ~2GB memory 32 cpus, 512GB memory (tested) 32 cpus, 80GB memory (tested) 1 cpu, theoretically unlimited memory  x86_64     RHEL 5.1  i686    dom0/HV Para-virt guest Fully-virt/HVM guest dom0/HV Para-virt guest Fully-virt/HVM guest 32 cpus, 16GB memory 32 cpus, 16GB memory >1 cpus, > 4GB memory 32 cpus, 512GB memory 32 cpus, 80GB memory >1 cpus, theoretically unlimited memory  x86_64    Guest Sizing and Limits  RHEL 5.2  i686    dom0/HV Para-virt guest Fully-virt/HVM guest dom0/HV Para-virt guest Fully-virt/HVM 32 cpus, 16GB memory 32 cpus, 16GB memory > 1 cpus, > 4GB memory 64 cpus, 512GB memory 32 cpus, 80GB memory > 1 cpus, theoretically unlimited memory  x86_64    Guest Sizing and Limits  Networking limits    Until RHEL5.1 only 3 NICs could be configured inside a guest RHEL5.2 has lifted the limited Network throughput for fully-virt/HVM guests will be limited to 100Mb/s.  It can be improved by installing the para-virt drivers for fully-virt/HVM RHEL/Windows guests The number of devices which can be configured inside a guest are depending on the underlying storage emulation used xvdX for para-virt drivers/guests (preferred for all virtualization models)  Up to 16 devices hdX for fully-virt/HVM guests  Up to 4 devices (if no CDROM in use) sdX for scsi emulation (not recommend due to low performance)  Up to 16 devices  Storage limits     High Level RHEL5/Virt Architecture for para-virt guest domU/Guest domU/Guest PV Driver dom0 /root Frontend /data Frontend /data Frontend /root Frontend Back End Virtual CPU & Memory Device Driver Hypervisor Physical Hardware High Level RHEL5/Virt Architecture for HVM guest domU/Guest domU/Guest QEMU /root Frontend /data Frontend /data Frontend /root Frontend dom0 Back End qemu-dm Virtual CPU & Memory Device Driver Hypervisor Physical Hardware High Level RHEL5/Virt Architecture for HVM guest with PV drivers for block and network domU/Guest domU/Guest PV Driver QEMU /root Frontend /data Frontend /data Frontend /root Frontend dom0 Back End qemu-dm Virtual CPU & Memory Device Driver Hypervisor Physical Hardware Fully-Virt/HVM Guest Considerations  HVM guests can incur a significant overhead for IO (net and storage) operations depending on workloads deployed  This overhead can largely be eliminated by installing para-virtualized drivers  PV drivers are available for RHEL3, RHEL4 and RHEL5 based guests  The Windows PV drivers will be available for RHEL5.2  The PV drivers are installed on RHEL using a RPM package  After the installation network traffic and any user data disks (non-system disk) can use the PV driver  On RHEL5.1 a manual step is required, fixed in RHEL5.2  To activate the PV drivers for networking simply remove the “type=ioemu” in the “vif=” section of the guest config file  Additional file based images to be used as virtual block devices should be added using the “tap:aio” option in the guest's “disk=” section of the guest's configuration file  If you are using a physical disk/partition/volume use “phy:” instead of “tap:aio” Fully-Virt/HVM Guest Considerations  If you are runnning a HVM guest on RHEL5.1 and if your workload will generate large amounts if IRQs/Interrupts, you should consider adding the option “NOAPIC” to the guest kernel boot line As of RHEL5.1 you can also use PXE boot for fully-virt/HVM guests   Add the option “boot=n' to your guest configuration file to enable PXE boot Planning and basic sizing for RHEL5/Virt Memory Configuration  Consider 512MB-1024MB for dom0/Hypervisor   If only para-virtualized guests in use can use small footprint for dom0 (<1024MB / = 512MB) If HVM/fully-virt guests in use plan on adding appr 128MB per guest and start with 1024MB for dom0 More memory will speed up the installation process 256MB may potentially cause installation failures  Use at least 512MB of memory for guest installations    Consider “wiring” dom0 to a fixed amount of memory (can always balloon down to minimum memory)  Add dom0_mem=XXXMB to the “kernel /xen.gz....” line   ie dom0_mem=1024MB to configure dom0 with 1024MB of memory at startup Minimum amount of memory is controlled via dom0-min-mem in /etc/xen/xendconfig.sxp Planning and basic sizing for RHEL5/Virt vCPU Configuration   Best performance if the number vCPUs is equal or less than physical CPUs However consolidation being a key feature of virtualization , need to driver vCPU count beyond physical CPU count Very basic rule (SWAG) is to start with ~4 vCPUs per pCPU    Assumption is that average environments are running at 15-20% utilization very optimistic guess, most environments run well below 15% average utilization Most workloads don't benefit from CPU pining CPU pining can not be resolved without rebooting the guest  RHEL5/Virt allows to “pin” vCPUs to physical CPUs   Planning and basic sizing for RHEL5/Virt Storage Configuration  RHEL5/virt supports all common storage models     Fiberchannel, iSCSI, NFS/Netapp Performance best with Fiberchannel, next iSCSI on dom0 and then NFS/Netapp Live migration will require shared storage for virtual machines (FC. iSCSI,NFS) If FC/iSCSI are used make sure to use udev rules to keep/make device names consistent across servers  Can use iSCSI inside a guest , but performance may not be optimal, better to use iSCSI in dom0 and pass device as vbd into guest Use Red Hat Clustering for more robust error handling and fencing Guest installation “image” will include encapsulated swap space      Will drive image/partition/volume size up Good starting point is 5GB If addtl packages/debug RPMs are used might consider 10GB Planning and basic sizing for RHEL5/Virt Storage Configuration  Performance Considerations      For file based guest images always use non-sparse files for best performance and data integrity Using a sparse file can result in performance degradation of 3x If you are using a physical device/partitions/LUN/LVM volume use the “phy:” option in your guest config file If you are using a file based guest use the “tap:aio” option If no PV drivers are used but only “/dev/hdX” you may want to consider using the “# hdparm -W 0 /dev/hdX” command to disable caching in dom0 I/O virtualization Virtual Machine 1 Virtual Machine 2 Virtual Machine 3 RHEL5 Virt Platform Physical Disks File Containers Partition(s) Logical Volumes ISO Images CD/DVD Drive SAN Storage Arrays SAN SAN Dynamic I/O Sharing Virtual Machine 1 Virtual Machine 2 Virtual Machine 3 vHBA vHBA vHBA Virtual server’s I/O packets directed to I/O cards by the HyperVisor/dom0 RHEL5 Virt Platform I/O card can be “dedicated” to a virtual machine for performance isolation Dynamic Network I/O Sharing Virtual Machine 1 Virtual Machine 2 Virtual Machine 3 vNIC vNIC vNIC vNIC vNIC Virtual machine’s network packets directed to physical NIC by the HyperVisor/dom0 Virtual NIC may be defined without a physical NIC for guest-to-guest communication NIC can be “dedicated” to a virtual machine for performance isolation Virtual Bridge NIC 1 Virtual Bridge DMZ Virtual Bridge NIC 2 RHEL5 Virt Platform Infrastructure & Management RHEL5 Technical Overview / June 2008 Product features subject to change prior to availability 23 Management Tools for RHEL5/Virt Numerous tools are available to manage virtual machines in a RHEL5/Virt environment  Red Hat developed and integrated tools  virt-manager, virsh, virt-install, cobbler/koan  virt-tools  virt-p2v,virt-top,nagios-virt  Red Hat Network Satellite   3rd party products and tools Scalent  Enomalism   OpenSource tools Nagios  Munin  RHEL5/Virt Tools http://et.redhat.com/~jmh/virt-tools/  Building tools to close immediate holes (but use them for longer term solutions) virt-top   Performance monitoring using a 'top' like tool Convert physical to virtual instances Integration of virtual machine monitoring into Nagios Convert an existing Vmware image/disk into a RHEL5/Virt image Provisioning of guests using PXE style  virt-p2v   nagios-virt   virt-v2v   Cobbler/Koan  Management Best Practices  As of RHEL5.2 remote management via virt-manager/virsh is supported   Can implement a “virtual appliance” style management instance Can trigger live migration from remote , as well as all other virsh commands  Can consolidate all management interfaces for virtualization and clustering onto a single management “appliance”/host If clustering is deployed use a bonded network interface for the cluster traffic and “virtualization” (live migration) traffic   Currently the clustering software assumes the network associated to the hostname is used for cluster and “virtualization” traffic  Even if no clustering is used it is recommended to use a dedicated network for migration traffic (and use at least a GbE connection) Installing RHEL5/Virt Considerations    Secure RHEL5 platform layer before installing any virtual machines or applications Enable SElinux to run in 'enforcing' mode Remove or disable any unwanted services  AutoFS, NFS, FTP, WWW, NIS, telnetd, sendmail etc...     Only add minimum number of user accounts needed for platform management Avoid running applications on dom0/Hypervisor Running applications in dom0 may impact virtual machine performance Use central location for virtual machine installations  Will make it easier to move to shared storage later on  If laptop with wireless adapter it used as virt platform use RHEL5.1 or Fedora 8 and beyond  New virt-manager will automatically configure a NAT/”dummy” network including local DHCP server Post-Install RHEL5/Virt Considerations  Services which can/should be disabled inside a RHEL5 guest     cpuspeed (prior to RHEL5.2), bluetooth, isdn, pcscd ip6tables (if no Ipv6 in use) hplip, cups (if no printing services are needed) mdmonitor, smartd (no need to monitor RAID and HW devices) Post-Install RHEL5/Virt Considerations  Setup remote VNC desktop access by performing the following steps  Enable vncserver using the command # chkconfig vncserver on  Create a password for the account using the vncserver (in our example it will be “root”) # vncpasswd (enter password and verify)  Edit /etc/sysconfig/vncservers and adding the lines : VNCSERVERS=”1:root” VNCSERVERARGS[1]=”-geometry 1024x768”  Create a X11 startup file for the vncserver account in ~/.vnc/ Name the file xstartup , it should include [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then eval `dbus-launch --sh-syntax --exit-with-session` echo "D-BUS per-session daemon address is: $DBUS_SESSION_BUS_ADDRESS" fi exec gnome-session  Planning for a RHEL5/Virt Infrastructure  Naming conventions for Virtual Machines, Network Interfaces, Filesystems, Volume Groups  At least choose different name for dom0/host VolGroup00 Foundation for live migration Make /var/lib/xen/images a seperate filesystem and consider using GFS  Consider shared storage to store Virtual Machine images    Make /var/lib/xen/dumps a seperate filesystem to avoid out-of-space for VM core dumps Private network for Xen traffic    Secure migration traffic and improve performance Controlled via “xend-relocation-*” options in /etc/xen/xend-config.sxp Network based installation tree for Para-Virt installations ISO file(s) or DVD/CD driver for HVM/Fully-virt installations  Central location for installation sources   RHEL5/Virt Considerations  Most of the standard Linux/RHEL tools for troubleshooting still work in a virtualized environment  top, iostat, vmstat, lsof, etc... Very few Xen specific tools (mostly xm and virsh commands)  “xentop & virt-top” for HyperVisor view of performance data  XenOprofile for profiling of active and inactive domains Leverage RHEL5/Virt capabilities to streamline provisioning  Golden Images for VMs and applications  Fast Provisioning with Kickstart files Always use virsh whenever possible  Allows scripting and command line recall  Can also extract domain/guest info as XML    PCIback configuration   RHEL5/Virt supports the “PCIback” feature (also known as PCI pass through) for para-virtualized guest operating systems Using PCIback it is possible to pass an individual PCI card to a given guest  The PCI card will only be available to this particular guest and can't be shared with other guests  PCIback has a number if implications the sysadmin should be aware of before implementing it    Any guest using PCIback will no longer be able to use save,restore and migration capabilities A guest which has access to a PCI card via PCIback also has potential access to the DMA address space of the host/dom0 The guest is no longer hardware agnostic as it will depend on underlying PCI infrastructure   The PCIback features has been build into the RHEL5/Virt kernel The feature is not functional in 5.1 but will be in 5.2 (there might be a hotfix for 5.1 at some point) PCIback configuration contd.   To configure PCIback follow the steps below There are two parts in configuring PCIback   Configuration on the host/dom0 side Configuration from the guest side Host side     Summary of steps required (more details in the following slides)   Load the pciback module Identify the PCI card(s) to be used for pass through Modify /etc/modprobe.conf to hide the PCI card(s) from the host and automatically load the pciback module Verify the PCI card has been unbound on the host and bound to the pciback driver Add PCI option to the guest config file Verify the PCI card can be seen inside the guest Configure the card as needed  Guest side    Virtualization Management Tools virt-top / Summary View virt-top / Physical CPU Statistics virt-top / Network Statistics virt-p2v      Utility to convert a physical server into a virtual machine Boot ISO image, USB stick of PXE Menu driven Data compression to improve performance Copy system data to remote host/Hypervisor nagios-virt   Plugin to allow monitoring of virtual machines in Nagios Simple installation   need libvirt-devel package Follow INSTALL and README files      Auto configuration via # nagios-virt install Display current config via # nagios-virt config Status information via # nagios-virt list Can easily be extended Provides status summary overview nagios-virt / All Hosts/Groups Summary nagios-virt / All Hosts Summary Nagios-virt / Service Summary Sorted Performance related Best Practices Virtual SMP combined with sub-CPU granularity All available in one offering on RHEL5 Virtual machine scalability and Higher resource utilization any virtual CPU can run on any physical CPU VM2 VM3 VM1 VM5 VM6 Virtual Machines VM8 VM4 VM7 CPU text CPU text CPU text CPU text RHEL5 Virt Platform VMn == domUn Memory ballooning  Guest can be configured to balloon/grow their current memory footprint  Allows for online expansion and growth  Can use virt-manager or CLI interface for management 2GB 1GB 1GB 0.5GB VM 2 Current Max Curr Max Memory Size Memory Size Mem Mem MEM 1GB MEM 1GB MEM 1GB MEM 1GB VM 1 Virtual Machines RHEL5 Virt Platform VMn == domUn Memory ballooning  Growing guest VM2 to 1GB using memory ballooning  Now both guests have increased their available memory online  Resize database SGA  Increase available VM for applications etc... 2GB 1GB Current Memory Size VM 1 1GB 0.5GB VM 2 Max Curr Max Memory Size Mem Mem MEM 1GB MEM 1GB MEM 1GB Virtual Machines MEM 1GB RHEL5 Virt Platform VMn == domUn Red Hat 5.1 Minimize Cost of Virtualization RHEL5.1 Fully Virtualized Performance Intel Woodcrest Linpackd 1kx1k Mflops Copy MB/sec RHEL5.1 Base RHEL5.1 PV RHEL4 FV RHEL4 FV+PV Iozone MB/sec Netperf Gb/sec 0 500 1000 1500 2000 2500 3000 3500 Network Performance in a virtualized environment Network throughput comparison with GbE Netperf Results in MB/s (remote via GbE) 1cpu Bare Metal Dom0 R5 PV R4 U5 PV R4FV+PV Other Virt R4U4 4cpu 0 20 40 60 80 100 120 Network Performance in a virtualized environment Internal Network throughput comparison Netperf Results in MB/s (local/internal bridge) 1cpu R5.1 PV (Local VM's) 2 x R5.1 PV (Local VM's) 4 x R5.1 PV (Local VM's) Other Virt R4u4 (Local VM's) Other Virt 2 x R4u4 (Local VM's) Other Virt 4 x R4u4 (Local VM's) 4cpu 0 100 200 300 400 500 600 700 800 Application Performance under RHEL5.2    OLTP Performance measured in tpm  Oracle 10G, SAP R3,  Use Fiber Channel or iSCSI to 14-32 15k rpm drives  Lower driver cost allows > tpm  Higher system time in drivers or long latency I/O reduce tpm RHEL5.1 PV drivers  Network  Disk I/O xvd Hardware enhancements − Intel – Large SMP systems 16-cpus - 4-socket, quad-core − AMD – Nested pages in newer HW  Barcelona quad-core systems – 8-cpu - 2-socket, quad-core Red Hat 5 Virt Minimize Cost of Virtualization RHEL5.1 Oracle 10G Relative OLTP Perf Intel 4-cpu 3Ghz Woodcrest, 8 GB guest, FC R5 GA 1-cpu Bare Metal R5 PV R4 FV R4 FV+PV R5 GA 4-cpu 0 0.2 0.4 0.6 0.8 1 1.2 Percent of Bare Metal trans/sec Red Hat 5 Virt Minimize Cost of Virtualization RHEL5.1 Virt Performance of Oracle 10G vs Other Virt , AMD 1-4-8 cpu, 8Gb mem 1-cpu RHEL5 Base RHEL5 PV RHEL4 FV+PV+NP OTHER Virt 4-cpu 8-cpu 0 10 20 30 40 tpm (k)50 60 70 80 90 100 Red Hat 5.1 Virt Multi-Guest Performance RHEL5.1 Virt, Oracle 10G Multiguest Performance AMD64 4cpu 2.0 Ghz, 16 GB mem, FC t RHEL4 RHEL4 guest4 guest3 guest2 guest1 RHELL4 0.00 10.00 20.00 30.00 40.00 50.00 60.00 70.00 80.00 90.00 100.00 OLTP Trans/min (1k) Red Hat 5 Virt Minimize Cost of Virtualization Red Hat 5 Virt Minimize Cost of Virtualization Red Hat 5 Virt Minimize Cost of Virtualization RHEL5.1 Virt HPDL585 16-cpu AMD Database Scaling Relative Performance Gain to Bare-Metal 1cpu Gain 8-cpu Gain 16cpu Gain 0 Bare-Metal 5 FV noopt FV w/ NP 10 FV PV+NP 15 20 25 Red Hat Virt Storage Alternatives RHEL5 RC1 Xen Application Performance w/ various Storage (2-cpu AMD64 2.2) Oracle 10G Trans/min (tpm) 25000 20000 15000 10000 5000 0 0.9 0.8 0.7 0.6 0.5 0.4 0.3 0.2 0.1 Fiber(xvd) iSCSI(xvd) ISCSI(guest NFSfiler(xv ) d) 0 R5(base) R5 – Dom0 R5 – Xen 4-cpu %diff Xen/Dom0 Similar Perf of Virtualization for different FS Comparison Ext3 vs GFS 100000.00 90000.00 80000.00 70000.00 60000.00 50000.00 40000.00 30000.00 20000.00 10000.00 0.00 Ext3 RHEL51 Base GFS RHEL51 Base Ext3 RHEL51 Dom0 GFS RHEL51 Dom0 Ext3 RHEL51 PV GFS RHEL51 PV Ext3 RHEL51 FV GFS RHEL51 FV 10 U 20 U 40 U 60 U 80 U 100 U Resources  Red Hat ● http://www.redhat.com/ http://www.openvirtualization.com/ http://www.libvirt.org/ http://virt-manager.et.redhat.com/ http://www.ovirt.org/ http://www.redhat.com/solutions/gfs/ http://et.redhat.com/  Virtualization Infocenter ●  libvirt ●  Virt-Manager ●  oVirt project home ●  Red Hat Cluster Suite ●  Red Hat Emerging Technology Group ● Thanks ! Questions ? High Availability & Virtualization RHEL5 Technical Overview / June 2008 Product features subject to change prior to availability 61 Highly Available RHEL5 Host RHEL5 Host A Shared Storage RHEL5 Host B Gues t Guest 1 Guest 2 Guest running as a RHCS service Guest X Highly Available RHEL5 Host RHEL5 Host A Shared Storage RHEL5 Host B Gues t Guest 1 Guest 2 Guest running as a RHCS service Guest X Automatic failover upon Hypervisor failure Highly Available RHEL5 Host RHEL5 Host A Shared Storage RHEL5 Host B App Gues t Guest 2 Guest 1 Guests running as independent cluster Guest X Hypervisor clustered via RHCS Highly Available RHEL5 Host RHEL5 Host A Shared Storage RHEL5 Host B App Guest 1 Guest 2 Guests running as independent cluster Guest X Hypervisor clustered via RHCS Application failover upon hosts/guest failure Highly Available RHEL5 Host RHEL5 Host A Shared Storage RHEL5 Host B Gues t Guest 1 Guest 2 App Guests running as independent cluster Guest X Hypervisor clustered via RHCS Application failover upon hosts/guest failure Highly Available RHEL5 Host RHEL5 Host A Shared Storage RHEL5 Host B App Guests running as independent cluster Guest 2 Guest X Guest 1 RHEL5 Host C Guest X Hypervisor and bare metal host clustered via RHCS Highly Available RHEL5 Host RHEL5 Host A Shared Storage RHEL5 Host B Guests running as independent cluster Guest 1 Guest 2 App Application can migrate to another Guest/VM RHEL5 Host C Guest X Guest X Hypervisor and bare metal host clustered via RHCS Highly Available RHEL5 Host RHEL5 Host A Shared Storage RHEL5 Host B Guests running as independent cluster Guest 1 Guest 2 Guest X RHEL5 App Host C Guest X Application can migrate to a bare metal system Hypervisor and bare metal host clustered via RHCS RHEL5 Disaster Recovery RHEL5 Site A RHEL5 Site B Shared Storage Guest 1 Guest 2 Guest Image Guest Image Guest Image Guest Image Guest Image Guest Image Guest X XP/CA, EVA/CA RHEL5 Disaster Recovery RHEL5 Site A RHEL5 Site B Shared Storage Guest 1 Guest 2 Guest Image Guest Image Guest Image Guest Image Guest Image Guest Image Guest X RHEL5 Disaster Recovery RHEL5 Site A RHEL5 Site B Shared Storage Guest X Guest Image Guest Image Guest Image Guest 1 Guest 2 XP/CA, EVA/CA Thanks ! Questions ?