Presentation is loading. Please wait.

Presentation is loading. Please wait.

HP Technology Forum & Expo Get connected. People. Technology. Solutions.

Similar presentations


Presentation on theme: "HP Technology Forum & Expo Get connected. People. Technology. Solutions."— Presentation transcript:

1 HP Technology Forum & Expo Get connected. People. Technology. Solutions.

2 Security Agility Reduced Cost Security Agility Reduced Cost Best Practices using Xen Virtualization with Red Hat Enterprise Linux 5 Jan Mark Holzer jmh@redhat.com Consulting Engineer Emerging Technology Group CTO Office

3 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 3 Outline Best Practices Performance Expectations Key directories and files Some common examples Q&A

4 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 4 Basic Information before you start

5 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 5 Before you start Read the documentation and QuickStart guides RHEL5 Virt Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Virtualization- en-US/index.html http://www.redhat.com/docs/ Fedora Core 6 Xen QuickStart http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 Kbase articles http://kbase.redhat.com http://kbase.redhat.com/faq/topten_108_0.shtm for virtualization specific topics Virtualization brain dump http://et.redhat.com/~jmh/docs/ Look for Installing_RHEL5_Virt.pdf/odt Red Hat Summit Slides http://et.redhat.com/~jmh/RH_Summit_2007/ XenWiki http://wiki.xensource.com/xenwiki/

6 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 6 RHEL5/Xen Architecture Hardware Hypervisor dom0 Device Driver Back End domU/VM1 Front end domU/VM2 Front end Virtual CPU & Memory

7 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 7 Guest/Hypervisor Matrix with PAE For Paravirtual, the guest has to be equal to dom0 For HVM, the guest has to be equal or less than dom0 RHEL5/Xen Hypervisor itself must be EQUAL to dom0 Goal to support 32bit para-virt on 64bit dom0/HV for RHEL 5.1

8 8 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Platform/Guest Release Support in RHEL5 Fully supported by Red Hat Para-virtualized guest support RHEL5 at GA (Q1/2007) RHEL4 U5 / RHEL 4.5 SMP and UP support for all RHEL para-virt guests Fully-virtualized support (with appropriate hardware features(VTx or AMD-V) All existing and supported RHEL releases RHEL3, RHEL4 (SMP and UP support) Will/Should work operating systems (best effort support by Red Hat) Fully virt support only for any foreign operating systems SUSE SLES9/SLES10 OpenSolaris Windows Other x86/x86_64 OS

9 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 9 Basic Information and Hints

10 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 10 Prerequisites for RHEL5/Xen Use RHEL5 Xen packages, DO NOT install Xen RPMs from XS !! Apply Day 0 errata updates for RHEL5 and Xen components Fix for 'dual' cursor mouse in virt-manager Need Intel-VT/AMD-V capabilities for HVM/Fully-Virt guests Install VNC and VSFTP packages VNC for remote desktop access VSFTP for access to local/remote para-virt installation tree At least 2GB of memory for a working system Use at least 300MB for guest installations More memory will speed up the installation process 256MB may potentially cause installation failures Plan for enough disk space on the host Rough guideline for a guest installation is ~5GB Guest image includes encapsulated swap space

11 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 11 Installing RHEL5/Xen 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 need to perform special steps to make Xen networking functional Setup dummy network interface and NAT traffic through WiFi

12 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 12 Planning for a Xen Infrastructure Naming conventions for Virtual Machines, Network Interfaces, Filesystems, Volume Groups At least choose different name for dom0/host VolGroup00 Consider shared storage to store Virtual Machine images Foundation for live migration Make /var/lib/xen/images a seperate filesystem and as of RHEL5.1 use GFS2 even on a single/local host 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 Central location for installation sources Network based installation tree for Para-Virt installations ISO file(s) or DVD/CD driver for HVM/Fully-virt installations

13 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 13 RHEL5/Xen 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) xm top for HyperVisor view of performance data XenOprofile for profiling of active and inactive domains Leverage RHEL5/Xen capabilities to streamline provisioning Golden Images for VMs and applications Fast Provisioning with Kickstart files

14 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 14 /etc/xen xend-config.sxp xend configuration file Domain / guest config files /etc/xen/scripts (customizable) control scripts Device management -eg. Networking /etc/xen/auto Softlinks to guests that should start automatically xendomains service starts these guests Typically disabled by default Configuration – Key files and directories

15 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 15 /var/lib/xen dump Kernel dumps generated with xm dump-core images Guest images (covered by SElinux policy) xend-db Xen internal database /var/lib/xend Sockets used by xend (xend-socket / relocation-socket) /var/lib/xenstored xend database (tdb) Can be read with xenstore-ls Configuration – Key files and directories

16 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 16 /var/log/xen xend.log Logfile used by xend for logging Primary file to review in case of problems xend-debug.log Debug output from xend xend-hotplug.log Logfile for hotplug events Will record information in case of hotplug failure of devices qemu-dm.{PID}.log Logfile used by the qemu-dm process All logfiles are human readbale and can be view with the standard Linux utilities (or xm log for xend.log) Logging – Key files and directories

17 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 17 /proc/cpuinfo shows whether pae, svm, vmx enabled CPU /proc/xen various information about xen /sys/hypervisor more information about domain, including UUID Xen Python scripts are logging to debug facility (not enabled by default) Add *.* /var/log/debug.log to syslog config file Logging/Capabilities – Key files and directories

18 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 18 Scripts are stored in /etc/xen/scripts Configured in /etc/xen/xend-config.sxp Networking (network-script network-bridge) (vif-script vif-bridge) This configuration declares that network-bridge should handle the network setup vif-bridge should handle each domU add/remove

19 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 19 Multi Network Bridge Solution : Modify /etc/xen/xend-config.sxp Replace call to network-bridge script with call to custom script (ie multi- network-bridge) Create custom script in /etc/xen/scripts Inside the custom script call network-bridge script with addtl parameters/interfaces Networking / Multi-bridge config

20 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 20 Networking / Example for multi-bridge config #!/bin/sh # network-xen-multi-bridge set -e # First arg is the operation. OP=$1 shift script=/etc/xen/scripts/network-bridge.xen case ${OP} in start) $script start vifnum=0 bridge=xenbr0 netdev=eth1 $script start vifnum=1 bridge=xenbr1 netdev=eth2 $script start vifnum=2 bridge=xenbr2 netdev=eth3 ;; stop) $script stop vifnum=0 bridge=xenbr0 netdev=eth1 $script stop vifnum=1 bridge=xenbr1 netdev=eth2 $script stop vifnum=2 bridge=xenbr2 netdev=eth3 ;; status) $script status vifnum=0 bridge=xenbr0 netdev=eth1 $script status vifnum=1 bridge=xenbr1 netdev=eth2 $script status vifnum=2 bridge=xenbr2 netdev=eth3 ;; *) echo 'Unknown command: ' ${OP} echo 'Valid commands are: start, stop, status' exit 1 esac

21 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 21 Migration Requires shared storage Both dom0's must access same disk image or physical device Using Physical device LUN on SAN Exported block device ISCSI, GNBD Both dom0's should use same name for device eg. /dev/sdg Use UDEV rules for mapping if required

22 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 22 Migration Using File based disk image Disk image stored on shared file system NFS * Samba GFS Should be mounted on same mount point Both domain 0's see same directory structure eg. /var/lib/xen/images

23 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 23 Migration Enable relocation server /etc/xen/xend-config.sxp (xend-relocation-server yes) (xend-relocation-port 8002) (xend-relocation-address '') (xend-relocation-hosts-allow '') Enables relocation server Listens on port 8002 (default) Use lsof to verify relocation port is active [root@grumble]$ sudo lsof -i :8002 python 3873 root 5u IPv4 12329 TCP *:teradataordbms (LISTEN) Binds to all IP addresses Allows any host to migrate to this domain 0 Authorized hosts can be listed by IP or name '^myserver.mydomain.com$ ^.*\.redhat\.com$'

24 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 24 Basic Xen commands Once you have your first guest installed you can use the following commands for some basic management To startup a guest # /usr/sbin/xm create -c GuestName Where GuestName is the name you gave for your guest during the installation The -c will attach a xen console to your vm A variety of other commands are available via xm including # /usr/sbin/xm help or # virsh help For a list of commands that can be run Use '--long' in addition for extended help text You can also use #/usr/sbin/xm help –help for a specific command

25 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 25 Basic Xen commands contd. # /usr/sbin/xm list (--long) or # virsh list List running domains/guest and their status/accumulated CPU time # /usr/sbin/xm top for a display showing what your virtual machines are doing similar to that provided by top # /usr/sbin/xm shutdown GuestName or # virsh shutdown GuestName to nicely shut down a guest OS where foo is the name of your guest. # /usr/sbin/xm destroy GuestName or # virsh destroy GuestName To power down a guest (hard reset)

26 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 26 Basic Xen commands (Suspend/Resume) # /usr/sbin/xm save GuestName GuestName.sav or # virsh save GuestName GuestName.sav to save the state of the guest 'GuestName' to the file GuestName.restore # /usr/sbin/xm restore GuestName.sav or # virsh restore GuestName.sav to restore the above saved guest # /usr/sbin/xm pause GuestName or # virsh pause GuestName to suspend a running guest (release CPU cycles but retain memory footprint) # /usr/sbin/xm unpause GuestName or # virsh unpause GuestName to resume a previously suspended guest

27 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 27 Basic Xen commands (Resource Management) # /usr/sbin/xm vcpu-set or # virsh setvcpus set the number of CPUs available to to (only works for dom0/paravirtualized guests) # /usr/sbin/xm vcpu-list or # virsh vcpuinfo List the physical-virtual CPU bindings # /usr/sbin/xm mem-set or # virsh setmem balloon up or down to (only works for dom0/paravirtualized guests) # /usr/sbin/xm sched-credit -d Display credit schedule information and set cap/weight for individual domain

28 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 28 Other Useful Commands and Tools Basic Xen commands xm log xm dmesg xm info / virsh nodeinfo xm top virsh commands (extract) virsh dominfo virsh domstate Virsh dumpxml Tools strace, lsof, iostat/vmstat Systemtap /var/log/messages /var/log/xen AVC messages (setroubleshoot) sosreport has a plugin that automatically gathers all of the above information Plugin not included in RHEL-5 GA, should be included in day0 errata

29 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 29 RHEL5 Virt Performance Data

30 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 30 Red Hat Virt Single-guest Performance

31 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 31 Red Hat Virt Performance Para-Virt vs Fully Virt VTx

32 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 32 Red Hat Virt Multi-guest Performance

33 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 33 Red Hat Virt Multi-guest Efficiency

34 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 34 Red Hat Virt Java Multiguest Performance

35 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 35 Red Hat Virt Multiple Guest Performance

36 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 36 SMP in Guest OSes Takes great care to get good performance while remaining secure Paravirtualized approach yields many important benefits Avoids many virtual IPIs Enables bad preemption avoidance Auto hot plug/unplug of CPUs SMP scheduling (at hypervisor) Strict gang scheduling not optimal Credit Scheduler in Xen 3.0.2 (RHEL5)

37 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 37 Red Hat Virt SMP guest Performance

38 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 38 Red Hat Virt SMP Performance

39 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 39 Red Hat Virt SMP guest Performance

40 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 40 Red Hat Virt Network Performance

41 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 41 Red Hat Virt Network Performance

42 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 42 Red Hat Xen FV Performance

43 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 43 Red Hat Virt Storage Alternatives

44 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 44 Tuning using PCI domain Hypervisor can dedicate PCI-domain's to individual guest. Default Xen shared HBA / NICs within guest config. Disk – tested up to 6 Fiber Channel HBAs Network – tested up to 3 1-Gibit network cards Pros - Dedicate physical PCI resource to guest Done in guest configuration file Improve I/O performance 10-15% Cons - Limit throughput when VM's are idle. Limit configuration if planning to use migration

45 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 45 Red Hat Virt Performance Enhance CPU Perf w/ Vcpu-pin Tuning

46 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 46 Tuning using PCI domain

47 47 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability A few examples

48 48 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Installation Issues Require different installation source for PV vs FV installations PV requires network based install tree FV require local boot.iso or DVD In upcoming version of virt-manager/virt-install can specify a network tree for boot.iso VM image not in /var/lib/xen/images with SElinux enabled in enforcing mode Will cause backend device not being connected and generate a hotplug event Installation seems to hang If iSCSI is used for root device for VM need to create a local boot slab Also needs a custom network script if iSCSI is not reachable via default network

49 49 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Installation Issues If multiple Xen bridges are configured use virt-install to specify specific bridge virt-manager will use the bridge attached to the default network/route

50 50 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Installation Issues / VT/AMD-V Extensions Intel/VT extensions not enabled in BIOS Unable to install HVM guest (box grayed out) You can use the following commands to verify whether the virtualization extensions have been enabled On an Intel/VT based system, look for VMX [root@woodie ~]# xm dmesg | grep VMX (XEN) VMXON is done and to verify the CPU flags have been set [root@woodie ~]# cat /proc/cpuinfo |grep vmx flags: fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm You should have a VMXON for each reported processor. If you have any other messages visit your BIOS settings There is no reason to go any further until you have VMXON reported - it just isn't going to work

51 51 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Installation Issues / VT/AMD-V Extensions AMD/AMD-V extensions not enabled in BIOS Unable to install HVM guest (box grayed out) On an AMD-V based system, look for SVM [root@perf3 ~]# xm dmesg|grep SVM (XEN) AMD SVM Extension is enabled for cpu 0 (XEN) AMD SVM Extension is enabled for cpu 1 and to verify the CPU flags have been set [root@perf3 ~]# cat /proc/cpuinfo |grep svm flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc You should have a AMD SVM for each reported processor. If you have any other messages visit your BIOS settings There is no reason to go any further until you have VMXON reported - it just isn't going to work

52 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 52 Troubleshooting (Memory Ballooning) Failed domain creation due to memory shortage, ie unable to balloon domain A domain might fail to start if there's either not enough memory available or if dom0 has not ballooned down enough to provide space for the newly created/started guest A typical error message in your /var/log/xen/xend.log would be [2006-11-21 20:33:31 xend 3198] DEBUG (balloon:133) Balloon: 558432 KiB free; 0 to scrub; need 1048576; retries: 20. [2006-11-21 20:33:52 xend.XendDomainInfo 3198] ERROR (XendDomainInfo:202) Domain construction failed You can verify the amount of memory currently used by dom0 using the command xm list Domain-0, if dom0 indeed is not ballooned down you can use the command xm mem-set Domain-0 NewMemSize (where NewMemSize should be a small(er) value

53 53 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Troubleshooting (non-Xen/PAE kernel) Wrong kernel image (ie non-Xen kernel in a para-virt guest) If you try to boot a non-xen kernel in a para-virtualized guest you will see the following error message [root@grumble]# xm create testVM Using config file "./testVM". Going to boot Red Hat Enterprise Linux Server (2.6.18-1.2839.el5) kernel: /vmlinuz-2.6.18-1.2839.el5 initrd: /initrd-2.6.18-1.2839.el5.img Error: (22, 'Invalid argument') In the above example you can see that the kernel line shows that it's trying to boot a non-xen kernel. The correct entry would be kernel: /vmlinuz-2.6.18-1.2839.el5xen

54 54 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Troubleshooting (networking/bridging) Wrong bridge configured in guest configuration file causing Xen Hotplug scripts to timeout If you have moved configuration files between different hosts you may to make sure your guest configuration files have been updated to reflect any change in network topology/configuration such as Xen bridge numbering etc [root@grumble xen]# xm create r5b2-mySQL01 Using config file "r5b2-mySQL01". Going to boot Red Hat Enterprise Linux Server (2.6.18-1.2747.el5xen) kernel: /vmlinuz-2.6.18-1.2747.el5xen initrd: /initrd-2.6.18-1.2747.el5xen.img Error: Device 0 (vif) could not be connected. Hotplug scripts not working In /var/log/xen/xen-hotplug.log you will see the following error being logged bridge xenbr1 does not exist!

55 55 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Troubleshooting (networking/bridging) contd In /var/log/xen/xend.log you will see the following messages being logged [2006-12-14 15:07:08 xend 3874] DEBUG (DevController:143) Waiting for devices vif. [2006-12-14 15:07:08 xend 3874] DEBUG (DevController:149) Waiting for 0. [2006-12-14 15:07:08 xend 3874] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug- status. [2006-12-14 15:08:48 xend 3874] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug- status. [2006-12-14 15:08:48 xend 3874] DEBUG (DevController:464)

56 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 56 Zombie Domains When shutting down a domain or migrating, it doesn't actually die but ends up leaving a domain named Zombie- Typically caused by restarting xend while domains are running Xend does not properly reconnect certain devices (most notably frame buffers), so when the domain goes to shut down, xend does not know how to find all of the resources for the domain to destroy If it happens during migration likely cause is either networking problem or remote relocation server not enabled (status can also change to migrating- [root@dhcp78-237 ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 14627 8 r----- 18883.9 Zombie-rhel4u5pv01 9 511 1 -p---- 1072.2 rhel5gapv01 4 511 1 -b---- 1961.1 To resolve the issue Reboot (only reliable solution) Balloon down Zombie domain to make room for other domains

57 57 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Storage Troubleshooting (Filebased) Unable to start more than 8 file based guests If file based guest images are used one may have to increase the number of configured loop devices. The default configuration allows up to 8 loop devices to be active, if more than 8 file based guests/loop devices are needed the number of loop devices configured can be adjusted in /etc/modprobe.conf Simply edit /etc/modprobe.conf and add the following line to it options loop max_loop=64 You can substitute the number '64' with a number which fits your local configuration

58 58 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Storage Troubleshooting (Filebased) Check if tapdisk process is actually running [root@dhcp78-237 ~]# ps auxw|grep tap root 3338 0.0 0.0 95644 680 ? Ssl Apr29 0:00 blktapctrl root 1053 0.0 0.0 60268 708 pts/7 S+ 06:09 0:00 grep tapd root 5238 0.0 0.0 30176 612 ? Sl Apr29 0:04 tapdisk /dev/xen/tapctrlwrite2 /dev/xen/tapctrlread2 root 6843 0.0 0.0 30172 612 ? Sl Apr29 0:03 tapdisk /dev/xen/tapctrlwrite3 /dev/xen/tapctrlread3

59 59 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Storage Troubleshooting (Filebased) For each disk there should be a corresponding entry in your domain configuration [root@woodie ~]# virsh dumpxml 4 rhel5gapv01 linux /var/lib/xen/vmlinuz.Q0Psrs /var/lib/xen/initrd.B_e0Gm ro root=/dev/VolGroup00/LogVol00 rhgb quiet

60 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 60 Other random bits A fully virtualized x86_64 guest fails to boot with Your CPU does not support long mode. Use a 32bit distribution. Resolution: Make sure pae=1 is set in the domain configuration file Over time, the /var/lib/xen directory becomes full of kernel.xxxxx and initrd.xxxxx files Xen tools don't always clean up after errors Resolution: Safe to just delete all of the files Message: FATAL: Module microcode not found during domain boot It's not really a fatal error, it is just warning that the virtual machine couldn't update the CPU microcode Resolution: Nothing required To get rid of error message, disable microcode_ctl service

61 61 HP Technology forum June 2007 / RHEL5/Virt Workshop Product features subject to change prior to availability Consider the possibilities...

62 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 62 Resources Red Hat http://www.redhat.com/ Virtualization Infocenter http://www.openvirtualization.com/ Libvirt http://www.libvirt.org/ Virt-Manager http://virt-manager.et.redhat.com/ Red Hat Cluster Suite http://www.redhat.com/solutions/gfs/ Red Hat Emerging Technology Group http://et.redhat.com/

63 63 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability Questions ? Thanks

64 HP Technology Forum & Expo Get connected. People. Technology. Solutions.

65 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 65 Highly Available RHEL5 Host RHEL5 Host A Guest RHEL5 Host B Shared Storage Guest running as a RHCS service Guest 1 Guest 2Guest X

66 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 66 Highly Available RHEL5 Host RHEL5 Host A Guest RHEL5 Host B Shared Storage Guest running as a RHCS service Guest 1 Guest 2Guest X Automatic failover upon Hypervisor failure

67 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 67 Highly Available RHEL5 Host RHEL5 Host A Guest RHEL5 Host B Shared Storage App Guest 2Guest X Guest 1 Guests running as independent cluster Hypervisor clustered via RHCS

68 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 68 Highly Available RHEL5 Host RHEL5 Host A RHEL5 Host B Shared Storage Guest 2 App Guest X Guest 1 Guests running as independent cluster Hypervisor clustered via RHCS Application failover upon hosts/guest failure

69 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 69 Highly Available RHEL5 Host RHEL5 Host A Guest RHEL5 Host B Shared Storage Guest 2 App Guest X Guest 1 Guests running as independent cluster Hypervisor clustered via RHCS Application failover upon hosts/guest failure

70 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 70 Highly Available RHEL5 Host RHEL5 Host A RHEL5 Host B Shared Storage App Guest 2 Guest X Guests running as independent cluster Hypervisor and bare metal host clustered via RHCS RHEL5 Host C Guest 1 Guest X

71 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 71 Highly Available RHEL5 Host RHEL5 Host A RHEL5 Host B Shared Storage Guest 2 Guest X Guests running as independent cluster Hypervisor and bare metal host clustered via RHCS RHEL5 Host C App Guest 1 Guest X Application can migrate to another Guest/VM

72 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 72 Highly Available RHEL5 Host RHEL5 Host A RHEL5 Host B Shared Storage Guest 2 Guest X Guests running as independent cluster Hypervisor and bare metal host clustered via RHCS RHEL5 Host C App Guest 1 Guest X Application can migrate to a bare metal system

73 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 73 RHEL5 Disaster Recovery RHEL5 Site A RHEL5 Site B Shared Storage Guest 1 Guest 2 Guest X Guest Image Guest Image Guest Image Guest Image Guest Image Guest Image XP/CA, EVA/CA

74 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 74 RHEL5 Disaster Recovery RHEL5 Site A RHEL5 Site B Shared Storage Guest 1 Guest 2 Guest X Guest Image Guest Image Guest Image Guest Image Guest Image Guest Image XP/CA, EVA/CA

75 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 75 RHEL5 Disaster Recovery RHEL5 Site A RHEL5 Site B Shared Storage Guest 1 Guest 2 Guest X Guest Image Guest Image Guest Image Guest Image Guest Image Guest Image XP/CA, EVA/CA

76 HP Technology Forum June 2007 / RHEL5/Virt Best Practices Product features subject to change prior to availability 76 RHEL5 Disaster Recovery RHEL5 Site A RHEL5 Site B Shared Storage Guest 1 Guest 2 Guest X Guest Image Guest Image Guest Image XP/CA, EVA/CA


Download ppt "HP Technology Forum & Expo Get connected. People. Technology. Solutions."

Similar presentations


Ads by Google