web/html/docs/virtualization-guide/f12/en-US/html-single index.html, NONE, 1.1

Rüdiger Landmann rlandmann at fedoraproject.org
Sat Oct 3 08:06:28 UTC 2009


Author: rlandmann

Update of /cvs/fedora/web/html/docs/virtualization-guide/f12/en-US/html-single
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv30540/virtualization-guide/f12/en-US/html-single

Added Files:
	index.html 
Log Message:
add F12 Virtualization Guide draft


--- NEW FILE index.html ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
  PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>Virtualization Guide</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content=""/><meta name="description" content="The Fedora 12 Virtualization Guide contains information on installation, configuring, administering, tips, tricks and troubleshooting virtualization technologies used in Fedora 12."/></head><body class="draft "><div class="book" lang="en-US"><div class="titlepage"><div><div class="producttitle"><span class="productname">Fedora</span> <span class="productnumber">12</span></div><div><h1 id="d0e1" class="title">Virtualization Guide</h1></div><div><h2 class="subtitle">The definitive guide for virtualization on Fedora</h2></div><p class="edition">Edition 1</p><div><h3 class="corpauthor">
				<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Logo</object></span>
			</h3></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Christoph</span> <span class="surname">Curran</span></h3><code class="email"><a class="email" href="mailto:ccurran at redhat.com">ccurran at redhat.com</a></code></div></div></div><hr/><div><div id="d0e27" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
		Copyright <span class="trademark"/>© 2009 Red Hat, Inc. This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1.0, (the latest version is presently available at <a href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a>).
	</div><div class="para">
		Fedora and the Fedora Infinity Design logo are trademarks or registered trademarks of Red Hat, Inc., in the U.S. and other countries.
	</div><div class="para">
		Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat Inc. in the United States and other countries.
	</div><div class="para">
		All other trademarks and copyrights referred to are the property of their respective owners.
	</div><div class="para">
		Documentation, as with software itself, may be subject to export control. Read about Fedora Project export controls at <a href="http://fedoraproject.org/wiki/Legal/Export">http://fedoraproject.org/wiki/Legal/Export</a>. 
	</div></div></div><div><div class="abstract"><h6>Abstract</h6><div class="para">The Fedora 12 Virtualization Guide contains information on
installation, configuring, administering, tips, tricks and
troubleshooting virtualization technologies used in Fedora
12.</div></div></div></div><hr/></div><div class="toc"><dl><dt><span class="preface"><a href="#pref-Virtualization_Guide-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-About_this_book">1. About this book</a></span></dt><dt><span class="section"><a href="#d0e86">2. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e96">2.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#d0e312">2.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#d0e331">2.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#d0e351">3. We Need Feedback!</a></span></dt></dl></dd><dt><span class="part"><a href="#part-Virtualization_Guide-Installation">I. Installation</a></span></dt><dd><dl><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Installing_the_virtualization_packages">1. Installing the virtualization packages</a></span></d
 t><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_with_a_new_Fedora_installation">1.1. Installing Xen with a new Fedora installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system">1.2. Installing Xen packages on an existing Fedora system</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation">1.3. Installing KVM with a new Fedora installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system">1.4. Installing KVM packages on an existing Fedora system</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Virtualized_guest_insta
 llation_overview">2. Virtualized guest installation overview</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_install">2.1. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager">2.2. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE">2.3. Installing guests with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Guest_operating_system_installation_procedures">3. Guest operating system installation procedures</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_5_as_a_para_virtualized_guest">3.1. Installing Red Hat 
 Enterprise Linux 5 as a para-virtualized guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest">3.2. Installing Red Hat Enterprise Linux as a fully virtualized guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest">3.3. Installing Windows XP as a fully virtualized guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest">3.4. Installing Windows Server 2003 as a fully virtualized guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest">3.5. Installing Windows Server 2008 as a fully virtualized guest</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Virtualization_Guide-Configuration">II. Configuration</a></span><
 /dt><dd><dl><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Virtualized_block_devices">4. Virtualized block devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Virtualized_block_devices-Creating_a_virtualized_floppy_disk_controller">4.1. Creating a virtualized floppy disk controller</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests">4.2. Adding storage devices to guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage">4.3. Configuring persistent storage</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Virtualized_block_devices-Add_a_virtualized_CD_ROM_or_DVD_device_to_a_guest">4.4. Add a virtualized CD-ROM or DVD device to a guest</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Shared_s
 torage_and_virtualization">5. Shared storage and virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_iSCSI_for_storing_guests">5.1. Using iSCSI for storing guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests">5.2. Using NFS for storing guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests">5.3. Using GFS2 for storing guests</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Server_best_practices">6. Server best practices</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Security_for_virtualization">7. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Security_for_virtualization-S
 ELinux_and_virtualization">7.1. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations">7.2. SELinux considerations</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Network_Configuration">8. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">8.1. Network address translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Network_Configuration-Bridged_networking_with_libvirt">8.2. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Xen_networking">9. Xen networking</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Xen_networking-Configuring_multiple_guest_network_bridges_
 to_use_multiple_Ethernet_cards">9.1. Configuring multiple guest network bridges to use multiple Ethernet cards</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Xen_networking-Laptop_network_configuration">9.2. Laptop network configuration</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Xen_Para_virtualized_Drivers">10. Xen Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Para_virtualization_Restrictions_and_Support">10.1. Para-virtualization Restrictions and Support</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers">10.2. Installing the Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers-Common_installation_steps">10.2.1. Common installation steps</a></span></dt><dt><span class="section"
 ><a href="#sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_3">10.2.2. Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 3</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_4">10.2.3. Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 4</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_5">10.2.4. Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 5</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization_Guide-Para_virtualized_Network_Driver_Configuration">10.3. Para-virtualized Network Driver Configuration</a></span></dt><dt><span class="section"><a href="#
 sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration">10.4. Additional Para-virtualized Hardware Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtualized_Network_Interfaces">10.4.1. Virtualized Network Interfaces</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtual_Storage_Devices">10.4.2. Virtual Storage Devices</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-KVM_Para_virtualized_Drivers">11. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-KVM_Para_virtualized_Drivers-Installing_the_KVM_Windows_para_virtualized_drivers">11.1. Installing the KVM Windows para-virtualized drivers</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Virt
 ualization_Guide-Administration">III. Administration</a></span></dt><dd><dl><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Managing_guests_with_xend">12. Managing guests with xend</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Guide-KVM_guest_timing_management">13. KVM guest timing management</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Xen_live_migration">14. Xen live migration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Xen_live_migration-A_live_migration_example">14.1. A live migration example</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Xen_live_migration-Configuring_guest_live_migration">14.2. Configuring guest live migration</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-KVM_live_migration">15. KVM live migration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualizati
 on_Guide-KVM_live_migration-Live_migration_requirements">15.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration">15.2. Share storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-KVM_live_migration-Live_KVM_migration_with_virsh">15.3. Live KVM migration with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-KVM_live_migration-Migrating_with_virt_manager">15.4. Migrating with virt-manager</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Remote_management_of_virtualized_guests">16. Remote management of virtualized guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_with_SSH">16.1. Remote management with SSH</a></span></dt><
 dt><span class="section"><a href="#sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL">16.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes">16.3. Transport modes</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Virtualization_Guide-Virtualization_Reference_Guide">IV. Virtualization Reference Guide</a></span></dt><dd><dl><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Virtualization_tools">17. Virtualization tools</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Managing_guests_with_virsh">18. Managing guests with virsh</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager">19. Managing guests with the Virtual Machine Manager (virt-manager)</a></span></dt><dd
 ><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window">19.1. The open connection window</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window">19.2. The Virtual Machine Manager main window</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_">19.3. The Virtual Machine Manager details window </a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_">19.4. Virtual Machine graphical console </a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manag
 er_virt_manager-Starting_virt_manager">19.5. Starting virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Restoring_a_saved_machine_">19.6. Restoring a saved machine </a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details">19.7. Displaying guest details</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring">19.8. Status monitoring</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers">19.9. Displaying guest identifiers</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-D
 isplaying_a_guests_status_">19.10. Displaying a guest's status </a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_">19.11. Displaying virtual CPUs </a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage">19.12. Displaying CPU usage</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_memory_usage_">19.13. Displaying memory usage </a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network">19.14. Managing a virtual network</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Cr
 eating_a_virtual_network">19.15. Creating a virtual network</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-The_xm_command_quick_reference">20. The xm command quick reference</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters">21. Configuring the Xen kernel boot parameters</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Xen_configuration_files">22. Xen configuration files</a></span></dt></dl></dd><dt><span class="part"><a href="#part-Virtualization_Guide-Tips_and_Tricks">V. Tips and Tricks</a></span></dt><dd><dl><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Tips_and_tricks">23. Tips and tricks</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Automatically_starting_guests">23.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualizat
 ion_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors">23.2. Changing between the KVM and Xen hypervisors</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-Xen_to_KVM">23.2.1. Xen to KVM</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-KVM_to_Xen">23.2.2. KVM to Xen</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img">23.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM">23.4. Overcommitting with KVM</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf">23.5. Modifying /etc/grub.conf</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualizatio
 n_extensions">23.6. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation">23.7. Identifying guest type and implementation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address">23.8. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest">23.9. Limit network bandwidth for a Xen guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Configuring_Xen_processor_affinities">23.10. Configuring Xen processor affinities</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Modifying_the_Xen_hypervisor">23.11. Modifying the Xen hypervisor</a></span></dt><dt><span class="section"><a href="#sect-Virtual
 ization_Guide-Tips_and_tricks-Very_Secure_ftpd">23.12. Very Secure ftpd</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence">23.13. Configuring LUN Persistence</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests">23.14. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files">23.15. Cleaning up old Xen configuration files</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Configuring_a_VNC_Server">23.16. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Tips_and_tricks-Cloning_guest_configuration_files">23.17. Cloning guest configuration files</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide
 -Tips_and_tricks-Duplicating_an_existing_guest_and_its_configuration_file">23.18. Duplicating an existing guest and its configuration file</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Creating_custom_libvirt_scripts">24. Creating custom libvirt scripts</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Creating_custom_libvirt_scripts-Using_XML_configuration_files_with_virsh">24.1. Using XML configuration files with virsh</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Virtualization_Guide-Troubleshooting">VI. Troubleshooting</a></span></dt><dd><dl><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Troubleshooting_Xen">25. Troubleshooting Xen</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Debugging_and_troubleshooting_Xen">25.1. Debugging and troubleshooting Xen</a></span></dt><dt><span class="section"><a hre
 f="#sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview">25.2. Log files overview</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions">25.3. Log file descriptions</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations">25.4. Important directory locations</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs">25.5. Troubleshooting with the logs</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_serial_console">25.6. Troubleshooting with the serial console</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Para_virtualized_guest_console_access">25.7. Para-virtualized guest console access</a></span></dt><dt><span class="section"><a href="#sec
 t-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access">25.8. Fully virtualized guest console access</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image">25.9. Accessing data on guest disk image</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Common_Xen_problems">25.10. Common Xen problems</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors">25.11. Guest creation errors</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles">25.12. Troubleshooting with serial consoles</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_for_Xen">25.12.1. Serial console output for Xen</a></span></dt><dt><sp
 an class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_para_virtualized_guests">25.12.2. Xen serial console output from para-virtualized guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_from_fully_virtualized_guests">25.12.3. Serial console output from fully virtualized guests</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Guest_configuration_files">25.13. Guest configuration files</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages">25.14. Interpreting Xen error messages</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_Xen-The_layout_of_the_log_directories">25.15. The layout of the log directories</a></span></dt></dl></dd><dt><span class
 ="chapter"><a href="#chap-Virtualization_Guide-Troubleshooting">26. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Identifying_available_storage_and_partitions">26.1. Identifying available storage and partitions</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes">26.2. After rebooting Xen-based guests the console freezes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Virtualized_Ethernet_devices_are_not_found_by_networking_tools">26.3. Virtualized Ethernet devices are not found by networking tools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Loop_device_errors">26.4. Loop device errors</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Failed_domain_creation_caused_by_a_memory_sh
 ortage">26.5. Failed domain creation caused by a memory shortage</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error">26.6. Wrong kernel image error</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error_non_PAE_kernel_on_a_PAE_platform">26.7. Wrong kernel image error - non-PAE kernel on a PAE platform</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Fully_virtualized_64_bit_guest_fails_to_boot">26.8. Fully-virtualized 64 bit guest fails to boot</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-A_missing_localhost_entry_causes_virt_manager_to_fail">26.9. A missing localhost entry causes virt-manager to fail</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Microcode_error_during_guest_boot">26.10. Microcode error during 
 guest boot</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Wrong_bridge_configured_on_the_guest_causing_hot_plug_script_timeouts">26.11. Wrong bridge configured on the guest causing hot plug script timeouts</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine">26.12. Python depreciation warning messages when starting a virtual machine</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS">26.13. Enabling Intel VT and AMD-V virtualization hardware extensions in BIOS</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers">27. Troubleshooting the Xen para-virtualized drivers</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-V
 irtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Fedora_Virtualization_log_file_and_directories">27.1. Fedora Virtualization log file and directories</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Para_virtualized_guest_fail_to_load_on_a_Red_Hat_Enterprise_Linux_3_guest_operating_system">27.2. Para-virtualized guest fail to load on a Red Hat Enterprise Linux 3 guest operating system</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers">27.3. Manually loading the para-virtualized drivers</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_have_successfully_loaded">27.4. Verifying the para-virtualized drivers have successfully loaded</a></span></dt><dt
 ><span class="section"><a href="#sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-The_system_has_limited_throughput_with_para_virtualized_drivers">27.5. The system has limited throughput with para-virtualized drivers</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#appe-Virtualization_Guide-Xen_system_architecture_">A. Xen system architecture </a></span></dt><dt><span class="appendix"><a href="#appe-Virtualization_Guide-Additional_resources">B. Additional resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Additional_resources-Online_resources">B.1. Online resources</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Additional_resources-Installed_documentation">B.2. Installed documentation</a></span></dt></dl></dd><dt><span class="glossary"><a href="#d0e15238">Glossary</a></span></dt><dt><span class="appendix"><a href="#appe-Virtualization_Guide-Revision_Hist
 ory">C. Revision History</a></span></dt><dt><span class="appendix"><a href="#appe-Virtualization_Guide-Colophon">D. Colophon</a></span></dt></dl></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h1 id="pref-Virtualization_Guide-Preface" class="title">Preface</h1></div></div></div><div class="para">
		This book is the Fedora 12 Virtualization Guide. The Guide covers all aspects of using and managing virtualization on Fedora 12.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-About_this_book">1. About this book</h2></div></div></div><div class="para">
		This book is divided into 7 parts: 
		<div class="itemizedlist"><ul><li><div class="para">
					System Requirements
				</div></li><li><div class="para">
					Installation
				</div></li><li><div class="para">
					Configuration
				</div></li><li><div class="para">
					Administration
				</div></li><li><div class="para">
					Reference
				</div></li><li><div class="para">
					Tips and Tricks
				</div></li><li><div class="para">
					Troubleshooting
				</div></li></ul></div>
	</div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="d0e86">2. Document Conventions</h2></div></div></div><div class="para">
		This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
	</div><div class="para">
		In PDF and paper editions, this manual uses typefaces drawn from the <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="d0e96">2.1. Typographic Conventions</h3></div></div></div><div class="para">
			Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
		</div><div class="para">
			<code class="literal">Mono-spaced Bold</code>
		</div><div class="para">
			Used to highlight system input, including shell commands, file names and paths. Also used to highlight key caps and key-combinations. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				To see the contents of the file <code class="filename">my_next_bestselling_novel</code> in your current working directory, enter the <code class="command">cat my_next_bestselling_novel</code> command at the shell prompt and press <span class="keycap"><strong>Enter</strong></span> to execute the command.
			</div></blockquote></div><div class="para">
			The above includes a file name, a shell command and a key cap, all presented in Mono-spaced Bold and all distinguishable thanks to context.
		</div><div class="para">
			Key-combinations can be distinguished from key caps by the hyphen connecting each part of a key-combination. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				Press <span class="keycap"><strong>Enter</strong></span> to execute the command.
			</div><div class="para">
				Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F1</strong></span> to switch to the first virtual terminal. Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F7</strong></span> to return to your X-Windows session.
			</div></blockquote></div><div class="para">
			The first sentence highlights the particular key cap to press. The second highlights two sets of three key caps, each set pressed simultaneously.
		</div><div class="para">
			If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in <code class="literal">Mono-spaced Bold</code>. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				File-related classes include <code class="classname">filesystem</code> for file systems, <code class="classname">file</code> for files, and <code class="classname">dir</code> for directories. Each class has its own associated set of permissions.
			</div></blockquote></div><div class="para">
			<span class="application"><strong>Proportional Bold</strong></span>
		</div><div class="para">
			This denotes words or phrases encountered on a system, including application names; dialogue box text; labelled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				Choose <span class="guimenu"><strong>System > Preferences > Mouse</strong></span> from the main menu bar to launch <span class="application"><strong>Mouse Preferences</strong></span>. In the <span class="guilabel"><strong>Buttons</strong></span> tab, click the <span class="guilabel"><strong>Left-handed mouse</strong></span> check box and click <span class="guibutton"><strong>Close</strong></span> to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
			</div><div class="para">
				To insert a special character into a <span class="application"><strong>gedit</strong></span> file, choose <span class="guimenu"><strong>Applications > Accessories > Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search > Find…</strong></span> from the <span class="application"><strong>Character Map</strong></span> menu bar, type the name of the character in the <span class="guilabel"><strong>Search</strong></span> field and click <span class="guibutton"><strong>Next</strong></span>. The character you sought will be highlighted in the <span class="guilabel"><strong>Character Table</strong></span>. Double-click this highlighted character to place it in the <span class="guilabel"><strong>Text to copy</strong></span> field and then click the <span class="guibutton"><strong>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit > Paste</strong></span> from the <
 span class="application"><strong>gedit</strong></span> menu bar.
			</div></blockquote></div><div class="para">
			The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in Proportional Bold and all distinguishable by context.
		</div><div class="para">
			Note the <span class="guimenu"><strong>></strong></span> shorthand used to indicate traversal through a menu and its sub-menus. This is to avoid the difficult-to-follow 'Select <span class="guimenuitem"><strong>Mouse</strong></span> from the <span class="guimenu"><strong>Preferences</strong></span> sub-menu in the <span class="guimenu"><strong>System</strong></span> menu of the main menu bar' approach.
		</div><div class="para">
			<code class="command"><em class="replaceable"><code>Mono-spaced Bold Italic</code></em></code> or <span class="application"><strong><em class="replaceable"><code>Proportional Bold Italic</code></em></strong></span>
		</div><div class="para">
			Whether Mono-spaced Bold or Proportional Bold, the addition of Italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				To connect to a remote machine using ssh, type <code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>domain.name</code></em></code> at a shell prompt. If the remote machine is <code class="filename">example.com</code> and your username on that machine is john, type <code class="command">ssh john at example.com</code>.
			</div><div class="para">
				The <code class="command">mount -o remount <em class="replaceable"><code>file-system</code></em></code> command remounts the named file system. For example, to remount the <code class="filename">/home</code> file system, the command is <code class="command">mount -o remount /home</code>.
			</div><div class="para">
				To see the version of a currently installed package, use the <code class="command">rpm -q <em class="replaceable"><code>package</code></em></code> command. It will return a result as follows: <code class="command"><em class="replaceable"><code>package-version-release</code></em></code>.
			</div></blockquote></div><div class="para">
			Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
		</div><div class="para">
			Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				When the Apache HTTP Server accepts requests, it dispatches child processes or threads to handle them. This group of child processes or threads is known as a <em class="firstterm">server-pool</em>. Under Apache HTTP Server 2.0, the responsibility for creating and maintaining these server-pools has been abstracted to a group of modules called <em class="firstterm">Multi-Processing Modules</em> (<em class="firstterm">MPMs</em>). Unlike other modules, only one module from the MPM group can be loaded by the Apache HTTP Server.
			</div></blockquote></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="d0e312">2.2. Pull-quote Conventions</h3></div></div></div><div class="para">
			Two, commonly multi-line, data types are set off visually from the surrounding text.
		</div><div class="para">
			Output sent to a terminal is set in <code class="computeroutput">Mono-spaced Roman</code> and presented thus:
		</div><pre class="screen">
books        Desktop   documentation  drafts  mss    photos   stuff  svn
books_tests  Desktop1  downloads      images  notes  scripts  svgs
</pre><div class="para">
			Source-code listings are also set in <code class="computeroutput">Mono-spaced Roman</code> but are presented and highlighted as follows:
		</div><pre class="programlisting">
package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

public class ExClient
{
   public static void main(String args[]) 
       throws Exception
   {
      InitialContext iniCtx = new InitialContext();
      Object         ref    = iniCtx.lookup("EchoBean");
      EchoHome       home   = (EchoHome) ref;
      Echo           echo   = home.create();

      System.out.println("Created Echo");

      System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
   }
   
}
</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="d0e331">2.3. Notes and Warnings</h3></div></div></div><div class="para">
			Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
		</div><div class="note"><h2>Note</h2><div class="para">
				A Note is a tip or shortcut or alternative approach to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
			</div></div><div class="important"><h2>Important</h2><div class="para">
				Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring Important boxes won't cause data loss but may cause irritation and frustration.
			</div></div><div class="warning"><h2>Warning</h2><div class="para">
				A Warning should not be ignored. Ignoring warnings will most likely cause data loss.
			</div></div></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="d0e351">3. We Need Feedback!</h2></div></div></div><a id="d0e354" class="indexterm"/><div class="para">
		If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: <a href="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</a>
		against the product <span class="application"><strong>Fedora Documentation.</strong></span>
	</div><div class="para">
		When submitting a bug report, be sure to mention the manual's identifier: <em class="citetitle">Virtualization_Guide</em>
	</div><div class="para">
		If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
	</div></div></div><div class="part" lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="part-Virtualization_Guide-Installation">Part I. Installation</h1></div></div></div><div class="partintro" lang="en-US"><div><div><div><h1 id="part-Virtualization_Guide-Installation-Virtualization_installation_topics" class="title">Virtualization installation topics</h1></div></div></div><div class="para">
				These chapters describe setting up the host and installing virtualized guests with Fedora. It is recommended to read these chapters carefully to ensure successful installation of virtualized guest operating systems.
			</div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Installing_the_virtualization_packages">1. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_with_a_new_Fedora_installation">1.1. Installing Xen with a new Fedora installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system">1.2. Installing Xen packages on an existing Fedora system</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation">1.3. Installing KVM with a new Fedora installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Insta
 lling_KVM_packages_on_an_existing_Fedora_system">1.4. Installing KVM packages on an existing Fedora system</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Virtualized_guest_installation_overview">2. Virtualized guest installation overview</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_install">2.1. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager">2.2. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE">2.3. Installing guests with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Guide-Guest_operating_system_installation_procedures">3. Guest 
 operating system installation procedures</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_5_as_a_para_virtualized_guest">3.1. Installing Red Hat Enterprise Linux 5 as a para-virtualized guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest">3.2. Installing Red Hat Enterprise Linux as a fully virtualized guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest">3.3. Installing Windows XP as a fully virtualized guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest">3.4. Installing Windows Server 2003 as a fully virtualized guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtu
 alized_guest">3.5. Installing Windows Server 2008 as a fully virtualized guest</a></span></dt></dl></dd></dl></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Installing_the_virtualization_packages">Chapter 1. Installing the virtualization packages</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_with_a_new_Fedora_installation">1.1. Installing Xen with a new Fedora installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system">1.2. Installing Xen packages on an existing Fedora system</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation">1.3. Installing KVM with a n
 ew Fedora installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system">1.4. Installing KVM packages on an existing Fedora system</a></span></dt></dl></div><div class="para">
		Before you can use virtualization, the virtualization packages must be installed on Fedora. Virtualization packages can be installed either during the installation sequence or after installation using the <code class="command">yum</code> command.
	</div><div class="para">
		You can install both the KVM and Xen hypervisors on a single system. The Xen hypervisor uses the <span class="package">kernel-xen</span> package and the KVM hypervisor uses the default Linux kernel with the <span class="package">kvm</span> kernel module. As each hypervisor uses a different kernel only one hypervisor can be active at any given time. fedora recommends to only install one hypervisor, the hypervisor you want to use for virtualization.
	</div><div class="para">
		To change hypervisor from Xen to KVM or KVM to Xen refer to <a class="xref" href="#sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors" title="23.2. Changing between the KVM and Xen hypervisors">Section 23.2, “Changing between the KVM and Xen hypervisors”</a>.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_with_a_new_Fedora_installation">1.1. Installing Xen with a new Fedora installation</h2></div></div></div><div class="para">
			This section covers installing virtualization tools and Xen packages as part of a fresh Fedora installation.
		</div><div class="note"><h2>Need help installing?</h2><div class="para">
				The <em class="citetitle">Fedora 12 Installation Guide</em> (available from <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a>) covers installing Fedora 12 in detail.
			</div></div><div class="procedure"><ol class="1"><li><div class="para">
					Start an interactive Fedora installation from the Fedora 12 Installation CD-ROM, DVD or PXE.
				</div></li><li><div class="para">
					You must enter a valid installation number when prompted to receive access to the virtualization and other Advanced Platform packages.
				</div></li><li><div class="para">
					Complete the other steps up to the package selection step.
				</div><div class="mediaobject"><img src="images/RHELcustomize14.png"/></div><div class="para">
					Select the <span class="guilabel"><strong>Virtualization</strong></span> package group and the <span class="guilabel"><strong>Customize Now</strong></span> radio button.
				</div></li><li><div class="para">
					Select the <span class="guilabel"><strong>Virtualization</strong></span> package group. This selects the Xen hypervisor, <code class="command">virt-manager</code>, <code class="command">libvirt</code> and <code class="command">virt-viewer</code> for installation.
				</div><div class="mediaobject"><img src="images/RHELXenSelect.png"/></div></li><li id="step-Virtualization_Guide-Installing_Xen_with_a_new_Linux_installation-Customize_the_packages_if_required"><p class="title"><b>Customize the packages (if required)</b></p><div class="para">
					Customize the <span class="guilabel"><strong>Virtualization</strong></span> group if you require other virtualization packages.
				</div><div class="mediaobject"><img src="images/RHELXenCustomize.png"/></div><div class="para">
					Press <span class="guilabel"><strong>Close</strong></span> followed by <span class="guilabel"><strong>Next</strong></span> to continue the installation.
				</div></li></ol></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installing_Xen_with_a_new_Linux_installation-Installing_Xen_packages_with_Kickstart_files">Installing Xen packages with Kickstart files</h5>
				This section describes how to use a Kickstart file to install Fedora with the Xen hypervisor packages. Kickstart files allow for large, automated installations without a user manually installing each individual system. The steps in this section will assist you in creating and using a Kickstart file to install Fedora with the virtualization packages.
			</div><div class="para">
			In the <code class="computeroutput">%packages</code> section of your Kickstart file, append the following package group:
		</div><pre class="screen">%packages
@virtualization
</pre><div class="para">
			More information on Kickstart files can be found on the Fedora Project website, <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a>, in the <em class="citetitle">Fedora 12 Installation Guide</em>.
		</div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system">1.2. Installing Xen packages on an existing Fedora system</h2></div></div></div><div class="para">
			The section describes the steps necessary to install the virtualization packages on a working Fedora system.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installing_Xen_packages_on_an_existing_Linux_system-Installing_the_Xen_hypervisor_with_yum">Installing the Xen hypervisor with <code class="command">yum</code></h5>
				To use virtualization on Fedora you need the <code class="filename">xen</code> and <code class="filename">kernel-xen</code> packages. The <code class="filename">xen</code> package contains the hypervisor and basic virtualization tools. The <code class="filename">kernel-xen</code> package contains a modified Linux kernel which runs as a virtual machine guest on the hypervisor.
			</div><div class="para">
			To install the <code class="filename">xen</code> and <code class="filename">kernel-xen</code> packages, run: 
<pre class="screen"># yum install xen kernel-xen
</pre>
		</div><div class="para">
			It is advised to install additional virtualization packages for management and configuration. <a class="xref" href="#vari-Virtualization_Guide-Installing_KVM_packages_on_an_existing_Fedora_system-Recommended_virtualization_packages" title="Recommended virtualization packages:">Recommended virtualization packages:</a> lists the recommended packages.
		</div><div class="variablelist" id="vari-Virtualization_Guide-Installing_Xen_packages_on_an_existing_Fedora_system-Recommended_virtualization_packages"><h6>Recommended virtualization packages:</h6><dl><dt><span class="term"><code class="filename">python-virtinst</code></span></dt><dd><div class="para">
						Provides the <code class="command">virt-install</code> command for creating virtual machines.
					</div></dd><dt><span class="term"><code class="filename">libvirt</code></span></dt><dd><div class="para">
						<code class="filename">libvirt</code> is an API library for interacting with hypervisors. <code class="filename">libvirt</code> uses the <code class="command">xm</code> virtualization framework and the <code class="command">virsh</code> command line tool to manage and control virtual machines.
					</div></dd><dt><span class="term"><code class="filename">libvirt-python</code></span></dt><dd><div class="para">
						The libvirt-python package contains a module that permits applications written in the Python programming language to use the interface supplied by the <code class="filename">libvirt</code> API.
					</div></dd><dt><span class="term"><code class="filename">virt-manager</code></span></dt><dd><div class="para">
						<code class="command">virt-manager</code>, also known as <span class="application"><strong>Virtual Machine Manager</strong></span>, provides a graphical tool for administering virtual machines. It uses <code class="filename">libvirt</code> library as the management API.
					</div></dd></dl></div><div class="para">
			Install the other recommended virtualization packages:
		</div><pre class="screen"># yum install virt-manager libvirt libvirt-python python-virtinst
</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation">1.3. Installing KVM with a new Fedora installation</h2></div></div></div><div class="para">
			This section covers installing virtualization tools and KVM package as part of a fresh Fedora 12 installation.
		</div><div class="note"><h2>Need help installing?</h2><div class="para">
				The <em class="citetitle">Fedora 12 Installation Guide</em> (available from <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a>) covers installing Fedora 12 in detail.
			</div></div><div class="procedure"><ol class="1"><li><div class="para">
					Start an interactive Fedora installation from the Fedora 12 Installation CD-ROM, DVD or PXE.
				</div></li><li><div class="para">
					Complete the other steps up to the package selection step.
[...5606 lines suppressed...]
	</div><div class="para">
		Guests can be identified in any of three <span class="application"><strong>identities</strong></span>: the domain name (<code class="command">domain-name</code>), the identity number (<code class="command">domain-id</code>), or the UUID. The <code class="command">domain-name</code> is a text string that corresponds to a guest configuration file. Theguests name can be used to start guests, and when the guest runs that same name can identify and control it. The domain-id is a unique, non-persistent number that gets assigned to an active domain can identify and control that guest. The UUID is a persistent, unique identifier that is controlled from the guest's configuration file and ensures that the guest is identified over time by system management tools. It is visible to the guest when it runs. A new UUID is automatically assigned to each guest by the system tools when the guest first installs.
	</div></div><div class="appendix" lang="en-US"><div class="titlepage"><div><div><h1 id="appe-Virtualization_Guide-Additional_resources" class="title">Additional resources</h1></div></div></div><div class="para">
		To learn more about virtualization and Linux, refer to the following resources.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Additional_resources-Online_resources">B.1. Online resources</h2></div></div></div><a id="d0e15079" class="indexterm"/><div class="itemizedlist"><ul><li><div class="para">
					<a href="http://www.cl.cam.ac.uk/research/srg/netos/xen/">http://www.cl.cam.ac.uk/research/srg/netos/xen/</a> The project website of the <span class="trademark">Xen</span>â„¢ para-virtualization machine manager from which the Fedora <span class="package">kernel-xen</span> package is derived. The site maintains the upstream xen project binaries and source code and also contains information, architecture overviews, documentation, and related links regarding xen and its associated technologies.
				</div></li><li><div class="para">
					The Xen Community website
				</div><div class="para">
					<a href="http://www.xen.org/">http://www.xen.org/</a>
				</div></li><li><div class="para">
					<a href="http://www.libvirt.org/">http://www.libvirt.org/</a> is the official website for the <code class="command">libvirt</code> virtualization API.
				</div></li><li><div class="para">
					<a href="http://virt-manager.et.redhat.com/">http://virt-manager.et.redhat.com/</a> is the project website for the <span class="application"><strong>Virtual Machine Manager</strong></span> (virt-manager), the graphical application for managing virtual machines.
				</div></li></ul></div><div class="itemizedlist"><ul><li><div class="para">
					Open Virtualization Center
				</div><div class="para">
					<a href="http://www.openvirtualization.com/">http://www.openvirtualization.com</a>
				</div></li><li><div class="para">
					Fedora Documentation
				</div><div class="para">
					<a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a>
				</div></li><li><div class="para">
					Virtualization technologies overview
				</div><div class="para">
					<a href="http://virt.kernelnewbies.org/">http://virt.kernelnewbies.org</a>
				</div></li><li><div class="para">
					Red Hat Emerging Technologies group
				</div><div class="para">
					<a href="http://et.redhat.com/">http://et.redhat.com</a>
				</div></li></ul></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Additional_resources-Installed_documentation">B.2. Installed documentation</h2></div></div></div><a id="d0e15160" class="indexterm"/><div class="itemizedlist"><ul><li><div class="para">
					<code class="filename">/usr/share/doc/xen-<em class="replaceable"><code><version-number></code></em>/</code> is the directory which contains information about the Xen para-virtualization hypervisor and associated management tools, including various example configurations, hardware-specific information, and the current Xen upstream user documentation.
				</div></li><li><div class="para">
					<code class="command">man virsh</code> and <code class="filename">/usr/share/doc/libvirt-<em class="replaceable"><code><version-number></code></em></code> — Contains sub commands and options for the <code class="command">virsh</code> virtual machine management utility as well as comprehensive information about the <code class="filename">libvirt</code> virtualization library API.
				</div></li><li><div class="para">
					<code class="filename">/usr/share/doc/gnome-applet-vm-<em class="replaceable"><code><version-number></code></em></code> — Documentation for the GNOME graphical panel applet that monitors and manages locally-running virtual machines.
				</div></li><li><div class="para">
					<code class="filename">/usr/share/doc/libvirt-python-<em class="replaceable"><code><version-number></code></em></code> — Provides details on the Python bindings for the <code class="filename">libvirt</code> library. The <code class="filename">libvirt-python</code> package allows python developers to create programs that interface with the <code class="filename">libvirt</code> virtualization management library.
				</div></li><li><div class="para">
					<code class="filename">/usr/share/doc/python-virtinst-<em class="replaceable"><code><version-number></code></em></code> — Provides documentation on the <code class="command">virt-install</code> command that helps in starting installations of Fedora and Linux related distributions inside of virtual machines.
				</div></li><li><div class="para">
					<code class="filename">/usr/share/doc/virt-manager-<em class="replaceable"><code><version-number></code></em></code> — Provides documentation on the Virtual Machine Manager, which provides a graphical tool for administering virtual machines.
				</div></li></ul></div></div></div><div class="glossary"><div class="titlepage"><div><div><h2 class="title" id="d0e15238">Glossary</h2></div></div></div><div class="para">
		This glossary is intended to define the terms used in this Installation Guide.
	</div><dl><dt id="glos-Virtualization_Guide-Bare_metal">Bare-metal</dt><dd><div class="para">
				The term bare-metal refers to the underlying physical architecture of a computer. Running an operating system on bare-metal is another way of referring to running an unmodified version of the operating system on the physical hardware. Examples of operating systems running on bare metal are <a class="firstterm" href="#glos-Virtualization_Guide-dom0"><em class="firstterm">dom0</em></a> or a normally installed operating system.
			</div></dd><dt id="glos-Virtualization_Guide-dom0">dom0</dt><dd><div class="para">
				Also known as the <a class="xref" href="#glos-Virtualization_Guide-Host" title="Host">Host</a> or host operating system.
			</div><div class="para">
				<code class="command">dom0</code> refers to the host instance of Linux running the <a class="xref" href="#glos-Virtualization_Guide-Hypervisor" title="Hypervisor">Hypervisor</a> which facilitates virtualization of guest operating systems. Dom0 runs on and manages the physical hardware and resource allocation for itself and the guest operating systems.
			</div></dd><dt id="glos-Virtualization_Guide-Domains">Domains</dt><dd><div class="para">
				<a class="xref" href="#glos-Virtualization_Guide-domU" title="domU">domU</a> and <a class="xref" href="#glos-Virtualization_Guide-Domains" title="Domains">Domains</a> are both domains. Domains run on the <a class="xref" href="#glos-Virtualization_Guide-Hypervisor" title="Hypervisor">Hypervisor</a>. The term domains has a similar meaning to <a class="xref" href="#glos-Virtualization_Guide-Virtual_machines" title="Virtual machines">Virtual machines</a> and the two are technically interchangeable. A domain is a Virtual Machine.
			</div></dd><dt id="glos-Virtualization_Guide-domU">domU</dt><dd><div class="para">
				<code class="command">domU</code> refers to the guest operating system which run on the host system (<a class="xref" href="#glos-Virtualization_Guide-Domains" title="Domains">Domains</a>).
			</div></dd><dt id="glos-Virtualization_Guide-Full_virtualization">Full virtualization</dt><dd><div class="para">
				Xen and KVM can use full virtualization. Full virtualization uses hardware features of the processor to provide total abstraction of the underlying physical system (<a class="xref" href="#glos-Virtualization_Guide-Bare_metal" title="Bare-metal">Bare-metal</a>) and create a new virtual system in which the guest operating systems can run. No modifications are needed in the guest operating system. The guest operating system and any applications on the guest are not aware of the virtualized environment and run normally. Para-virtualization requires a modified version of the Linux operating system.
			</div></dd><dt id="glos-Virtualization_Guide-Fully_virtualized">Fully virtualized</dt><dd><div class="para">
				See <a class="xref" href="#glos-Virtualization_Guide-Full_virtualization" title="Full virtualization">Full virtualization</a>.
			</div></dd><dt id="glos-Virtualization_Guide-Guest_system">Guest system</dt><dd><div class="para">
				Also known as guests, virtual machines or <a class="xref" href="#glos-Virtualization_Guide-domU" title="domU">domU</a>.
			</div></dd><dt id="glos-Virtualization_Guide-Hardware_Virtual_Machine">Hardware Virtual Machine</dt><dd><div class="para">
				See <a class="xref" href="#glos-Virtualization_Guide-Full_virtualization" title="Full virtualization">Full virtualization</a>
			</div></dd><dt id="glos-Virtualization_Guide-Hypervisor">Hypervisor</dt><dd><div class="para">
				The hypervisor is the software layer that abstracts the hardware from the operating system permitting multiple operating systems to run on the same hardware. The hypervisor runs on a host operating system allowing other virtualized operating systems to run on the host's hardware.
			</div></dd><dt id="glos-Virtualization_Guide-Host">Host</dt><dd><div class="para">
				The host operating system, also known as <a class="xref" href="#glos-Virtualization_Guide-dom0" title="dom0">dom0</a>.
			</div><div class="para">
				The host operating system environment runs the virtualization software for <a class="xref" href="#glos-Virtualization_Guide-Fully_virtualized" title="Fully virtualized">Fully virtualized</a> and <a class="xref" href="#glos-Virtualization_Guide-Para_virtualized" title="Para-virtualized">Para-virtualized</a> guest systems.
			</div></dd><dt id="glos-Virtualization_Guide-IO">I/O</dt><dd><div class="para">
				Short for input/output (pronounced "eye-oh"). The term I/O describes any program, operation or device that transfers data to or from a computer and to or from a peripheral device. Every transfer is an output from one device and an input into another. Devices such as keyboards and mouses are input-only devices while devices such as printers are output-only. A writable CD-ROM is both an input and an output device.
			</div></dd><dt id="glos-Virtualization_Guide-Kernel_based_Virtual_Machine">Kernel-based Virtual Machine</dt><dd><div class="para">
				KVM (Kernel-based Virtual Machine) is a <a class="xref" href="#glos-Virtualization_Guide-Full_virtualization" title="Full virtualization">Full virtualization</a> solution for Linux on AMD64 and Intel 64 hardware. VM is a Linux kernel module built for the standard Linux kernel. KVM can run multiple, unmodified virtualized guest Windows and Linux operating systems. KVM is a hypervisor which uses the libvirt virtualization tools (virt-manager and virsh).
			</div><div class="para">
				KVM is a set of Linux kernel modules which manage devices, memory and management APIs for the Hypervisor module itself. Virtualized guests are run as Linux processes and threads which are controlled by these modules.
			</div></dd><dt id="glos-Virtualization_Guide-LUN">LUN</dt><dd><div class="para">
				A Logical Unit Number (LUN) is a number assigned to a logical unit (a SCSI protocol entity).
			</div></dd><dt id="glos-Virtualization_Guide-Migration">Migration</dt><dd><div class="para">
				Migration is name for the process of moving a virtualized guest from one host to another. Migration can be conducted offline (where the guest is suspended and then moved) or live (where a guest is moved without suspending). Xen fully virtualized guests, Xen para-virtualized guest and KVM fully virtualized guests can all be migrated.
			</div><div class="para">
				Migration is a key feature of virtualization as software is completely separated from hardware. Migration is useful for:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Load balancing - guests can be moved to hosts with lower usage when a host becomes overloaded.
					</div></li><li><div class="para">
						Hardware failover - when hardware devices on the host start to fail, guests can be safely relocated so the host can be powered down and repaired.
					</div></li><li><div class="para">
						Energy saving - guests can be redistributed to other hosts and host systems powered off to save energy and cut costs in low usage periods.
					</div></li><li><div class="para">
						Geographic migration - guests can be moved to another location for lower latency or in serious circumstances.
					</div></li></ul></div><div class="para">
				Shared, networked storage is used for storing guest images. Without shared storage migration is not possible.
			</div><div class="para">
				An offline migration suspends the guest then moves an image of the guests memory to the destination host. The guest is resumed on the destination host and the memory the guest used on the source host is freed.
			</div><div class="para">
				The time an offline migration takes depends network bandwidth and latency. A guest with 2GB of memory should take several seconds on a 1 Gbit Ethernet link.
			</div><div class="para">
				A live migration keeps the guest running on the source host and begins moving the memory without stopping the guest. All modified memory pages are tracked and sent to the destination after the image is sent. The memory is updated with the changed pages. The process continues until it reaches some heuristic; either it successfully copied all the pages over, or the source is changing too fast and the destination host cannot make progress. If the heuristic is met the guest is briefly paused on the source host and the registers and buffers are sent. The registers are loaded on the new host and the guest is then resumed on the destination host. If the guest cannot be merged (which happens when guests are under extreme loads) the guest is paused and then an offline migration is started instead.
			</div><div class="para">
				The time an offline migration takes depends network bandwidth and latency as well as activity on the guest. If the guest is using significant I/O or CPU the migration will take much longer.
			</div></dd><dt id="glos-Virtualization_Guide-MAC_Addresses">MAC Addresses</dt><dd><div class="para">
				The Media Access Control Address is the hardware address for a Network Interface Controller. In the context of virtualization MAC addresses must be generated for virtual network interfaces with each MAC on your local domain being unique.
			</div></dd><dt id="glos-Virtualization_Guide-Para_virtualization">Para-virtualization</dt><dd><div class="para">
				Para-virtualization uses a special kernel, sometimes referred to as the Xen kernel or the <span class="package">kernel-xen</span> package. Para-virtualized guest kernels are run concurrently on the host while using the host's libraries and devices. A para-virtualized installation can have complete access to all devices on the system which can be limited with security settings (SELinux and file controls). Para-virtualization is faster than full virtualization. Para-virtualization can effectively be used for load balancing, provisioning, security and consolidation advantages.
			</div><div class="para">
				As of Fedora 9 a special kernel will no longer be needed. Once this patch is accepted into the main Linux tree all Linux kernels after that version will have para-virtualization enabled or available.
			</div></dd><dt id="glos-Virtualization_Guide-Para_virtualized">Para-virtualized</dt><dd><div class="para">
				See <a class="xref" href="#glos-Virtualization_Guide-Para_virtualization" title="Para-virtualization">Para-virtualization</a>,
			</div></dd><dt id="glos-Virtualization_Guide-Para_virtualized_drivers">Para-virtualized drivers</dt><dd><div class="para">
				Para-virtualized drivers are device drivers that operate on fully virtualized Linux guests. These drivers greatly increase performance of network and block device I/O for fully virtualized guests.
			</div></dd><dt id="glos-Virtualization_Guide-Security_Enhanced_Linux">Security Enhanced Linux</dt><dd><div class="para">
				Short for Security Enhanced Linux, SELinux uses Linux Security Modules (LSM) in the Linux kernel to provide a range of minimum privilege required security policies.
			</div></dd><dt id="glos-Virtualization_Guide-Universally_Unique_Identifier">Universally Unique Identifier</dt><dd><div class="para">
				A Universally Unique Identifier (UUID) is a standardized numbering method for devices, systems and certain software objects in distributed computing environments. Types of UUIDs in virtualization include: <code class="systemitem">ext2</code> and <code class="systemitem">ext3</code> file system identifiers, RAID device identifiers, iSCSI and LUN device identifiers, MAC addresses and virtual machine identifiers.
			</div></dd><dt id="glos-Virtualization_Guide-Virtualization">Virtualization</dt><dd><div class="para">
				Virtualization is a board computing term for running software, usually operating systems, concurrently and isolated from other programs on one system. Most existing implementations of virtualization use a hypervisor, a software layer on top of an operating system, to abstract hardware. The hypervisor allows multiple operating systems to run on the same physical system by giving the guest operating system virtualized hardware. There are various methods for virtualizing operating systems: 
				<div class="itemizedlist"><ul><li><div class="para">
							Hardware-assisted virtualization is the technique used for full virtualization with Xen and KVM (definition: <a class="xref" href="#glos-Virtualization_Guide-Full_virtualization" title="Full virtualization">Full virtualization</a>)
						</div></li><li><div class="para">
							Para-virtualization is a technique used by Xen to run Linux guests (definition: <a class="xref" href="#glos-Virtualization_Guide-Para_virtualization" title="Para-virtualization">Para-virtualization</a>)
						</div></li><li><div class="para">
							Software virtualization or emulation. Software virtualization uses binary translation and other emulation techniques to run unmodified operating systems. Software virtualization is significantly slower than hardware-assisted virtualization or para-virtualization. 
						</div></li></ul></div>
			</div></dd><dt id="glos-Virtualization_Guide-Virtualized_CPU">Virtualized CPU</dt><dd><div class="para">
				A system has a number of virtual CPUs (VCPUs) relative to the number of physical processor cores. The number of virtual CPUs is finite and represents the total number of virtual CPUs that can be assigned to guest virtual machines.
			</div></dd><dt id="glos-Virtualization_Guide-Virtual_machines">Virtual machines</dt><dd><div class="para">
				A virtual machine is a software implementation of a physical machine or programming language (for example the Java Runtime Environment or LISP). Virtual machines in the context of virtualization are operating systems running on virtualized hardware.
			</div></dd><dt id="glos-Virtualization_Guide-Xen">Xen</dt><dd><div class="para">
				Fedora supports the Xen hypervisor and the KVM hypervisor (refer to <a class="xref" href="#glos-Virtualization_Guide-Kernel_based_Virtual_Machine" title="Kernel-based Virtual Machine">Kernel-based Virtual Machine</a>). Both hypervisors have different architectures and development approaches. The Xen hypervisor runs underneath a Linux operating system which acts as a host managing system resources and virtualization APIs. The host is sometimes referred to as as <a class="xref" href="#glos-Virtualization_Guide-dom0" title="dom0">dom0</a> or Domain0.
			</div><div class="mediaobject"><img src="images/Xen_full_virtualization_architecture.png"/></div><div class="mediaobject"><img src="images/Xen_para-virtualization_architecture.png"/></div></dd></dl></div><div class="appendix" lang="en-US"><div class="titlepage"><div><div><h1 id="appe-Virtualization_Guide-Revision_History" class="title">Revision History</h1></div></div></div><div class="para">
		<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 5.4-61</td><td align="left">Wed Sep 30 2009</td><td align="left"><span class="author"><span class="firstname">Christopher</span> <span class="surname">Curran</span></span></td></tr><tr><td align="left" colspan="3">
					<table class="simplelist" border="0" summary="Simple list"><tr><td>Split from Red Hat Enterprise Linux 5.4 Virtualization Guide version 5.4-61.</td></tr></table>
				</td></tr></table></div>
	</div></div><div class="appendix" lang="en-US"><div class="titlepage"><div><div><h1 id="appe-Virtualization_Guide-Colophon" class="title">Colophon</h1></div></div></div><div class="para">
		This manual was written in the DocBook XML v4.3 format.
	</div><div class="para">
		This book is based on the work of Jan Mark Holzer and Chris Curran.
	</div><div class="para">
		Other writing credits go to:
	</div><div class="itemizedlist"><ul><li><div class="para">
				Don Dutile contributed technical editing for the para-virtualized drivers section.
			</div></li><li><div class="para">
				Barry Donahue contributed technical editing for the para-virtualized drivers section.
			</div></li><li><div class="para">
				Rick Ring contributed technical editing for the Virtual Machine Manager Section.
			</div></li><li><div class="para">
				Michael Kearey contributed technical editing for the sections on using XML configuration files with virsh and virtualized floppy drives.
			</div></li><li><div class="para">
				Marco Grigull contributed technical editing for the software compatibility and performance section.
			</div></li><li><div class="para">
				Eugene Teo contributed technical editing for the Managing Guests with virsh section.
			</div></li></ul></div><div class="para">
		Publican, the publishing tool which produced this book, was written by Jeffrey Fearn.
	</div><div class="para">
		The Red Hat Localization Team consists of the following people:
	</div><div class="itemizedlist" id="item-Virtualization_Guide-Colophon-East_Asian_Languages"><h6>East Asian Languages</h6><ul><li><div class="para">
				Simplified Chinese
			</div><div class="itemizedlist"><ul><li><div class="para">
						Leah Wei Liu
					</div></li></ul></div></li><li><div class="para">
				Traditional Chinese
			</div><div class="itemizedlist"><ul><li><div class="para">
						Chester Cheng
					</div></li><li><div class="para">
						Terry Chuang
					</div></li></ul></div></li><li><div class="para">
				Japanese
			</div><div class="itemizedlist"><ul><li><div class="para">
						Junko Ito
					</div></li></ul></div></li><li><div class="para">
				Korean
			</div><div class="itemizedlist"><ul><li><div class="para">
						Eun-ju Kim
					</div></li></ul></div></li></ul></div><div class="itemizedlist" id="item-Virtualization_Guide-Colophon-Latin_Languages"><h6>Latin Languages</h6><ul><li><div class="para">
				French
			</div><div class="itemizedlist"><ul><li><div class="para">
						Sam Friedmann
					</div></li></ul></div></li><li><div class="para">
				German
			</div><div class="itemizedlist"><ul><li><div class="para">
						Hedda Peters
					</div></li></ul></div></li><li><div class="para">
				Italian
			</div><div class="itemizedlist"><ul><li><div class="para">
						Francesco Valente
					</div></li></ul></div></li><li><div class="para">
				Brazilian Portuguese
			</div><div class="itemizedlist"><ul><li><div class="para">
						Glaucia de Freitas
					</div></li><li><div class="para">
						Leticia de Lima
					</div></li></ul></div></li><li><div class="para">
				Spanish
			</div><div class="itemizedlist"><ul><li><div class="para">
						Angela Garcia
					</div></li><li><div class="para">
						Gladys Guerrero
					</div></li></ul></div></li><li><div class="para">
				Russian
			</div><div class="itemizedlist"><ul><li><div class="para">
						Yuliya Poyarkova
					</div></li></ul></div></li></ul></div></div></div></body></html>




More information about the Fedora-docs-commits mailing list