Sat Oct 3 08:06:11 UTC 2009

Author: rlandmann

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

Added Files:
	appe-Virtualization_Guide-Additional_resources.html 
	appe-Virtualization_Guide-Colophon.html 
	appe-Virtualization_Guide-Revision_History.html 
	appe-Virtualization_Guide-Xen_system_architecture_.html 
	chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters.html 
	chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html 
	chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html 
	chap-Virtualization_Guide-Installing_the_virtualization_packages.html 
	chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html 
	chap-Virtualization_Guide-KVM_guest_timing_management.html 
	chap-Virtualization_Guide-KVM_live_migration.html 
	chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html 
	chap-Virtualization_Guide-Managing_guests_with_virsh.html 
	chap-Virtualization_Guide-Managing_guests_with_xend.html 
	chap-Virtualization_Guide-Network_Configuration.html 
	chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html 
	chap-Virtualization_Guide-Security_for_virtualization.html 
	chap-Virtualization_Guide-Server_best_practices.html 
	chap-Virtualization_Guide-Shared_storage_and_virtualization.html 
	chap-Virtualization_Guide-The_xm_command_quick_reference.html 
	chap-Virtualization_Guide-Tips_and_tricks.html 
	chap-Virtualization_Guide-Troubleshooting.html 
	chap-Virtualization_Guide-Troubleshooting_Xen.html 
	chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html 
	chap-Virtualization_Guide-Virtualization_tools.html 
	chap-Virtualization_Guide-Virtualized_block_devices.html 
	chap-Virtualization_Guide-Virtualized_guest_installation_overview.html 
	chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html 
	chap-Virtualization_Guide-Xen_configuration_files.html 
	chap-Virtualization_Guide-Xen_live_migration.html 
	chap-Virtualization_Guide-Xen_networking.html go01.html 
	index.html part-Virtualization_Guide-Administration.html 
	part-Virtualization_Guide-Configuration.html 
	part-Virtualization_Guide-Installation.html 
	part-Virtualization_Guide-Tips_and_Tricks.html 
	part-Virtualization_Guide-Troubleshooting.html 
	part-Virtualization_Guide-Virtualization_Reference_Guide.html 
	pr01s02.html pr01s02s02.html pr01s02s03.html pr01s03.html 
	pref-Virtualization_Guide-Preface.html 
	sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtual_Storage_Devices.html 
	sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html 
	sect-Virtualization_Guide-Additional_resources-Installed_documentation.html 
	sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-KVM_to_Xen.html 
	sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_3.html 
	sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_4.html 
	sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_5.html 
	sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest.html 
	sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest.html 
	sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest.html 
	sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest.html 
	sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html 
	sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system.html 
	sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation.html 
	sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system.html 
	sect-Virtualization_Guide-KVM_live_migration-Live_KVM_migration_with_virsh.html 
	sect-Virtualization_Guide-KVM_live_migration-Migrating_with_virt_manager.html 
	sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Creating_a_virtual_network.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_a_guests_status_.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_memory_usage_.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Restoring_a_saved_machine_.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html 
	sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html 
	sect-Virtualization_Guide-Network_Configuration-Bridged_networking_with_libvirt.html 
	sect-Virtualization_Guide-Para_virtualized_Network_Driver_Configuration.html 
	sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html 
	sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes.html 
	sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html 
	sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests.html 
	sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests.html 
	sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html 
	sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files.html 
	sect-Virtualization_Guide-Tips_and_tricks-Cloning_guest_configuration_files.html 
	sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html 
	sect-Virtualization_Guide-Tips_and_tricks-Configuring_Xen_processor_affinities.html 
	sect-Virtualization_Guide-Tips_and_tricks-Configuring_a_VNC_Server.html 
	sect-Virtualization_Guide-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html 
	sect-Virtualization_Guide-Tips_and_tricks-Duplicating_an_existing_guest_and_its_configuration_file.html 
	sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address.html 
	sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation.html 
	sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest.html 
	sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html 
	sect-Virtualization_Guide-Tips_and_tricks-Modifying_the_Xen_hypervisor.html 
	sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html 
	sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img.html 
	sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html 
	sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd.html 
	sect-Virtualization_Guide-Troubleshooting-A_missing_localhost_entry_causes_virt_manager_to_fail.html 
	sect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes.html 
	sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html 
	sect-Virtualization_Guide-Troubleshooting-Failed_domain_creation_caused_by_a_memory_shortage.html 
	sect-Virtualization_Guide-Troubleshooting-Fully_virtualized_64_bit_guest_fails_to_boot.html 
	sect-Virtualization_Guide-Troubleshooting-Loop_device_errors.html 
	sect-Virtualization_Guide-Troubleshooting-Microcode_error_during_guest_boot.html 
	sect-Virtualization_Guide-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine.html 
	sect-Virtualization_Guide-Troubleshooting-Virtualized_Ethernet_devices_are_not_found_by_networking_tools.html 
	sect-Virtualization_Guide-Troubleshooting-Wrong_bridge_configured_on_the_guest_causing_hot_plug_script_timeouts.html 
	sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error.html 
	sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error_non_PAE_kernel_on_a_PAE_platform.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Common_Xen_problems.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Guest_configuration_files.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Para_virtualized_guest_console_access.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-The_layout_of_the_log_directories.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs.html 
	sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_serial_console.html 
	sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers.html 
	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.html 
	sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-The_system_has_limited_throughput_with_para_virtualized_drivers.html 
	sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_have_successfully_loaded.html 
	sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_from_fully_virtualized_guests.html 
	sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_para_virtualized_guests.html 
	sect-Virtualization_Guide-Virtualized_block_devices-Add_a_virtualized_CD_ROM_or_DVD_device_to_a_guest.html 
	sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests.html 
	sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html 
	sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager.html 
	sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html 
	sect-Virtualization_Guide-Xen_live_migration-Configuring_guest_live_migration.html 
	sect-Virtualization_Guide-Xen_networking-Laptop_network_configuration.html 
Log Message:
add F12 Virtualization Guide draft

--- NEW FILE appe-Virtualization_Guide-Additional_resources.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>AppendixÂ B.Â Additional resources</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="appe-Virtualization_Guide-Xen_system_architecture_.html" title="AppendixÂ A.Â Xen system architecture"/><link rel="next" href="sect-Virtualization_Guide-Additional_resources-Installed_documentation.html" title="B.2.Â Installed documentation"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p
 ><ul class="docnav"><li class="previous"><a accesskey="p" href="appe-Virtualization_Guide-Xen_system_architecture_.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Additional_resources-Installed_documentation.html"><strong>Next</strong></a></li></ul><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><ul class="docnav"><li class="previous"><a accesskey="p" href="appe-Virtualization_Guide-Xen_system_architecture_.html"><strong>Prev</strong>AppendixÂ A.Â Xen system architecture </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Additional_resources-Installed_documentation.html"><strong>Next</strong>B.2.Â Installed documentation</a></li></ul></body></html>

--- NEW FILE appe-Virtualization_Guide-Colophon.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>AppendixÂ D.Â Colophon</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="appe-Virtualization_Guide-Revision_History.html" title="AppendixÂ C.Â Revision History"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="appe-Virtualization_Guide-Revision_History.html"><strong>Prev</strong></a></li><li class="next"/></ul>
 <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><ul class="docnav"><li class="previous"><a accesskey="p" href="appe-Virtualization_Guide-Revision_History.html"><strong>Prev</strong>AppendixÂ C.Â Revision History</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li></ul></body></html>

--- NEW FILE appe-Virtualization_Guide-Revision_History.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>AppendixÂ C.Â Revision History</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="go01.html" title="Glossary"/><link rel="next" href="appe-Virtualization_Guide-Colophon.html" title="AppendixÂ D.Â Colophon"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="go01.html"><strong>Prev</strong></a></li><li class="next">
 <a accesskey="n" href="appe-Virtualization_Guide-Colophon.html"><strong>Next</strong></a></li></ul><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><ul class="docnav"><li class="previous"><a accesskey="p" href="go01.html"><strong>Prev</strong>Glossary</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="appe-Virtualization_Guide-Colophon.html"><strong>Next</strong>AppendixÂ D.Â Colophon</a></li></ul></body></html>

--- NEW FILE appe-Virtualization_Guide-Xen_system_architecture_.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>AppendixÂ A.Â Xen system architecture</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-The_system_has_limited_throughput_with_para_virtualized_drivers.html" title="27.5.Â The system has limited throughput with para-virtualized drivers"/><link rel="next" href="appe-Virtualization_Guide-Additional_resources.html" title="AppendixÂ B.Â Additional resources"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://d
 ocs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-The_system_has_limited_throughput_with_para_virtualized_drivers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-Virtualization_Guide-Additional_resources.html"><strong>Next</strong></a></li></ul><div class="appendix" lang="en-US"><div class="titlepage"><div><div><h1 id="appe-Virtualization_Guide-Xen_system_architecture_" class="title">Xen system architecture </h1></div></div></div><div class="para">
		A functional Linux system with virtualization is multi-layered and is driven by the privileged Xen kernel component. Xen can host multiple guest operating systems. Each guest operating system runs in its own domain. Xen schedules virtual CPUs within the virtual machines to make the best use of the available physical CPUs. Each guest operating systems handles its own applications. These guest operating systems schedule each application accordingly.
	</div><div class="para">
		You can deploy Xen in one of two choices: <a class="firstterm" href="go01.html#glos-Virtualization_Guide-Full_virtualization"><em class="firstterm">full virtualization</em></a> or <a class="firstterm" href="go01.html#glos-Virtualization_Guide-Para_virtualization"><em class="firstterm">para-virtualization</em></a>. Full virtualization provides total abstraction of the underlying physical system and creates a new virtual system in which the guest operating systems can run. No modifications are needed in the guest OS or application (the guest OS or application is not aware of the virtualized environment and runs normally). Para-virtualization requires user modification of the guest operating systems that run on the virtual machines (these guest operating systems are aware that they are running on a virtual machine) and provide near-native performance. You can deploy both para-virtualization and full virtualization across your virtualization infrastructure.
	</div><div class="para">
		The first domain, known as <span class="application"><strong>domain0</strong></span> (dom0), is automatically created when you boot the system. Domain0 is the privileged guest and it possesses management capabilities which can create new domains and manage their virtual devices. Domain0 handles the physical hardware, such as network cards and hard disk controllers. Domain0 also handles administrative tasks such as suspending, resuming, or migrating guest domains to other virtual machines.
	</div><div class="para">
		The <span class="application"><strong>hypervisor</strong></span> (fedora's Virtual Machine Monitor) is a virtualization platform that allows multiple operating systems to run on a single host simultaneously within a full virtualization environment. A guest is an operating system (OS) that runs on a virtual machine in addition to the host or main OS.
	</div><div class="para">
		With Xen, each guests <span class="application"><strong>memory</strong></span> comes from a slice of the host's physical memory. For para-virtualized guests, you can set both the initial memory and the maximum size of the virtual machine. You can add (or remove) physical memory to the virtual machine at runtime without exceeding the maximum size you specify. This process is called ballooning.
	</div><div class="para">
		You can configure each guest with a number of virtual <span class="application"><strong>cpus</strong></span> (called VCPUs). VCPUs are scheduled according to the workload on the physical CPUs.
	</div><div class="para">
		You can grant a guest any number of <span class="application"><strong>virtual disks</strong></span>. The guest sees these as either hard disks or (for full virtual guests) as CD-ROM drives. Each virtual disk is served to the guest from a block device or from a regular file on the host. The device on the host contains the entire full disk image for the guest, and usually includes partition tables, multiple partitions, and potentially LVM physical volumes.
	</div><div class="para">
		<span class="application"><strong>Virtual networking interfaces</strong></span> runs on the guest. Other interfaces can run on the guest like virtual Ethernet Internet cards (VNICs). These network interfaces are configured with a persistent virtual media access control (MAC) address. The default installation of a new guest installs the VNIC with a MAC address selected at random from a reserved pool of over 16 million addresses, so it is unlikely that any two guests will receive the same MAC address. Complex sites with a large number of guests can allocate MAC addresses manually to ensure that they remain unique on the network.
	</div><div class="para">
		Each guest has a virtual <span class="application"><strong>text console</strong></span> that connects to the host. You can redirect guest log in and console output to the text console.
	</div><div class="para">
		You can configure any guest to use a virtual <span class="application"><strong>graphical console</strong></span> that corresponds to the normal video console on the physical host. You can do this for full virtual and para-virtualized guests. It employs the features of the standard graphic adapter like boot messaging, graphical booting, multiple virtual terminals, and can launch the X window system. You can also use the graphical keyboard to configure the virtual keyboard and mouse.
	</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><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-The_system_has_limited_throughput_with_para_virtualized_drivers.html"><strong>Prev</strong>27.5.Â The system has limited throughput with para...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="appe-Virtualization_Guide-Additional_resources.html"><strong>Next</strong>AppendixÂ B.Â Additional resources</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 21.Â Configuring the Xen kernel boot parameters</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html" title="PartÂ IV.Â Virtualization Reference Guide"/><link rel="prev" href="chap-Virtualization_Guide-The_xm_command_quick_reference.html" title="ChapterÂ 20.Â The xm command quick reference"/><link rel="next" href="chap-Virtualization_Guide-Xen_configuration_files.html" title="ChapterÂ 22.Â Xen configuration files"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedorap
 roject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-The_xm_command_quick_reference.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Xen_configuration_files.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters">ChapterÂ 21.Â Configuring the Xen kernel boot parameters</h2></div></div></div><div class="para">
		The GNU Grand Unified Boot Loader (GRUB) is a program for booting various installed operating systems or kernels. GRUB also allows the user to pass arguments to the kernel. The GRUB configuration file (located in <code class="command">/boot/grub/grub.conf</code>) creates the list of operating systems the GRUB boot menu interface. When you install the <code class="command">kernel-xen</code> RPM, a script adds the <code class="command">kernel-xen</code> entry to the GRUB configuration file which boots <code class="command">kernel-xen</code> by default. Edit the <code class="command">grub.conf</code> file to modify the default kernel or to add additional kernel parameters.
	</div><pre class="screen">title Fedora (2.6.23.14-107.fc8xen)
root (hd0,0)
	kernel  /xen.gz.-2.6.23.14-107.fc8
	module  /vmlinuz-2.6.23.14-107.fc8xen ro root=/dev/VolGroup00/LogVol00  rhgb quiet
	module  /initrd-2.6.23.14-107.fc8xen.img
</pre><div class="para">
		If you set your Fedora grub entries to reflect this example, the boot loader loads the hypervisor, <code class="command">initrd </code>image, and Linux kernel. Since the kernel entry is on top of the other entries, the kernel loads into memory first. The boot loader sends, and receives, command line arguments to and from the hypervisor and Linux kernel. This example entry shows how you would restrict the Dom0 Linux kernel memory to 800 MB.
	</div><pre class="screen">title Fedora (2.6.23.14-107.fc8xen)
root (hd0,0)
	kernel  /xen.gz.-2.6.23.14-107.fc8 dom0_mem=800M
	module  /vmlinuz-2.6.23.14-107.fc8xen ro root=/dev/VolGroup00/LogVol00  rhgb quiet
	module  /initrd-2.6.23.14-107.fc8xen.img
</pre><div class="para">
		You can use these GRUB parameters to configure the Virtualization hypervisor:
	</div><pre class="screen">mem
</pre><div class="para">
		This limits the amount of memory that is available to the hypervisor kernel.
	</div><pre class="screen">com1=115200, 8n1
</pre><div class="para">
		This enables the first serial port in the system to act as serial console (com2 is assigned for the next port, and so on).
	</div><pre class="screen">dom0_mem
</pre><div class="para">
		This limits the memory available for the hypervisor.
	</div><pre class="screen">dom0_max_vcpus
</pre><div class="para">
		This limits the amount of CPUs visible to the Xen domain0.
	</div><pre class="screen">acpi
</pre><div class="para">
		This switches the ACPI hypervisor to the hypervisor and domain0. The ACPI parameter options include:
	</div><pre class="screen">/*   ****  Linux config options: propagated to domain0  ****/
/*   "acpi=off":      Disables both ACPI table parsing and interpreter.   */
/*   "acpi=force":    Overrides the disable blacklist.                    */
/*   "acpi=strict":   Disables out-of-spec workarounds.                   */
/*   "acpi=ht":       Limits ACPI from boot-time to enable HT.            */
/*   "acpi=noirq":    Disables ACPI interrupt routing.                    */
</pre><pre class="screen">noacpi
</pre><div class="para">
		This disables ACPI for interrupt delivery.
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-The_xm_command_quick_reference.html"><strong>Prev</strong>ChapterÂ 20.Â The xm command quick reference</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Xen_configuration_files.html"><strong>Next</strong>ChapterÂ 22.Â Xen configuration files</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 24.Â Creating custom libvirt scripts</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Tips_and_Tricks.html" title="PartÂ V.Â Tips and Tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Duplicating_an_existing_guest_and_its_configuration_file.html" title="23.18.Â Duplicating an existing guest and its configuration file"/><link rel="next" href="part-Virtualization_Guide-Troubleshooting.html" title="PartÂ VI.Â Troubleshooting"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedora
 project.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Duplicating_an_existing_guest_and_its_configuration_file.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Troubleshooting.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Creating_custom_libvirt_scripts">ChapterÂ 24.Â Creating custom libvirt scripts</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html#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></div><div class="para">
		This section provides some information which may be useful to programmers and system administrators intending to write custom scripts to make their lives easier by using <code class="command">libvirt</code>.
	</div><div class="para">
		<a class="xref" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks">ChapterÂ 23, <i>Tips and tricks</i></a> is recommended reading for programmers thinking of writing new applications which use <code class="command">libvirt</code>.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Creating_custom_libvirt_scripts-Using_XML_configuration_files_with_virsh">24.1.Â Using XML configuration files with virsh</h2></div></div></div><div class="para">
			<code class="command">virsh</code> can handle XML configuration files. You may want to use this to your advantage for scripting large deployments with special options. You can add devices defined in an XML file to a running para-virtualized guest. For example, to add a ISO file as <code class="filename">hdc</code> to a running guest create an XML file: 
<pre class="screen"># cat satelliteiso.xml
<disk type="file" device="disk">
	<driver name="file"/>
	<source file="/var/lib/libvirt/images/rhn-satellite-5.0.1-11-redhat-linux-as-i386-4-embedded-oracle.iso"/>
	<target dev="hdc"/>
	<readonly/>
</disk>
</pre>
			 Run <code class="command">virsh attach-device</code> to attach the ISO as <code class="filename">hdc</code> to a guest called "satellite" : 
<pre class="screen"># virsh attach-device satellite satelliteiso.xml
</pre>
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Duplicating_an_existing_guest_and_its_configuration_file.html"><strong>Prev</strong>23.18.Â Duplicating an existing guest and its conf...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Troubleshooting.html"><strong>Next</strong>PartÂ VI.Â Troubleshooting</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 3.Â Guest operating system installation procedures</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Installation.html" title="PartÂ I.Â Installation"/><link rel="prev" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html" title="2.3.Â Installing guests with PXE"/><link rel="next" href="sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest.html" title="3.2.Â Installing Red Hat Enterprise Linux as a fully virtualized guest"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" al
 t="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Guest_operating_system_installation_procedures">ChapterÂ 3.Â Guest operating system installation procedures</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html#sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_5_as_a_para_virtualized_g
 uest">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.html">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.html">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.html">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.html">3.5. Installing Windows Server 2008 as a fully virtualized guest</a></span></dt></dl></div><div class="para">
		This chapter covers how to install various guest operating systems in a virtualized environment on Fedora. To understand the basic processes, refer to <a class="xref" href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html" title="ChapterÂ 2.Â Virtualized guest installation overview">ChapterÂ 2, <i>Virtualized guest installation overview</i></a>.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></div></div><div class="para">
		This section describes how to install Red Hat Enterprise Linux 5 as a para-virtualized guest. Para-virtualization is a faster than full virtualization and supports all of the advantages of full virtualization. Para-virtualization requires a special, supported kernel, the <code class="command">kernel-xen</code> kernel.
	</div><div class="important"><h2>Important note on para-virtualization</h2><div class="para">
			Para-virtualization only works with the Xen hypervisor. Para-virtualization does not work with the KVM hypervisor.
		</div></div><div class="para">
		Ensure you have root access before starting the installation.
	</div><div class="para">
		This method installs Red Hat Enterprise Linux from a remote server. The installation instructions presented in this section are similar to installing from the minimal installation live CD-ROM.
	</div><div class="para">
		Create para-virtualized Red Hat Enterprise Linux 5 guests using virt-manager or virt-install. For instructions on <code class="command">virt-manager</code>, refer to the procedure in <a class="xref" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager.html" title="2.2.Â Creating guests with virt-manager">SectionÂ 2.2, â€œCreating guests with virt-managerâ€</a>.
	</div><div class="para">
		Create a para-virtualized guest with the command line based <code class="command">virt-install</code> tool. The <code class="command">--vnc</code> option shows the graphical installation. The name of the guest in the example is <em class="replaceable"><code>rhel5PV</code></em>, the disk image file is <em class="replaceable"><code>rhel5PV.dsk</code></em> and a local mirror of the Red Hat Enterprise Linux 5 installation tree is <em class="replaceable"><code>ftp://10.1.1.1/trees/CentOS5-B2-Server-i386/</code></em>. Replace those values with values accurate for your system and network.
	</div><pre class="screen"># virt-install -n <em class="replaceable"><code>rhel5PV</code></em> -r 500 \
-f /var/lib/libvirt/images/<em class="replaceable"><code>rhel5PV.dsk</code></em> -s 3 --vnc -p \
-l <em class="replaceable"><code>ftp://10.1.1.1/trees/CentOS5-B2-Server-i386/</code></em>
</pre><div class="note"><h2>Automating installation</h2><div class="para">
			Red Hat Enterprise Linux can be installed without a graphical interface or manual input. Use Kickstart files to automate the installation process.
		</div></div><div class="para">
		Using either method opens this window, displaying the initial boot phases of your guest:
	</div><div class="mediaobject"><img src="images/guest_initial_boot.png"/></div><div class="para">
		After your guest has completed its initial boot, the standard installation process for Red Hat Enterprise Linux starts. For most systems the default answers are acceptable.
	</div><div class="procedure" id="proc-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_5_as_a_para_virtualized_guest-Para_virtualized_Red_Hat_Enterprise_Linux_guest_installation_procedure"><h6>ProcedureÂ 3.1.Â Para-virtualized Red Hat Enterprise Linux guest installation procedure</h6><ol class="1"><li><div class="para">
				Select the language and click <span class="guibutton"><strong>OK</strong></span>.
			</div><div class="mediaobject"><img src="images/install_language.png"/></div></li><li><div class="para">
				Select the keyboard layout and click <span class="guibutton"><strong>OK</strong></span>.
			</div><div class="mediaobject"><img src="images/select_keyboard.png"/></div></li><li><div class="para">
				Assign the guest's network address. Choose to use <code class="systemitem">DHCP</code> (as shown below) or a static IP address:
			</div><div class="mediaobject"><img src="images/config_tcp1.png"/></div></li><li><div class="para">
				If you select DHCP the installation process will now attempt to acquire an IP address:
			</div><div class="mediaobject"><img src="images/acquiring_ip.png"/></div></li><li><div class="para">
				If you chose a static IP address for your guest this prompt appears. Enter the details on the guest's networking configuration:
			</div><ol class="a"><li><div class="para">
						Enter a valid IP address. Ensure the IP address you enter can reach the server with the installation tree.
					</div></li><li><div class="para">
						Enter a valid Subnet mask, default gateway and name server address.
					</div></li></ol><div class="para">
				Select the language and click <span class="guibutton"><strong>OK</strong></span>.
			</div><div class="mediaobject"><img src="images/manual_tcp.png"/></div></li><li><div class="para">
				This is an example of a static IP address configuration:
			</div><div class="mediaobject"><img src="images/example_tcp.png"/></div></li><li><div class="para">
				The installation process now retrieves the files it needs from the server:
			</div><div class="mediaobject"><img src="images/retrieve_image.png"/></div></li></ol></div><div class="para">
		Once the initial steps are complete the graphical installation process starts.
	</div><div class="mediaobject"><img src="images/initial_graphic_install.png"/></div><div class="para">
		If you are installing a Beta or early release distribution confirm that you want to install the operating system. Click <span class="guibutton"><strong>Install Anyway</strong></span>, and then click <span class="guibutton"><strong>OK</strong></span>:
	</div><div class="mediaobject"><img src="images/confirm_beta.png"/></div><div class="procedure" id="proc-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_5_as_a_para_virtualized_guest-The_graphical_installation_process"><h6>ProcedureÂ 3.2.Â The graphical installation process</h6><ol class="1"><li><div class="para">
				Enter a valid registration code. If you have a valid RHN subscription key please enter in the <code class="computeroutput">Installation Number</code> field:
			</div><div class="mediaobject"><img src="images/install_number.png"/></div><div class="note"><h2>Note</h2><div class="para">
					If you skip the registration step the you can confirm your fedora Network account details after the installation with the <code class="command">rhn_register</code> command. The <code class="command">rhn_register</code> command requires root access.
				</div><pre class="screen"># rhn_register
</pre></div></li><li><div class="para">
				The installation prompts you to confirm erasure of all data on the storage you selected for the installation:
			</div><div class="mediaobject"><img src="images/erase_storage.png"/></div><div class="para">
				Click <span class="guibutton"><strong>Yes</strong></span> to continue.
			</div></li><li><div class="para">
				Review the storage configuration and partition layout. You can chose to select the advanced storage configuration if you want to use iSCSI for the guest's storage.
			</div><div class="mediaobject"><img src="images/review_storage.png"/></div><div class="para">
				Make your selections then click <span class="guibutton"><strong>Next</strong></span>.
			</div></li><li><div class="para">
				Confirm the selected storage for the installation.
			</div><div class="mediaobject"><img src="images/confirm_storage.png"/></div><div class="para">
				Click <span class="guibutton"><strong>Yes</strong></span> to continue.
			</div></li><li><div class="para">
				Configure networking and hostname settings. These settings are populated with the data entered earlier in the installation process. Change these settings if necessary.
			</div><div class="mediaobject"><img src="images/guest_network_settings.png"/></div><div class="para">
				Click <span class="guibutton"><strong>OK</strong></span> to continue.
			</div></li><li><div class="para">
				Select the appropriate time zone for your environment.
			</div><div class="mediaobject"><img src="images/time_zone.png"/></div></li><li><div class="para">
				Enter the root password for the guest.
			</div><div class="mediaobject"><img src="images/root_password.png"/></div><div class="para">
				Click <span class="guibutton"><strong>Next</strong></span> to continue.
			</div></li><li><div class="para">
				Select the software packages to install. Select the <span class="guibutton"><strong>Customize Now</strong></span> button. You must install the <span class="guilabel"><strong>kernel-xen</strong></span> package in the <span class="guilabel"><strong>System</strong></span> directory. The <span class="guilabel"><strong>kernel-xen</strong></span> package is required for para-virtualization.
			</div><div class="mediaobject"><img src="images/software_selection1.png"/></div><div class="para">
				Click <span class="guibutton"><strong>Next</strong></span>.
			</div></li><li><div class="para">
				Dependencies and space requirements are calculated.
			</div><div class="mediaobject"><img src="images/check_dependencies.png"/></div></li><li><div class="para">
				After the installation dependencies and space requirements have been verified click <span class="guibutton"><strong>Next</strong></span> to start the actual installation.
			</div><div class="mediaobject"><img src="images/begin_install.png"/></div></li><li><div class="para">
				All of the selected software packages are installed automatically.
			</div><div class="mediaobject"><img src="images/installing_packages.png"/></div></li><li><div class="para">
				After the installation has finished reboot your guest:
			</div><div class="mediaobject"><img src="images/reboot_guest.png"/></div></li><li><div class="para">
				The guest will not reboot, instead it will shutdown..
			</div><div class="mediaobject"><img src="images/guest_rebooting.png"/></div></li><li><div class="para">
				Boot the guest. The guest's name was chosen when you used the <code class="command">virt-install</code> in <a class="xref" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html#sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_5_as_a_para_virtualized_guest" title="3.1.Â Installing Red Hat Enterprise Linux 5 as a para-virtualized guest">SectionÂ 3.1, â€œInstalling Red Hat Enterprise Linux 5 as a para-virtualized guestâ€</a>. If you used the default example the name is <em class="replaceable"><code>rhel5PV</code></em>.
			</div><div class="para">
				Run:
			</div><pre class="screen">virsh reboot <em class="replaceable"><code>rhel5PV</code></em>
</pre><div class="para">
				Alternatively, open <code class="command">virt-manager</code>, select the name of your guest, click <span class="guibutton"><strong>Open</strong></span>, then click <span class="guibutton"><strong>Run</strong></span>.
			</div><div class="para">
				A <span class="application"><strong>VNC</strong></span> window displaying the guest's boot processes now opens.
			</div><div class="mediaobject"><img src="images/initial_guest_booting.png"/></div><div class="mediaobject"><img src="images/initial_guest_booting2.png"/></div></li><li><div class="para">
				Booting the guest starts the <span class="emphasis"><em>First Boot</em></span> configuration screen. This wizard prompts you for some basic configuration choices for your guest.
			</div><div class="mediaobject"><img src="images/first_boot_welcome.png"/></div></li><li><div class="para">
				Read and agree to the license agreement.
			</div><div class="mediaobject"><img src="images/license_agreement.png"/></div><div class="para">
				Click <span class="guibutton"><strong>Forward</strong></span> on the license agreement windows.
			</div></li><li><div class="para">
				Configure the firewall.
			</div><div class="mediaobject"><img src="images/firewall.png"/></div><div class="para">
				Click <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div><ol class="a"><li><div class="para">
						If you disable the firewall prompted to confirm your choice. Click <span class="guibutton"><strong>Yes</strong></span> to confirm and continue.
					</div><div class="mediaobject"><img src="images/disable_firewall.png"/></div></li></ol></li><li><div class="para">
				Configure SELinux. It is strongly recommended you run SELinux in <span class="guilabel"><strong>enforcing mode</strong></span>. You can choose to either run SELinux in permissive mode or completely disable it.
			</div><div class="mediaobject"><img src="images/selinux1.png"/></div><div class="para">
				Click <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div><ol class="a"><li><div class="para">
						If you choose to disable SELinux this warning displays. Click <span class="guibutton"><strong>Yes</strong></span> to disable SELinux.
					</div><div class="mediaobject"><img src="images/disable_selinux.png"/></div></li></ol></li><li><div class="para">
				Enable <code class="command">kdump</code> if necessary.
			</div><div class="mediaobject"><img src="images/enable_kdump.png"/></div><div class="para">
				Click <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li><div class="para">
				Confirm time and date are set correctly for your guest. If you install a para-virtualized guest time and date should sync with the hypervisor.
			</div><div class="mediaobject"><img src="images/date_time.png"/></div><div class="para">
				Click <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li><div class="para">
				Set up software updates. If you have a fedora Network subscription or want to trial one use the screen below to register your newly installed guest in RHN.
			</div><div class="mediaobject"><img src="images/rhn.png"/></div><div class="para">
				Click <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div><ol class="a"><li><div class="para">
						Confirm your choices for RHN.
					</div><div class="mediaobject"><img src="images/confirm_rhn.png"/></div></li><li><div class="para">
						Once setup has finished you may see one more screen if you opted out of RHN at this time. You will not receive software updates.
					</div><div class="mediaobject"><img src="images/no_rhn.png"/></div><div class="para">
						Click the <span class="guibutton"><strong>Forward</strong></span> button.
					</div></li></ol></li><li><div class="para">
				Create a non root user account. It is advised to create a non root user for normal usage and enhanced security. Enter the Username, Name and password.
			</div><div class="mediaobject"><img src="images/create_user.png"/></div><div class="para">
				Click the <span class="guibutton"><strong>Forward</strong></span> button.
			</div></li><li><div class="para">
				If a sound device is detected and you require sound, calibrate it. Complete the process and click <span class="guibutton"><strong>Forward</strong></span>.
			</div><div class="mediaobject"><img src="images/sound_card.png"/></div></li><li><div class="para">
				You can to install any additional software packages from CD you could do so on this screen. It it often more efficient to not install any additional software at this point but add it later using yum. Click <span class="guibutton"><strong>Finish</strong></span>.
			</div><div class="mediaobject"><img src="images/additional_software.png"/></div></li><li><div class="para">
				The guest now configure any settings you changed and continues the boot process.
			</div><div class="mediaobject"><img src="images/continue_boot_process.png"/></div></li><li><div class="para">
				The Red Hat Enterprise Linux 5 login screen displays. Log in using the username created in the previous steps.
			</div><div class="mediaobject"><img src="images/login_screen.png"/></div></li><li><div class="para">
				You have now successfully installed a para-virtualized Red Hat Enterprise Linux 5 guest.
			</div><div class="mediaobject"><img src="images/redhat_desktop.png"/></div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html"><strong>Prev</strong>2.3.Â Installing guests with PXE</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest.html"><strong>Next</strong>3.2.Â Installing Red Hat Enterprise Linux as a ful...</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Installing_the_virtualization_packages.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 1.Â Installing the virtualization packages</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Installation.html" title="PartÂ I.Â Installation"/><link rel="prev" href="part-Virtualization_Guide-Installation.html" title="PartÂ I.Â Installation"/><link rel="next" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system.html" title="1.2.Â Installing Xen packages on an existing Fedora system"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.
 fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system.html"><strong>Next</strong></a></li></ul><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="chap-Virtualization_Guide-Installing_the_virtualization_packages.html#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.html">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.html">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.html">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.html" 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><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Installation.html"><strong>Prev</strong>PartÂ I.Â Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system.html"><strong>Next</strong>1.2.Â Installing Xen packages on an existing Fedor...</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 11.Â KVM Para-virtualized Drivers</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Configuration.html" title="PartÂ II.Â Configuration"/><link rel="prev" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtual_Storage_Devices.html" title="10.4.2.Â Virtual Storage Devices"/><link rel="next" href="part-Virtualization_Guide-Administration.html" title="PartÂ III.Â Administration"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content
 /images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtual_Storage_Devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Administration.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers">ChapterÂ 11.Â KVM Para-virtualized Drivers</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html#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></div><div class="para">
		Para-virtualized drivers are available for virtualized Windows guests running on KVM hosts. These para-virtualized drivers are included in the virtio package. The virtio package supports block (storage) devices and network interface controllers.
	</div><div class="para">
		Para-virtualized drivers enhance the performance of fully virtualized guests. With the para-virtualized drivers guest I/O latency decreases and throughput increases to near bare-metal levels. It is recommended to use the para-virtualized drivers for fully virtualized guests running I/O heavy tasks and applications.
	</div><div class="para">
		The KVM para-virtualized drivers are automatically loaded and installed on newer versions of Fedora. Those Fedora versions detect and install the drivers so additional installation steps are not required.
	</div><div class="para">
		As with the KVM module, the virtio drivers are only available on hosts running newer versions of Fedora.
	</div><div class="important"><h2>Note</h2><div class="para">
			There are only 28 PCI slots available for additional devices per guest. Every para-virtualized network or block device uses one slot. Each guest can use up to 28 additional devices made up of any combination of para-virtualized network, para-virtualized disk devices, or other PCI devices using VTd.
		</div></div><div class="para">
		The following Microsoft Windows versions have supported KVM para-virtualized drivers:
	</div><div class="itemizedlist"><ul><li><div class="para">
				Windows XP,
			</div></li><li><div class="para">
				Windows Server 2003,
			</div></li><li><div class="para">
				Windows Vista, and
			</div></li><li><div class="para">
				Windows Server 2008.
			</div></li></ul></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-KVM_Para_virtualized_Drivers-Installing_the_KVM_Windows_para_virtualized_drivers">11.1.Â Installing the KVM Windows para-virtualized drivers</h2></div></div></div><div class="para">
			This section covers the installation process for the KVM Windows para-virtualized drivers. The KVM para-virtualized drivers can be loaded during the Windows installation or installed after the guest is installed.
		</div><div class="para">
			You can install the para-virtualized drivers on your guest by one of the following methods: 
			<div class="itemizedlist"><ul><li><div class="para">
						hosting the installation files on a network accessible to the guest,
					</div></li><li><div class="para">
						using a virtualized CD-ROM device of the driver installation disk .iso file, or
					</div></li><li><div class="para">
						using a virtualized floppy device to install the drivers during boot time (for Windows guests).
					</div></li></ul></div>
			 This guide describes installation from the para-virtualized installer disk as a virtualized CD-ROM device.
		</div><div class="procedure"><ol class="1"><li id="step-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Download_the_drivers"><p class="title"><b>Download the drivers</b></p><div class="para">
					The drivers are  available  from Microsoft (<a href="http://www.windowsservercatalog.com/results.aspx?text=Red+Hat&bCatID=1282&avc=10&ava=0&OR=5&=Go&chtext=&cstext=&csttext=&chbtext=">windowsservercatalog.com</a>). 
				</div><div class="para">
					The <span class="package">virtio-win</span> package installs a CD-ROM image, <code class="filename">virtio-win.iso</code>, in the <code class="filename">/usr/share/virtio-win/</code> directory.
				</div></li><li id="step-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Install_the_para_virtualized_drivers"><p class="title"><b>Install the para-virtualized drivers</b></p><div class="para">
					It is recommended to install the drivers on the guest before attaching or modifying a device to use the para-virtualized drivers.
				</div><div class="para">
					For block devices storing root file systems or other block devices required for booting the guest, the drivers must be installed before the device is modified. If the drivers are not installed on the guest and the driver is set to the virtio driver the guest will not boot.
				</div></li></ol></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Mounting_the_image_with_virt_manager">Mounting the image with virt-manager</h5>
				Follow <a class="xref" href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html#proc-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Using_virt_manager_to_mount_a_CD_ROM_image_for_a_Windows_guest" title="ProcedureÂ 11.1.Â Using virt-manager to mount a CD-ROM image for a Windows guest">ProcedureÂ 11.1, â€œUsing virt-manager to mount a CD-ROM image for a Windows guestâ€</a> to add a CD-ROM image with <code class="command">virt-manager</code>.
			</div><div class="procedure" id="proc-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Using_virt_manager_to_mount_a_CD_ROM_image_for_a_Windows_guest"><h6>ProcedureÂ 11.1.Â Using <code class="command">virt-manager</code> to mount a CD-ROM image for a Windows guest</h6><ol class="1"><li><div class="para">
					Open <code class="command">virt-manager</code>, select your virtualized guest from the list of virtual machines and press the <span class="guibutton"><strong>Details</strong></span> button.
				</div></li><li><div class="para">
					Click the <span class="guibutton"><strong>Add</strong></span> button in the <span class="guilabel"><strong>Details</strong></span> panel.
				</div></li><li><div class="para">
					This opens a wizard for adding the new device. Select <span class="guilabel"><strong>Storage device</strong></span> from the drop down menu, then click <span class="guibutton"><strong>Forward</strong></span>. 
					<div class="mediaobject"><img src="images/select_type.png"/></div>
				</div></li><li><div class="para">
					Choose the <span class="guilabel"><strong>File (disk image)</strong></span> option and set the file location of the para-virtualized drivers .iso file. The location of the .iso files is <code class="filename">/usr/share/xenpv-win</code> if you used <code class="command">yum</code> to install the para-virtualized driver packages.
				</div><div class="para">
					If the drivers are stored physical CD, use the <span class="guilabel"><strong>Normal Disk Partition</strong></span> option.
				</div><div class="para">
					Set the <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>IDE cdrom</strong></span> and click <span class="guibutton"><strong>Forward</strong></span> to proceed. 
					<div class="mediaobject"><img src="images/type_assigned.png"/></div>
				</div></li><li><div class="para">
					The disk has been assigned and is available for the guest once the guest is started. Click <span class="guibutton"><strong>Finish</strong></span> to close the wizard or back if you made a mistake. 
					<div class="mediaobject"><img src="images/done.png"/></div>
				</div></li></ol></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk">Installing with a virtualized floppy disk</h5>
				This procedure covers installing the para-virtualized drivers during a Windows installation.
			</div><div class="procedure"><ul><li><div class="para">
					Upon installing the Windows VM for the first time using the run-once menu attach <code class="filename">viostor.vfd</code> as a floppy
				</div><ol class="a"><li id="step-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Windows_Server_2003"><p class="title"><b>Windows Server 2003</b></p><div class="para">
							When windows prompts to press F6 for third party drivers, do so and follow the onscreen instructions.
						</div></li><li id="step-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Windows_Server_2008"><p class="title"><b>Windows Server 2008</b></p><div class="para">
							When the installer prompts you for the driver, click on "Load Driver", point the installer to drive A: and pick the driver that suits your OS and bittage
						</div></li></ol></li></ul></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices">Using KVM para-virtualized drivers for existing devices</h5>
				Modify an existing hard disk device attached to the guest to use the <code class="command">virtio</code> driver instead of virtualized IDE driver. This example edits libvirt configuration files. Alternatively, <code class="command">virt-manager</code>, <code class="command">virsh attach-disk</code> or <code class="command">virsh attach-interface</code> can add a new device using the para-virtualized drivers <a class="xref" href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html#form-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices" title="Using KVM para-virtualized drivers for new devices">Using KVM para-virtualized drivers for new devices</a>.
			</div><div class="procedure"><ol class="1"><li><div class="para">
					Below is a file-based block device using the virtualized IDE driver. This is a typical entry for a virtualized guest not using the para-virtualized drivers.
				</div><pre class="screen"><disk type='file' device='disk'>
   <source file='/var/lib/libvirt/images/disk1.img'/>
   <target dev='hda' bus='ide'/>
</disk>
</pre></li><li><div class="para">
					Change the entry to use the para-virtualized device by modifying the <span class="bold bold"><strong>bus=</strong></span> entry to <code class="command">virtio</code>.
				</div><pre class="screen"><disk type='file' device='disk'>
   <source file='/var/lib/libvirt/images/disk1.img'/>
   <target dev='hda' <span class="bold bold"><strong>bus='virtio'/></strong></span>
</disk>
</pre></li></ol></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices">Using KVM para-virtualized drivers for new devices</h5>
				This procedure covers creating new devices using the KVM para-virtualized drivers with <code class="command">virt-manager</code>.
			</div><div class="para">
			Alternatively, the <code class="command">virsh attach-disk</code> or <code class="command">virsh attach-interface</code> commands can be used to attach devices using the para-virtualized drivers.
		</div><div class="important"><h2>Install the drivers first</h2><div class="para">
				Ensure the drivers have been installed on the Windows guest before proceeding to install new devices. If the drivers are unavailable the device will not be recognized and will not work.
			</div></div><div class="procedure"><ol class="1"><li><div class="para">
					Open the virtualized guest by double clicking on the name of the guest in <code class="command">virt-manager</code>.
				</div></li><li><div class="para">
					Open the <span class="guilabel"><strong>Hardware</strong></span> tab.
				</div></li><li><div class="para">
					Press the <span class="guilabel"><strong>Add Hardware</strong></span> button.
				</div></li><li><div class="para">
					In the Adding Virtual Hardware tab select <span class="guilabel"><strong>Storage</strong></span> or <span class="guilabel"><strong>Network</strong></span> for the type of device.
				</div><div class="orderedlist"><ol><li><div class="para">
							<span class="bold bold"><strong>New disk devices</strong></span>
						</div><div class="para">
							Select the storage device or file based image. Select <span class="guilabel"><strong>Virtio Disk</strong></span> as the <span class="guilabel"><strong>Device type</strong></span> and press <span class="guilabel"><strong>Forward</strong></span>.
						</div><div class="mediaobject"><img src="images/virtiodisk.png"/></div></li><li><div class="para">
							<span class="bold bold"><strong>New network devices</strong></span>
						</div><div class="para">
							Select <span class="guilabel"><strong>Virtual network</strong></span> or <span class="guilabel"><strong>Shared physical device</strong></span>. Select <span class="guilabel"><strong>virtio</strong></span> as the <span class="guilabel"><strong>Device type</strong></span> and press <span class="guilabel"><strong>Forward</strong></span>.
						</div><div class="mediaobject"><img src="images/virtionet.png"/></div></li></ol></div></li><li><div class="para">
					Press <span class="guilabel"><strong>Finish</strong></span> to save the device.
				</div><div class="mediaobject"><img src="images/virtionetdone.png"/></div></li><li><div class="para">
					Reboot the guest. The device may to be recognized by the Windows guest until it restarts.
				</div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtual_Storage_Devices.html"><strong>Prev</strong>10.4.2.Â Virtual Storage Devices</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Administration.html"><strong>Next</strong>PartÂ III.Â Administration</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-KVM_guest_timing_management.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 13.Â KVM guest timing management</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Administration.html" title="PartÂ III.Â Administration"/><link rel="prev" href="chap-Virtualization_Guide-Managing_guests_with_xend.html" title="ChapterÂ 12.Â Managing guests with xend"/><link rel="next" href="chap-Virtualization_Guide-Xen_live_migration.html" title="ChapterÂ 14.Â Xen live migration"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="
 Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Managing_guests_with_xend.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Xen_live_migration.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-KVM_guest_timing_management">ChapterÂ 13.Â KVM guest timing management</h2></div></div></div><div class="para">
		KVM uses the constant Time Stamp Counter (TSC) feature of many modern CPUs. Some CPUs do not have a constant Time Stamp Counter which will affect the way guests running on KVM keep time. Guest's running without accurate timekeeping can have serious affects on some networked applications as your guest will run faster or slower than the actual time.
	</div><div class="para">
		Guests can have several problems caused by inaccurate clocks and counters:
	</div><div class="itemizedlist"><ul><li><div class="para">
				Clocks can fall out of synchronization with the actual time which invalidates sessions and affects networks.
			</div></li><li><div class="para">
				Guests with slower clocks may have issues migrating.
			</div></li><li><div class="para">
				Guests may stop or crash.
			</div></li></ul></div><div class="para">
		These problems exist on other virtualization platforms and timing should always be tested.
	</div><div class="important"><h2>NTP</h2><div class="para">
			The Network Time Protocol (NTP) daemon should be running on the host and the guests. Enable the <code class="systemitem">ntpd</code> service:
		</div><pre class="screen"># service ntpd start
</pre><div class="para">
			Add the ntpd service to the default startup sequence:
		</div><pre class="screen"># chkconfig ntpd on
</pre><div class="para">
			Using the <code class="systemitem">ntpd</code> service should minimize the affects of clock skew in all cases.
		</div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-KVM_guest_timing_management-Determining_if_your_CPU_has_the_constant_Time_Stamp_Counter">Determining if your CPU has the constant Time Stamp Counter</h5>
			Your CPU has a constant Time Stamp Counter if the <code class="computeroutput">constant_tsc</code> flag is present. To determine if your CPU has the <code class="computeroutput">constant_tsc</code> flag run the following command:
		</div><pre class="screen">$ cat /proc/cpuinfo | grep constant_tsc
</pre><div class="para">
		If any output is given your CPU has the <code class="computeroutput">constant_tsc</code> bit. If no output is given follow the instructions below.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-KVM_guest_timing_management-Configuring_hosts_without_a_constant_Time_Stamp_Counter">Configuring hosts without a constant Time Stamp Counter</h5>
			Systems without constant time stamp counters require additional configuration. Power management features interfere with accurate time keeping and must be disabled for guests to accurately keep time with KVM.
		</div><div class="important"><h2>Note</h2><div class="para">
			These instructions are for AMD revision F cpus only.
		</div></div><div class="para">
		If the CPU lacks the <code class="computeroutput">constant_tsc</code> bit, disable all power management features (<a href="https://bugzilla.redhat.com/show_bug.cgi?id=513138">BZ#513138</a>). Each system has several timers it uses to keep time. The TSC is not stable on the host, which is sometimes caused by <code class="command">cpufreq</code> changes, deep C state, or migration to a host with a faster TSC. To stop deep C states, which cam stop the TSC, add "<code class="command">processor.max_cstate=1</code>" to the kernel boot options in grub on the host:
	</div><pre class="screen">term Fedora (vmlinuz-2.6.29.6-217.2.3.fc11)
        root (hd0,0)
	kernel /vmlinuz-vmlinuz-2.6.29.6-217.2.3.fc11 ro root=/dev/VolGroup00/LogVol00 rhgb quiet <span class="emphasis"><em>processor.max_cstate=1</em></span>
</pre><div class="para">
		Disable <code class="command">cpufreq</code> (only necessary on hosts without the <code class="command">constant_tsc</code>) by editing the <code class="filename">/etc/sysconfig/cpuspeed</code> configuration file and change the <code class="command">MIN_SPEED</code> and <code class="command">MAX_SPEED</code> variables to the highest frequency available. Valid limits can be found in the <code class="filename">/sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies</code> files.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-KVM_guest_timing_management-Using_the_para_virtualized_clock_with_Red_Hat_Enterprise_Linux_guests">Using the para-virtualized clock with Red Hat Enterprise Linux guests</h5>
			For certain Red Hat Enterprise Linux guests, additional kernel parameters are required. These parameters can be set by appending them to the end of the /kernel line in the /boot/grub/grub.conf file of the guest.
		</div><div class="para">
		The table below lists versions of Red Hat Enterprise Linux and the parameters required for guests on systems without a constant Time Stamp Counter.
	</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Red Hat Enterprise Linux</th><th>Additional guest kernel parameters</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">5.4 AMD64/Intel 64 with the para-virtualized clock</td><td class="seg">Additional parameters are not required</td></tr><tr class="seglistitem"><td class="seg">5.4 AMD64/Intel 64 without the para-virtualized clock</td><td class="seg">divider=10 notsc lpj=n</td></tr><tr class="seglistitem"><td class="seg">5.4 x86 with the para-virtualized clock </td><td class="seg">Additional parameters are not required</td></tr><tr class="seglistitem"><td class="seg">5.4 x86 without the para-virtualized clock</td><td class="seg">divider=10 clocksource=acpi_pm lpj=n</td></tr><tr class="seglistitem"><td class="seg"> 5.3 AMD64/Intel 64</td><td class="seg">divider=10 notsc</td></tr><tr class="seglistitem"><td class="seg">5.3 x86</td><td class="seg">divider=10 clocksource=acpi_pm</td></
 tr><tr class="seglistitem"><td class="seg">4.8 AMD64/Intel 64</td><td class="seg">notsc divider=10</td></tr><tr class="seglistitem"><td class="seg">4.8 x86</td><td class="seg">clock=pmtmr divider=10</td></tr><tr class="seglistitem"><td class="seg">3.9 AMD64/Intel 64 </td><td class="seg">Additional parameters are not required</td></tr><tr class="seglistitem"><td class="seg">3.9 x86</td><td class="seg">Additional parameters are not required</td></tr></tbody></table></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-KVM_guest_timing_management-Using_the_para_virtualized_clock_with_Windows_guests">Using the para-virtualized clock with Windows guests</h5>
			Enable the para-virtualized clock on Window guests by editing the boot parameters. Windows boot settings are stored in the boot.ini file. To enable the para-virtualized clock add the following line:
		</div><pre class="screen">/use pmtimer
</pre><div class="para">
		For more information on Windows boot settings and the pmtimer option, refer to <a href="http://support.microsoft.com/kb/833721">Available switch options for the Windows XP and the Windows Server 2003 Boot.ini files</a>.
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Managing_guests_with_xend.html"><strong>Prev</strong>ChapterÂ 12.Â Managing guests with xend</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Xen_live_migration.html"><strong>Next</strong>ChapterÂ 14.Â Xen live migration</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-KVM_live_migration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 15.Â KVM live migration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Administration.html" title="PartÂ III.Â Administration"/><link rel="prev" href="sect-Virtualization_Guide-Xen_live_migration-Configuring_guest_live_migration.html" title="14.2.Â Configuring guest live migration"/><link rel="next" href="sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration.html" title="15.2.Â Share storage example: NFS for a simple migration"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" h
 ref="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Xen_live_migration-Configuring_guest_live_migration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-KVM_live_migration">ChapterÂ 15.Â KVM live migration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-KVM_live_migration.html#sect-Virtualization_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_examp
 le_NFS_for_a_simple_migration.html">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.html">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.html">15.4. Migrating with virt-manager</a></span></dt></dl></div><div class="para">
		This chapter covers migrating guests running on a KVM hypervisor to another KVM host.
	</div><div class="para">
		Migration is name for the process of moving a virtualized guest from one host to another. 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">
		Migrations can be performed live or offline. To migrate guests the storage must be shared. Migration works by sending the guests memory to the destination host. The shared storage stores the guest's default file system. The file system image is not sent over the network from the source host to the destination host.
	</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 an average of ten or so 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 monitored for changes and sent to the destination while the image is sent. The memory is updated with the changed pages. The process continues until the amount of pause time allowed for the guest equals the predicted time for the final few pages to be transfer. KVM estimates that and attempts to transfer the maximum amount of pages from the source to the destination until we predict than the amount of remaining pages can be transferred in configured time while the VM is paused. The registers are loaded on the new host and the guest is then resumed on the destination host. If the guest is 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. If the network is in heavy use or a low bandwidth the migration will take much longer.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-KVM_live_migration-Live_migration_requirements">15.1.Â Live migration requirements</h2></div></div></div><div class="para">
			Migrating guests requires the following:
		</div><div class="itemizedlist" id="item-Virtualization_Guide-Live_migration_requirements-Migration_requirements"><h6>Migration requirements</h6><ul><li><div class="para">
					A virtualized guest installed on shared networked storage using one of the following protocols:
				</div><div class="itemizedlist"><ul><li><div class="para">
							Fibre Channel
						</div></li><li><div class="para">
							iSCSI
						</div></li><li><div class="para">
							NFS
						</div></li><li><div class="para">
							GFS2
						</div></li></ul></div></li><li><div class="para">
					Two or more Fedora systems of the same version with the same updates.
				</div></li><li><div class="para">
					Both system must have the appropriate ports open.
				</div></li><li><div class="para">
					Both systems must have identical network configurations. All bridging and network configurations must be exactly the same on both hosts.
				</div></li><li><div class="para">
					Shared storage must mount at the same location on source and destination systems. The mounted directory name must be identical.
				</div></li></ul></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Live_migration_requirements-Configuring_network_storage">Configuring network storage</h5>
				Configure shared storage and install a guest on the shared storage. For shared storage instructions, refer to <a class="xref" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html" title="ChapterÂ 5.Â Shared storage and virtualization">ChapterÂ 5, <i>Shared storage and virtualization</i></a>.
			</div><div class="para">
			Alternatively, use the NFS example in <a class="xref" href="sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration.html" title="15.2.Â Share storage example: NFS for a simple migration">SectionÂ 15.2, â€œShare storage example: NFS for a simple migrationâ€</a>.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Xen_live_migration-Configuring_guest_live_migration.html"><strong>Prev</strong>14.2.Â Configuring guest live migration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration.html"><strong>Next</strong>15.2.Â Share storage example: NFS for a simple mig...</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html" title="PartÂ IV.Â Virtualization Reference Guide"/><link rel="prev" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html" title="ChapterÂ 18.Â Managing guests with virsh"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html" title="19.2.Â The Virtual Machine Manager main window"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Comm
 on_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager">ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html#sect-V
 irtualization_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.html">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_.html">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_.html">19.4. Virtual Machine graphical console </a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manage
 r.html">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_.html">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.html">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.html">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.html">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-Displaying_a_gues
 ts_status_.html">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_.html">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.html">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_.html">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.html">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_manage
 r-Creating_a_virtual_network.html">19.15. Creating a virtual network</a></span></dt></dl></div><div class="para">
		This section describes the Virtual Machine Manager (<code class="command">virt-manager</code>) windows, dialog boxes, and various GUI controls.
	</div><div class="para">
		<code class="command">virt-manager</code> provides a graphical view of hypervisors and guest on your system and on remote machines. You can use <code class="command">virt-manager</code> to define both para-virtualized and fully virtualized guests. <code class="command">virt-manager</code> can perform virtualization management tasks, including:
	</div><div class="itemizedlist"><ul><li><div class="para">
				assigning memory,
			</div></li><li><div class="para">
				assigning virtual CPUs,
			</div></li><li><div class="para">
				monitoring operational performance,
			</div></li><li><div class="para">
				saving and restoring, pausing and resuming, and shutting down and starting virtualized guests,
			</div></li><li><div class="para">
				links to the textual and graphical consoles, and
			</div></li><li><div class="para">
				live and offline migrations.
			</div></li></ul></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window">19.1.Â The open connection window</h2></div></div></div><div class="para">
			This window appears first and prompts the user to choose a hypervisor session. Non-privileged users can initiate a read-only session. Root users can start a session with full blown read-write status. For normal use, select the <span class="guilabel"><strong>Local Xen host</strong></span> option or QEMU (for KVM).
		</div><div class="figure" id="figu-Virtualization_Guide-The_open_connection_window-Virtual_Machine_Manager_connection_window"><div class="figure-contents"><div class="mediaobject"><img src="images/step1-1.png" alt="Virtual Machine Manager connection window"/></div></div><h6>FigureÂ 19.1.Â Virtual Machine Manager connection window</h6></div><br class="figure-break"/></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html"><strong>Prev</strong>ChapterÂ 18.Â Managing guests with virsh</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html"><strong>Next</strong>19.2.Â The Virtual Machine Manager main window</a></li></ul></body></h
 tml>

--- NEW FILE chap-Virtualization_Guide-Managing_guests_with_virsh.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 18.Â Managing guests with virsh</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html" title="PartÂ IV.Â Virtualization Reference Guide"/><link rel="prev" href="chap-Virtualization_Guide-Virtualization_tools.html" title="ChapterÂ 17.Â Virtualization tools"/><link rel="next" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a>
 <a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Virtualization_tools.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Managing_guests_with_virsh">ChapterÂ 18.Â Managing guests with virsh</h2></div></div></div><div class="para">
		<code class="command">virsh</code> is a command line interface tool for managing guests and the hypervisor.
	</div><div class="para">
		The <code class="command">virsh</code> tool is built on the <code class="command">libvirt</code> management API and operates as an alternative to the <code class="command">xm</code> command and the graphical guest Manager (<code class="command">virt-manager</code>). <code class="command">virsh</code> can be used in read-only mode by unprivileged users. You can use <code class="command">virsh</code> to execute scripts for the guest machines.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-virsh_command_quick_reference">virsh command quick reference</h5>
			The following tables provide a quick reference for all virsh command line options.
		</div><div class="table" id="tabl-Virtualization_Guide-Managing_guests_with_virsh-Guest_management_commands"><div class="table-contents"><table summary="Guest management commands" border="1"><colgroup><col/><col/></colgroup><thead><tr><th>
						Command
					</th><th>
						Description
					</th></tr></thead><tbody><tr><td>
						<code class="command">help</code>
					</td><td>
						Prints basic help information.
					</td></tr><tr><td>
						<code class="command">list</code>
					</td><td>
						Lists all guests.
					</td></tr><tr><td>
						<code class="command">dumpxml</code>
					</td><td>
						Outputs the XML configuration file for the guest.
					</td></tr><tr><td>
						<code class="command">create</code>
					</td><td>
						Creates a guest from an XML configuration file and starts the new guest.
					</td></tr><tr><td>
						<code class="command">start</code>
					</td><td>
						Starts an inactive guest.
					</td></tr><tr><td>
						<code class="command">destroy</code>
					</td><td>
						Forces a guest to stop.
					</td></tr><tr><td>
						<code class="command">define</code>
					</td><td>
						Outputs an XML configuration file for a guest.
					</td></tr><tr><td>
						<code class="command">domid</code>
					</td><td>
						Displays the guest's ID.
					</td></tr><tr><td>
						<code class="command">domuuid</code>
					</td><td>
						Displays the guest's UUID.
					</td></tr><tr><td>
						<code class="command">dominfo</code>
					</td><td>
						Displays guest information.
					</td></tr><tr><td>
						<code class="command">domname</code>
					</td><td>
						Displays the guest's name.
					</td></tr><tr><td>
						<code class="command">domstate</code>
					</td><td>
						Displays the state of a guest.
					</td></tr><tr><td>
						<code class="command">quit</code>
					</td><td>
						Quits the interactive terminal.
					</td></tr><tr><td>
						<code class="command">reboot</code>
					</td><td>
						Reboots a guest.
					</td></tr><tr><td>
						<code class="command">restore</code>
					</td><td>
						Restores a previously saved guest stored in a file.
					</td></tr><tr><td>
						<code class="command">resume</code>
					</td><td>
						Resumes a paused guest.
					</td></tr><tr><td>
						<code class="command">save</code>
					</td><td>
						Save the present state of a guest to a file.
					</td></tr><tr><td>
						<code class="command">shutdown</code>
					</td><td>
						Gracefully shuts down a guest.
					</td></tr><tr><td>
						<code class="command">suspend</code>
					</td><td>
						Pauses a guest.
					</td></tr><tr><td>
						<code class="command">undefine</code>
					</td><td>
						Deletes all files associated with a guest.
					</td></tr><tr><td>
						<code class="command">migrate</code>
					</td><td>
						Migrates a guest to another host.
					</td></tr></tbody></table></div><h6>TableÂ 18.1.Â Guest management commands</h6></div><br class="table-break"/><div class="para">
		The following <code class="command">virsh</code> command options to manage guest and hypervisor resources:
	</div><div class="table" id="tabl-Virtualization_Guide-Managing_guests_with_virsh-Resource_management_options"><div class="table-contents"><table summary="Resource management options" border="1"><colgroup><col/><col/></colgroup><thead><tr><th>
						Command
					</th><th>
						Description
					</th></tr></thead><tbody><tr><td>
						<code class="command">setmem</code>
					</td><td>
						Sets the allocated memory for a guest.
					</td></tr><tr><td>
						<code class="command">setmaxmem</code>
					</td><td>
						Sets maximum memory limit for the hypervisor.
					</td></tr><tr><td>
						<code class="command">setvcpus</code>
					</td><td>
						Changes number of virtual CPUs assigned to a guest.
					</td></tr><tr><td>
						<code class="command">vcpuinfo</code>
					</td><td>
						Displays virtual CPU information about a guest.
					</td></tr><tr><td>
						<code class="command">vcpupin</code>
					</td><td>
						Controls the virtual CPU affinity of a guest.
					</td></tr><tr><td>
						<code class="command">domblkstat</code>
					</td><td>
						Displays block device statistics for a running guest.
					</td></tr><tr><td>
						<code class="command">domifstat</code>
					</td><td>
						Displays network interface statistics for a running guest.
					</td></tr><tr><td>
						<code class="command">attach-device</code>
					</td><td>
						Attach a device to a guest, using a device definition in an XML file.
					</td></tr><tr><td>
						<code class="command">attach-disk</code>
					</td><td>
						Attaches a new disk device to a guest.
					</td></tr><tr><td>
						<code class="command">attach-interface</code>
					</td><td>
						Attaches a new network interface to a guest.
					</td></tr><tr><td>
						<code class="command">detach-device</code>
					</td><td>
						Detach a device from a guest, takes the same kind of XML descriptions as command <code class="command">attach-device</code>.
					</td></tr><tr><td>
						<code class="command">detach-disk</code>
					</td><td>
						Detach a disk device from a guest.
					</td></tr><tr><td>
						<code class="command">detach-interface</code>
					</td><td>
						Detach a network interface from a guest.
					</td></tr></tbody></table></div><h6>TableÂ 18.2.Â Resource management options</h6></div><br class="table-break"/><div class="para">
		These are miscellaneous <code class="command">virsh</code> options:
	</div><div class="table" id="tabl-Virtualization_Guide-Managing_guests_with_virsh-Miscellaneous_options"><div class="table-contents"><table summary="Miscellaneous options" border="1"><colgroup><col/><col/></colgroup><thead><tr><th>
						Command
					</th><th>
						Description
					</th></tr></thead><tbody><tr><td>
						<code class="command">version</code>
					</td><td>
						Displays the version of <code class="command">virsh</code>
					</td></tr><tr><td>
						<code class="command">nodeinfo</code>
					</td><td>
						Outputs information about the hypervisor
					</td></tr></tbody></table></div><h6>TableÂ 18.3.Â Miscellaneous options</h6></div><br class="table-break"/><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Connecting_to_the_hypervisor">Connecting to the hypervisor</h5>
			Connect to a hypervisor session with <code class="command">virsh</code>:
		</div><pre class="screen"># virsh connect <em class="parameter"><code>{hostname OR URL}</code></em>
</pre><div class="para">
		Where <code class="command"><name></code> is the machine name of the hypervisor. To initiate a read-only connection, append the above command with <code class="command">-readonly</code>.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file">Creating a virtual machine XML dump (configuration file)</h5>
			Output a guest's XML configuration file with <code class="command">virsh</code>:
		</div><pre class="screen"># virsh dumpxml <em class="parameter"><code>{domain-id, domain-name or domain-uuid}</code></em>
</pre><div class="para">
		This command outputs the guest's XML configuration file to standard out (<code class="command">stdout</code>). You can save the data by piping the output to a file. An example of piping the output to a file called <em class="replaceable"><code>guest.xml</code></em>: 
<pre class="screen"># virsh dumpxml <em class="replaceable"><code>GuestID</code></em> > <em class="replaceable"><code>guest.xml</code></em>
</pre>
		 This file <code class="filename">guest.xml</code> can recreate the guest (refer to <a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html#form-Virtualization_Guide-Managing_guests_with_virsh-Editing_a_guests_configuration_file" title="Editing a guest's configuration file">Editing a guest's configuration file</a>. You can edit this XML configuration file to configure additional devices or to deploy additional guests. Refer to <a class="xref" href="chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html#sect-Virtualization_Guide-Creating_custom_libvirt_scripts-Using_XML_configuration_files_with_virsh" title="24.1.Â Using XML configuration files with virsh">SectionÂ 24.1, â€œUsing XML configuration files with virshâ€</a> for more information on modifying files created with <code class="command">virsh dumpxml</code>.
	</div><div class="para">
		An example of <code class="command">virsh dumpxml</code> output:
	</div><pre class="screen"># virsh dumpxml r5b2-mySQL01
<domain type='xen' id='13'>
    <name>r5b2-mySQL01</name>
    <uuid>4a4c59a7ee3fc78196e4288f2862f011</uuid>
    <bootloader>/usr/bin/pygrub</bootloader>
    <os>
        <type>linux</type>
        <kernel>/var/lib/libvirt/vmlinuz.2dgnU_</kernel>
	<initrd>/var/lib/libvirt/initrd.UQafMw</initrd>
        <cmdline>ro root=/dev/VolGroup00/LogVol00 rhgb quiet</cmdline>
    </os>
    <memory>512000</memory>
    <vcpu>1</vcpu>
    <on_poweroff>destroy</on_poweroff>
    <on_reboot>restart</on_reboot>
    <on_crash>restart</on_crash>
    <devices>
        <interface type='bridge'>
            <source bridge='xenbr0'/>
            <mac address='00:16:3e:49:1d:11'/>
            <script path='vif-bridge'/>
        </interface>
        <graphics type='vnc' port='5900'/>
        <console tty='/dev/pts/4'/>
    </devices>
</domain>
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Creating_a_guest_from_a_configuration_file">Creating a guest from a configuration file</h5>
			Guests can be created from XML configuration files. You can copy existing XML from previously created guests or use the <code class="command">dumpxml</code> option (refer to <a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html#form-Virtualization_Guide-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file" title="Creating a virtual machine XML dump (configuration file)">Creating a virtual machine XML dump (configuration file)</a>). To create a guest with <code class="command">virsh</code> from an XML file:
		</div><pre class="screen"># virsh create <em class="replaceable"><code>configuration_file.xml</code></em>
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Editing_a_guests_configuration_file">Editing a guest's configuration file</h5>
			Instead of using the <code class="command">dumpxml</code> option (refer to <a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html#form-Virtualization_Guide-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file" title="Creating a virtual machine XML dump (configuration file)">Creating a virtual machine XML dump (configuration file)</a>) guests can be edited either while they run or while they are offline. The <code class="command">virsh edit</code> command provides this functionality. For example, to edit the guest named <em class="parameter"><code>softwaretesting</code></em>:
		</div><pre class="screen"># virsh edit <em class="parameter"><code>softwaretesting</code></em>
</pre><div class="para">
		This opens a text editor. The default text editor is the <code class="command">$EDITOR</code> shell parameter (set to <code class="command">vi</code> by default).
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Suspending_a_guest">Suspending a guest</h5>
			Suspend a guest with <code class="command">virsh</code>:
		</div><pre class="screen"># virsh suspend <em class="parameter"><code>{domain-id, domain-name or domain-uuid}</code></em>
</pre><div class="para">
		When a guest is in a suspended state, it consumes system RAM but not processor resources. Disk and network I/O does not occur while the guest is suspended. This operation is immediate and the guest can be restarted with the <code class="command">resume</code> (<a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html#form-Virtualization_Guide-Managing_guests_with_virsh-Resuming_a_guest" title="Resuming a guest">Resuming a guest</a>) option.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Resuming_a_guest">Resuming a guest</h5>
			Restore a suspended guest with <code class="command">virsh</code> using the <code class="command">resume</code> option:
		</div><pre class="screen"># virsh resume <em class="parameter"><code>{domain-id, domain-name or domain-uuid}</code></em>
</pre><div class="para">
		This operation is immediate and the guest parameters are preserved for <code class="command">suspend</code> and <code class="command">resume</code> operations.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Save_a_guest">Save a guest</h5>
			Save the current state of a guest to a file using the <code class="command">virsh</code> command:
		</div><pre class="screen"># virsh save <em class="parameter"><code>{domain-name, domain-id or domain-uuid} filename</code></em>
</pre><div class="para">
		This stops the guest you specify and saves the data to a file, which may take some time given the amount of memory in use by your guest. You can restore the state of the guest with the <code class="command">restore</code> (<a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html#form-Virtualization_Guide-Managing_guests_with_virsh-Restore_a_guest" title="Restore a guest">Restore a guest</a>) option. Save is similar to pause, instead of just pausing a guest the present state of the guest is saved.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Restore_a_guest">Restore a guest</h5>
			Restore a guest previously saved with the <code class="command">virsh save</code> command (<a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html#form-Virtualization_Guide-Managing_guests_with_virsh-Save_a_guest" title="Save a guest">Save a guest</a>) using <code class="command">virsh</code>:
		</div><pre class="screen"># virsh restore <em class="parameter"><code>filename</code></em>
</pre><div class="para">
		This restarts the saved guest, which may take some time. The guest's name and UUID are preserved but are allocated for a new id.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Shut_down_a_guest">Shut down a guest</h5>
			Shut down a guest using the <code class="command">virsh</code> command:
		</div><pre class="screen"># virsh shutdown <em class="parameter"><code>{domain-id, domain-name or domain-uuid}</code></em>
</pre><div class="para">
		You can control the behavior of the rebooting guest by modifying the <code class="command">on_shutdown</code> parameter in the guest's configuration file file.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Rebooting_a_guest">Rebooting a guest</h5>
			Reboot a guest using <code class="command">virsh</code> command:
		</div><pre class="screen">#virsh reboot <em class="parameter"><code>{domain-id, domain-name or domain-uuid}</code></em>
</pre><div class="para">
		You can control the behavior of the rebooting guest by modifying the <code class="command">on_reboot</code> parameter in the guest's configuration file file.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Forcing_a_guest_to_stop">Forcing a guest to stop</h5>
			Force a guest to stop with the <code class="command">virsh</code> command:
		</div><pre class="screen"># virsh destroy <em class="parameter"><code>{domain-id, domain-name or domain-uuid}</code></em>
</pre><div class="para">
		This command does an immediate ungraceful shutdown and stops the specified guest. Using <code class="command">virsh destroy</code> can corrupt guest file systems . Use the <code class="command">destroy</code> option only when the guest is unresponsive. For para-virtualized guests, use the <code class="command">shutdown</code> option(<a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html#form-Virtualization_Guide-Managing_guests_with_virsh-Shut_down_a_guest" title="Shut down a guest">Shut down a guest</a>) instead.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Getting_the_domain_ID_of_a_guest">Getting the domain ID of a guest</h5>
			To get the domain ID of a guest:
		</div><pre class="screen"># virsh domid <em class="parameter"><code>{domain-name or domain-uuid}</code></em>
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Getting_the_domain_name_of_a_guest">Getting the domain name of a guest</h5>
			To get the domain name of a guest:
		</div><pre class="screen"># virsh domname <em class="parameter"><code>{domain-id or domain-uuid}</code></em>
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Getting_the_UUID_of_a_guest">Getting the UUID of a guest</h5>
			To get the Universally Unique Identifier (UUID) for a guest:
		</div><pre class="screen"># virsh domuuid <em class="replaceable"><code>{domain-id or domain-name}</code></em>
</pre><div class="para">
		An example of <code class="command">virsh domuuid</code> output:
	</div><pre class="screen"># virsh domuuid r5b2-mySQL01
4a4c59a7-ee3f-c781-96e4-288f2862f011
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Displaying_guest_Information_">Displaying guest Information </h5>
			Using <code class="command">virsh</code> with the guest's domain ID, domain name or UUID you can display information on the specified guest:
		</div><pre class="screen"># virsh dominfo <em class="parameter"><code>{domain-id, domain-name or domain-uuid}</code></em>
</pre><div class="para">
		This is an example of <code class="command">virsh dominfo</code> output:
	</div><pre class="screen"># virsh dominfo r5b2-mySQL01
id:             13
name:           r5b2-mysql01
uuid:           4a4c59a7-ee3f-c781-96e4-288f2862f011
os type:      	linux
state:          blocked
cpu(s):         1
cpu time:     	11.0s
max memory:     512000 kb
used memory:    512000 kb
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Displaying_host_information">Displaying host information</h5>
			To display information about the host:
		</div><pre class="screen"># virsh nodeinfo
</pre><div class="para">
		An example of <code class="command">virsh nodeinfo</code> output:
	</div><pre class="screen"># virsh nodeinfo
CPU model                    x86_64
CPU (s)                      8
CPU frequency                2895 Mhz
CPU socket(s)                2      
Core(s) per socket           2
Threads per core:            2
Numa cell(s)                 1
Memory size:                 1046528 kb
</pre><div class="para">
		This displays the node information and the machines that support the virtualization process.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Displaying_the_guests">Displaying the guests</h5>
			To display the guest list and their current states with <code class="command">virsh</code>:
		</div><pre class="screen"># virsh list
</pre><div class="para">
		Other options available include:
	</div><div class="para">
		the <code class="command">--inactive</code> option to list inactive guests (that is, guests that have been defined but are not currently active), and
	</div><div class="para">
		the <code class="command">--all</code> option lists all guests. For example:
	</div><pre class="screen"># virsh list --all
 Id Name                 State
----------------------------------
  0 Domain-0             running
  1 Domain202            paused
  2 Domain010            inactive
  3 Domain9600           crashed
</pre><div class="para">
		The output from <code class="command">virsh list</code> is categorized as one of the six states (listed below).
	</div><div class="itemizedlist"><ul><li><div class="para">
				The <code class="computeroutput">running</code> state refers to guests which are currently active on a CPU.
			</div></li><li><div class="para">
				Guests listed as <code class="computeroutput">blocked</code> are blocked, and are not running or runnable. This is caused by a guest waiting on I/O (a traditional wait state) or guests in a sleep mode.
			</div></li><li><div class="para">
				The <code class="computeroutput">paused</code> state lists domains that are paused. This occurs if an administrator uses the <span class="guilabel"><strong>pause</strong></span> button in <code class="command">virt-manager</code>, <code class="command">xm pause</code> or <code class="command">virsh suspend</code>. When a guest is paused it consumes memory and other resources but it is ineligible for scheduling and CPU resources from the hypervisor.
			</div></li><li><div class="para">
				The <code class="computeroutput">shutdown</code> state is for guests in the process of shutting down. The guest is sent a shutdown signal and should be in the process of stopping its operations gracefully. This may not work with all guest operating systems; some operating systems do not respond to these signals.
			</div></li><li><div class="para">
				Domains in the <code class="computeroutput">dying</code> state are in is in process of dying, which is a state where the domain has not completely shut-down or crashed.
			</div></li><li><div class="para">
				<code class="computeroutput">crashed</code> guests have failed while running and are no longer running. This state can only occur if the guest has been configured not to restart on crash. 
			</div></li></ul></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Displaying_virtual_CPU_information">Displaying virtual CPU information</h5>
			To display virtual CPU information from a guest with <code class="command">virsh</code>:
		</div><pre class="screen"># virsh vcpuinfo <em class="replaceable"><code>{domain-id, domain-name or domain-uuid}</code></em>
</pre><div class="para">
		An example of <code class="command">virsh vcpuinfo</code> output:
	</div><pre class="screen"># virsh vcpuinfo r5b2-mySQL01
VCPU:           0
CPU:            0
State:          blocked
CPU time:       0.0s
CPU Affinity:   yy
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Configuring_virtual_CPU_affinity">Configuring virtual CPU affinity</h5>
			To configure the affinity of virtual CPUs with physical CPUs:
		</div><pre class="screen"># virsh vcpupin <em class="replaceable"><code>{domain-id, domain-name or domain-uuid} vcpu, cpulist</code></em>
</pre><div class="para">
		Where <code class="command">vcpu</code> is the virtual VCPU number and <code class="command">cpulist</code> lists the physical number of CPUs.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Configuring_virtual_CPU_count">Configuring virtual CPU count</h5>
			To modify the number of CPUs assigned to a guest with <code class="command">virsh</code>:
		</div><pre class="screen"># virsh setvcpus <em class="parameter"><code>{domain-name, domain-id or domain-uuid} count</code></em>
</pre><div class="para">
		The new <em class="parameter"><code>count</code></em> value cannot exceed the count above the amount specified when the guest was created.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Configuring_memory_allocation">Configuring memory allocation</h5>
			To modify a guest's memory allocation with <code class="command">virsh</code> :
		</div><pre class="screen"># virsh setmem {domain-id or domain-name} count
</pre><div class="para">
		You must specify the <span class="emphasis"><em>count</em></span> in kilobytes. The new count value cannot exceed the amount you specified when you created the guest. Values lower than 64 MB are unlikely to work with most guest operating systems. A higher maximum memory value will not affect the an active guest unless the new value is lower which will shrink the available memory usage.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Displaying_guest_block_device_information">Displaying guest block device information</h5>
			Use <code class="command">virsh domblkstat</code> to display block device statistics for a running guest.
		</div><pre class="screen"># virsh domblkstat <em class="replaceable"><code>GuestName block-device</code></em>
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Displaying_guest_network_device_information">Displaying guest network device information</h5>
			Use <code class="command">virsh domifstat</code> to display network interface statistics for a running guest.
		</div><pre class="screen"># virsh domifstat <em class="replaceable"><code>GuestName interface-device </code></em>
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Migrating_guests_with_virsh">Migrating guests with virsh</h5>
			A guest can be migrated to another host with <code class="command">virsh</code>. Migrate domain to another host. Add --live for live migration. The <code class="command">migrate</code> command accepts parameters in the following format:
		</div><pre class="screen"># virsh migrate --live <em class="parameter"><code>GuestName DestinationURL</code></em>
</pre><div class="para">
		The <em class="parameter"><code>--live</code></em> parameter is optional. Add the <em class="parameter"><code>--live</code></em> parameter for live migrations.
	</div><div class="para">
		The <em class="parameter"><code>GuestName</code></em> parameter represents the name of the guest which you want to migrate.
	</div><div class="para">
		The <em class="parameter"><code>DestinationURL</code></em> parameter is the URL or hostname of the destination system. The destination system must run the same version of Fedora, be using the same hypervisor and have <code class="command">libvirt</code> running.
	</div><div class="para">
		Once the command is entered you will be prompted for the root password of the destination system.
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Managing_guests_with_virsh-Managing_virtual_networks">Managing virtual networks</h5>
			This section covers managing virtual networks with the <code class="command">virsh</code> command. To list virtual networks:
		</div><pre class="screen"># virsh net-list
</pre><div class="para">
		This command generates output similar to:
	</div><pre class="screen"># virsh net-list
Name                 State      Autostart
-----------------------------------------
default              active     yes      
vnet1	             active     yes      
vnet2	             active     yes
</pre><div class="para">
		To view network information for a specific virtual network:
	</div><pre class="screen"># virsh net-dumpxml <em class="replaceable"><code>NetworkName</code></em>
</pre><div class="para">
		This displays information about a specified virtual network in XML format:
	</div><pre class="screen"># virsh net-dumpxml vnet1
<network>
  <name>vnet1</name>
  <uuid>98361b46-1581-acb7-1643-85a412626e70</uuid>
  <forward dev='eth0'/>
  <bridge name='vnet0' stp='on' forwardDelay='0' />
  <ip address='192.168.100.1' netmask='255.255.255.0'>
    <dhcp>
      <range start='192.168.100.128' end='192.168.100.254' />
    </dhcp>
  </ip>
</network>
</pre><div class="para">
		Other <code class="command">virsh</code> commands used in managing virtual networks are:
	</div><div class="itemizedlist"><ul><li><div class="para">
				<code class="command">virsh net-autostart <em class="replaceable"><code>network-name</code></em></code> â€” Autostart a network specified as <em class="replaceable"><code>network-name</code></em>.
			</div></li><li><div class="para">
				<code class="command">virsh net-create <em class="replaceable"><code>XMLfile</code></em></code> â€” generates and starts a new network using an existing XML file.
			</div></li><li><div class="para">
				<code class="command">virsh net-define <em class="replaceable"><code>XMLfile</code></em></code> â€” generates a new network device from an existing XML file without starting it.
			</div></li><li><div class="para">
				<code class="command">virsh net-destroy <em class="replaceable"><code>network-name</code></em></code> â€” destroy a network specified as <em class="replaceable"><code>network-name</code></em>.
			</div></li><li><div class="para">
				<code class="command">virsh net-name <em class="replaceable"><code>networkUUID</code></em></code> â€” convert a specified <em class="replaceable"><code>networkUUID</code></em> to a network name.
			</div></li><li><div class="para">
				<code class="command">virsh net-uuid <em class="replaceable"><code>network-name</code></em></code> â€” convert a specified <em class="replaceable"><code>network-name</code></em> to a network UUID.
			</div></li><li><div class="para">
				<code class="command">virsh net-start <em class="replaceable"><code>nameOfInactiveNetwork</code></em></code> â€” starts an inactive network.
			</div></li><li><div class="para">
				<code class="command">virsh net-undefine <em class="replaceable"><code>nameOfInactiveNetwork</code></em></code> â€” removes the definition of an inactive network.
			</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Virtualization_tools.html"><strong>Prev</strong>ChapterÂ 17.Â Virtualization tools</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html"><strong>Next</strong>ChapterÂ 19.Â Managing guests with the Virtual Mach...</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Managing_guests_with_xend.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 12.Â Managing guests with xend</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Administration.html" title="PartÂ III.Â Administration"/><link rel="prev" href="part-Virtualization_Guide-Administration.html" title="PartÂ III.Â Administration"/><link rel="next" href="chap-Virtualization_Guide-KVM_guest_timing_management.html" title="ChapterÂ 13.Â KVM guest timing management"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Document
 ation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Administration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-KVM_guest_timing_management.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Managing_guests_with_xend">ChapterÂ 12.Â Managing guests with <code class="systemitem">xend</code></h2></div></div></div><div class="para">
		The <span class="application"><strong>xend</strong></span> node control daemon performs certain system management functions that relate to virtual machines. This daemon controls the virtualized resources, and <span class="application"><strong>xend</strong></span> must be running to interact with virtual machines. Before you start <span class="application"><strong>xend</strong></span>, you must specify the operating parameters by editing the <span class="application"><strong>xend</strong></span> configuration file <code class="command">/etc/xen/xend-config.sxp</code>. Here are the parameters you can enable or disable in the <code class="command">xend-config.sxp</code> configuration file:
	</div><div class="table" id="tabl-Virtualization_Guide-Managing_guests_with_xend-xend_configuration_parameters"><div class="table-contents"><table summary="xend configuration parameters" border="1"><colgroup><col/><col/></colgroup><thead><tr><th>
						Item
					</th><th>
						Description
					</th></tr></thead><tbody><tr><td>
						<div class="para">
							<span class="application"><strong>(console-limit)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the console server's memory buffer limit xend_unix_server and assigns values on a per domain basis.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(min-mem)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the minimum number of megabytes that is reserved for domain0 (if you enter 0, the value does not change).
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(dom0-cpus)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the number of CPUs in use by domain0 (at least 1 CPU is assigned by default).
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(enable-dump)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines that a crash occurs then enables a dump (the default is 0).
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(external-migration-tool)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the script or application that handles external device migration. Scripts must reside in <code class="command">etc/xen/scripts/external-device-migrate</code>.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(logfile)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the location of the log file (default is <code class="command">/var/log/xend.log</code>).
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(loglevel)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Filters out the log mode values: DEBUG, INFO, WARNING, ERROR, or CRITICAL (default is DEBUG).
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(network-script)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the script that enables the networking environment (scripts must reside in <code class="command">etc/xen/scripts </code> directory).
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(xend-http-server)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Enables the http stream packet management server (the default is no).
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(xend-unix-server)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Enables the unix domain socket server, which is a socket server is a communications endpoint that handles low level network connections and accepts or rejects incoming connections. The default value is set to yes.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(xend-relocation-server)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Enables the relocation server for cross-machine migrations (the default is no).
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(xend-unix-path)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the location where the <code class="command">xend-unix-server</code> command outputs data (default is <code class="command">var/lib/xend/xend-socket</code>)
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(xend-port)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the port that the http management server uses (the default is 8000).
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(xend-relocation-port)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the port that the relocation server uses (the default is 8002).
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(xend-relocation-address)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the host addresses allowed for migration. The default value is the value of <code class="computeroutput">xend-address</code>.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<span class="application"><strong>(xend-address)</strong></span>
						</div>
					</td><td>
						<div class="para">
							Determines the address that the domain socket server binds to. The default value allows all connections.
						</div>
					</td></tr></tbody></table></div><h6>TableÂ 12.1.Â <span class="application">xend</span> configuration parameters</h6></div><br class="table-break"/><div class="para">
		After setting these operating parameters, you should verify that xend is running and if not, initialize the daemon. At the command prompt, you can start the <span class="application"><strong>xend</strong></span> daemon by entering the following:
	</div><pre class="screen">service xend start
</pre><div class="para">
		You can use <span class="application"><strong>xend</strong></span> to stop the daemon:
	</div><pre class="screen">service xend stop
</pre><div class="para">
		This stops the daemon from running.
	</div><div class="para">
		You can use <span class="application"><strong>xend</strong></span> to restart the daemon:
	</div><pre class="screen">service xend restart
</pre><div class="para">
		The daemon starts once again.
	</div><div class="para">
		You check the status of the <span class="application"><strong>xend</strong></span> daemon.
	</div><pre class="screen">service xend status
</pre><div class="para">
		The output displays the daemon's status.
	</div><div class="note"><h2>Enabling xend at boot time</h2><div class="para">
			Use the <code class="command">chkconfig</code> command to add the <code class="systemitem">xend</code> to the <code class="filename">initscript</code>.
		</div><div class="para">
			<code class="command">chkconfig --level 345 xend</code>
		</div><div class="para">
			The the <code class="systemitem">xend</code> will now start at runlevels 3, 4 and 5.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Administration.html"><strong>Prev</strong>PartÂ III.Â Administration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-KVM_guest_timing_management.html"><strong>Next</strong>ChapterÂ 13.Â KVM guest timing management</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Network_Configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 8.Â Network Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Configuration.html" title="PartÂ II.Â Configuration"/><link rel="prev" href="sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html" title="7.2.Â SELinux considerations"/><link rel="next" href="sect-Virtualization_Guide-Network_Configuration-Bridged_networking_with_libvirt.html" title="8.2.Â Bridged networking with libvirt"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="
 Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Network_Configuration">ChapterÂ 8.Â Network Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Network_Configuration.html#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
 .html">8.2. Bridged networking with libvirt</a></span></dt></dl></div><div class="para">
		This page provides an introduction to the common networking configurations used by libvirt based applications. This information applies to all hypervisors, whether Xen, KVM or another. For additional information consult the libvirt network architecture docs.
	</div><div class="para">
		The two common setups are "virtual network" or "shared physical device". The former is identical across all distributions and available out-of-the-box. The latter needs distribution specific manual configuration.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">8.1.Â Network address translation (NAT) with libvirt</h2></div></div></div><div class="para">
			One of the most common methods for sharing network connections is to use Network address translation (NAT) forwarding (also know as virtual networks).
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Network_address_translation_NAT_with_libvirt-Host_configuration">Host configuration</h5>
				Every standard <code class="systemitem">libvirt</code> installation provides NAT based connectivity to virtual machines out of the box. This is the so called 'default virtual network'. Verify that it is available with the <code class="command">virsh net-list --all</code> command.
			</div><pre class="screen"># virsh net-list --all
Name                 State      Autostart 
-----------------------------------------
default              active     yes
</pre><div class="para">
			If it is missing, the example XML configuration file can be reloaded and activated:
		</div><pre class="screen"># virsh net-define /usr/share/libvirt/networks/default.xml
</pre><div class="para">
			The default network is defined from <code class="filename">/usr/share/libvirt/networks/default.xml</code>
		</div><div class="para">
			Mark the default network to automatically start:
		</div><pre class="screen"># virsh net-autostart default
Network default marked as autostarted
</pre><div class="para">
			Start the default network:
		</div><pre class="screen"># virsh net-start default
Network default started
</pre><div class="para">
			Once the <code class="systemitem">libvirt</code> default network is running, you will see an isolated bridge device. This device does <span class="emphasis"><em>not</em></span> have any physical interfaces added, since it uses NAT and IP forwarding to connect to outside world. Do not add new interfaces.
		</div><pre class="screen"># brctl show
bridge name     bridge id               STP enabled     interfaces
virbr0          8000.000000000000       yes
</pre><div class="para">
			<code class="command">libvirt</code> adds <code class="command">iptables</code> rules which allow traffic to and from guests attached to the <code class="systemitem">virbr0</code> device in the <code class="command">INPUT</code>, <code class="command">FORWARD</code>, <code class="command">OUTPUT</code> and <code class="command">POSTROUTING</code> chains. <code class="command">libvirt</code> then attempts to enable the <code class="command">ip_forward</code> parameter. Some other applications may disable <code class="command">ip_forward</code>, so the best option is to add the following to <code class="filename">/etc/sysctl.conf</code>.
		</div><pre class="screen"> net.ipv4.ip_forward = 1
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Network_address_translation_NAT_with_libvirt-Guest_configuration">Guest configuration</h5>
				Once the host configuration is complete, a guest can be connected to the virtual network based on its name. To connect a guest to the 'default' virtual network, the following XML can be used in the guest:
			</div><pre class="screen"><interface type='network'>
  <source network='default'/>
</interface>
</pre><div class="note"><h2>Note</h2><div class="para">
				Defining a MAC address is optional. A MAC address is automatically generated if omitted. Manually setting the MAC address is useful in certain situations.
			</div><pre class="screen"><interface type='network'>
  <source network='default'/>
  <mac address='00:16:3e:1a:b3:4a'/>
  </interface>
</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html"><strong>Prev</strong>7.2.Â SELinux considerations</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Next</strong>8.2.Â Bridged networking with libvirt</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 16.Â Remote management of virtualized guests</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Administration.html" title="PartÂ III.Â Administration"/><link rel="prev" href="sect-Virtualization_Guide-KVM_live_migration-Migrating_with_virt_manager.html" title="15.4.Â Migrating with virt-manager"/><link rel="next" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html" title="16.2.Â Remote management over TLS and SSL"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right
 " href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Remote_management_of_virtualized_guests">ChapterÂ 16.Â Remote management of virtualized guests</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_with_SSH">16.1. Remote management with SSH</a></span></dt><dt><span cl
 ass="section"><a href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html">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.html">16.3. Transport modes</a></span></dt></dl></div><div class="para">
		This section explains how to remotely manage your virtualized guests using <code class="command">ssh</code> or TLS and SSL.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_with_SSH">16.1.Â Remote management with SSH</h2></div></div></div><div class="para">
			The <span class="package">ssh</span> package provides an encrypted network protocol which can securely send management functions to remote virtualization servers. The method described uses the <code class="command">libvirt</code> management connection securely tunneled over an <span class="application"><strong>SSH</strong></span> connection to manage the remote machines. All the authentication is done using <span class="application"><strong>SSH</strong></span> public key cryptography and passwords or passphrases gathered by your local <span class="application"><strong>SSH</strong></span> agent. In addition the <span class="application"><strong>VNC</strong></span> console for each guest virtual machine is tunneled over <span class="application"><strong>SSH</strong></span>.
		</div><div class="para">
			<span class="application"><strong>SSH</strong></span> is usually configured by default so you probably already have SSH keys setup and no extra firewall rules needed to access the management service or <span class="application"><strong>VNC</strong></span> console.
		</div><div class="para">
			Be aware of the issues with using <span class="application"><strong>SSH</strong></span> for remotely managing your virtual machines, including: 
			<div class="itemizedlist"><ul><li><div class="para">
						you require root log in access to the remote machine for managing virtual machines,
					</div></li><li><div class="para">
						the initial connection setup process may be slow,
					</div></li><li><div class="para">
						there is no standard or trivial way to revoke a user's key on all hosts or guests, and
					</div></li><li><div class="para">
						ssh does not scale well with larger numbers of remote machines.
					</div></li></ul></div>
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Remote_management_with_SSH-Configuring_SSH_access_for_virt_manager">Configuring <span class="application"><strong>SSH</strong></span> access for <code class="command">virt-manager</code></h5>
				The following instructions assume you are starting from scratch and do not already have <span class="application"><strong>SSH</strong></span> keys set up.
			</div><div class="orderedlist"><ol><li><div class="para">
					You need a public key pair on the machine <code class="command">virt-manager</code> is used. If <code class="command">ssh</code> is already configured you can skip this command.
				</div><pre class="screen">$ ssh-keygen -t rsa
</pre></li><li><div class="para">
					To permit remote log in, <code class="command">virt-manager</code> needs a copy of the public key on each remote machine running <code class="command">libvirt</code>. Copy the file <code class="filename">$HOME/.ssh/id_rsa.pub</code> from the machine you want to use for remote management using the <code class="command">scp</code> command:
				</div><pre class="screen">$ scp $HOME/.ssh/id_rsa.pub root at somehost:/root/key-dan.pub
</pre></li><li><div class="para">
					After the file has copied, use <code class="command">ssh</code> to connect to the remote machines as root and add the file that you copied to the list of authorized keys. If the root user on the remote host does not already have an list of authorized keys, make sure the file permissions are correctly set
				</div><pre class="screen">$ ssh root@<em class="replaceable"><code>somehost</code></em>
# mkdir /root/.ssh
# chmod go-rwx /root/.ssh
# cat /root/key-dan.pub >> /root/.ssh/authorized_keys
# chmod go-rw /root/.ssh/authorized_keys
</pre></li></ol></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Remote_management_with_SSH-The_libvirt_daemon_libvirtd">The <code class="command">libvirt</code> daemon (<code class="systemitem">libvirtd</code>)</h5>
				The <code class="systemitem">libvirt</code> daemon provide an interface for managing virtual machines. You should use the <code class="systemitem">libvirtd</code> daemon installed and running on every remote host that you need to manage. Using the Fedora <code class="command">kernel-xen</code> package requires a speci TODO
			</div><pre class="screen">$ ssh root@<em class="replaceable"><code>somehost</code></em>
# chkconfig libvirtd on
# service libvirtd start
</pre><div class="para">
			After <code class="systemitem">libvirtd</code> and <span class="application"><strong>SSH</strong></span> are configured you should be able to remotely access and manage your virtual machines. You should also be able to access your guests with <code class="command">VNC</code> at this point.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Prev</strong>15.4.Â Migrating with virt-manager</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Next</strong>16.2.Â Remote management over TLS and SSL</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Security_for_virtualization.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 7.Â Security for virtualization</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Configuration.html" title="PartÂ II.Â Configuration"/><link rel="prev" href="chap-Virtualization_Guide-Server_best_practices.html" title="ChapterÂ 6.Â Server best practices"/><link rel="next" href="sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html" title="7.2.Â SELinux considerations"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_r
 ight.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Server_best_practices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Security_for_virtualization">ChapterÂ 7.Â Security for virtualization</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Security_for_virtualization.html#sect-Virtualization_Guide-Security_for_virtualization-SELinux_and_virtualization">7.1. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html">7.2. SELinux considerations</a></span></dt></dl></div><div class="para"
 >
		When deploying virtualization technologies on your corporate infrastructure, you must ensure that the host cannot be compromised. The host, in the Xen hypervisor, is a privileged domain that handles system management and manages all virtual machines. If the host is insecure, all other domains in the system are vulnerable. There are several ways to enhance security on systems using virtualization. You or your organization should create a <span class="emphasis"><em>Deployment Plan</em></span> containing the operating specifications and specifies which services are needed on your virtualized guests and host servers as well as what support is required for these services. Here are a few security issues to consider while developing a deployment plan:
	</div><div class="itemizedlist"><ul><li><div class="para">
				Run only necessary services on hosts. The fewer processes and services running on the host, the higher the level of security and performance.
			</div></li><li><div class="para">
				Enable <a class="firstterm" href="go01.html#glos-Virtualization_Guide-Security_Enhanced_Linux"><em class="firstterm">SELinux</em></a> on the hypervisor. Read <a class="xref" href="chap-Virtualization_Guide-Security_for_virtualization.html#sect-Virtualization_Guide-Security_for_virtualization-SELinux_and_virtualization" title="7.1.Â SELinux and virtualization">SectionÂ 7.1, â€œSELinux and virtualizationâ€</a> for more information on using SELinux and virtualization.
			</div></li><li><div class="para">
				Use a firewall to restrict traffic to dom0. You can setup a firewall with default-reject rules that will help secure attacks on dom0. It is also important to limit network facing services.
			</div></li><li><div class="para">
				Do not allow normal users to access dom0. If you do permit normal users dom0 access, you run the risk of rendering dom0 vulnerable. Remember, dom0 is privileged, and granting unprivileged accounts may compromise the level of security.
			</div></li></ul></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Security_for_virtualization-SELinux_and_virtualization">7.1.Â SELinux and virtualization</h2></div></div></div><div class="para">
			Security Enhanced Linux was developed by the <span class="orgname">NSA</span>
			 with assistance from the Linux community to provide stronger security for Linux. SELinux limits an attackers abilities and works to prevent many common security exploits such as buffer overflow attacks and privilege escalation. It is because of these benefits that Fedora recommends all Linux systems should run with SELinux enabled and in enforcing mode.
		</div><div class="para">
			SELinux prevents guest images from loading if SELinux is enabled and the images are not in the correct directory. SELinux requires that all guest images are stored in <code class="filename">/var/lib/libvirt/images</code>.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-SELinux_and_virtualization-Adding_LVM_based_storage_with_SELinux_in_enforcing_mode">Adding LVM based storage with SELinux in enforcing mode</h5>
				The following section is an example of adding a logical volume to a virtualized guest with SELinux enabled. These instructions also work for hard drive partitions.
			</div><div class="procedure" id="proc-Virtualization_Guide-SELinux_and_virtualization-Creating_and_mounting_a_logical_volume_on_a_virtualized_guest_with_SELinux_enabled"><h6>ProcedureÂ 7.1.Â Creating and mounting a logical volume on a virtualized guest with SELinux enabled</h6><ol class="1"><li><div class="para">
					Create a logical volume. This example creates a 5 gigabyte logical volume named <em class="parameter"><code>NewVolumeName</code></em> on the volume group named <em class="parameter"><code>volumegroup</code></em>.
				</div><pre class="screen"># lvcreate -n <em class="parameter"><code>NewVolumeName</code></em> -L <em class="parameter"><code>5G</code></em> <em class="parameter"><code>volumegroup</code></em>
</pre></li><li><div class="para">
					Format the <em class="parameter"><code>NewVolumeName</code></em> logical volume with a file system that supports extended attributes, such as ext3.
				</div><pre class="screen"># mke2fs -j <em class="parameter"><code>/dev/volumegroup/NewVolumeName</code></em>
</pre></li><li><div class="para">
					Create a new directory for mounting the new logical volume. This directory can be anywhere on your file system. It is advised not to put it in important system directories (<code class="filename">/etc</code>, <code class="filename">/var</code>, <code class="filename">/sys</code>) or in home directories (<code class="filename">/home</code> or <code class="filename">/root</code>). This example uses a directory called <code class="filename">/virtstorage</code>
				</div><pre class="screen"># mkdir <em class="parameter"><code>/virtstorage</code></em>
</pre></li><li><div class="para">
					Mount the logical volume.
				</div><pre class="screen"># mount <em class="parameter"><code>/dev/volumegroup/NewVolumeName</code></em> <em class="parameter"><code>/virtstorage</code></em>
</pre></li><li><div class="para">
					Set the correct SELinux type for the Xen folder.
				</div><pre class="screen">semanage fcontext -a -t xen_image_t "/virtualization(/.*)?"
</pre><div class="para">
					Alternatively, set the correct SELinux type for a KVM folder.
				</div><pre class="screen">semanage fcontext -a -t virt_image_t "/virtualization(/.*)?"
</pre><div class="para">
					If the targeted policy is used (targeted is the default policy) the command appends a line to the <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code> file which makes the change persistent. The appended line may resemble this:
				</div><pre class="screen">/virtstorage(/.*)?    system_u:object_r:xen_image_t:s0
</pre></li><li><div class="para">
					Run the command to change the type of the mount point (<code class="filename">/virtstorage</code>) and all files under it to <code class="command">xen_image_t</code> (<code class="command">restorecon</code> and <code class="command">setfiles</code> read the files in <code class="filename">/etc/selinux/targeted/contexts/files/</code>).
				</div><pre class="screen"># restorecon -R -v /virtualization
</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Server_best_practices.html"><strong>Prev</strong>ChapterÂ 6.Â Server best practices</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html"><strong>Next</strong>7.2.Â SELinux considerations</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Server_best_practices.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 6.Â Server best practices</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Configuration.html" title="PartÂ II.Â Configuration"/><link rel="prev" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests.html" title="5.3.Â Using GFS2 for storing guests"/><link rel="next" href="chap-Virtualization_Guide-Security_for_virtualization.html" title="ChapterÂ 7.Â Security for virtualization"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Com
 mon_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Security_for_virtualization.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Server_best_practices">ChapterÂ 6.Â Server best practices</h2></div></div></div><div class="para">
		The following tasks and tips can assist you with securing and ensuring reliability of your Fedora server host (dom0).
	</div><div class="itemizedlist"><ul><li><div class="para">
				Run SELinux in enforcing mode. You can do this by executing the command below. 
<pre class="screen"># setenforce 1
</pre>
			</div></li><li><div class="para">
				Remove or disable any unnecessary services such as <code class="command">AutoFS</code>, <code class="command">NFS</code>, <code class="command">FTP</code>, <code class="command">HTTP</code>, <code class="command">NIS</code>, <code class="command">telnetd</code>, <code class="command">sendmail</code> and so on.
			</div></li><li><div class="para">
				Only add the minimum number of user accounts needed for platform management on the server and remove unnecessary user accounts.
			</div></li><li><div class="para">
				Avoid running any unessential applications on your host. Running applications on the host may impact virtual machine performance and can affect server stability. Any application which may crash the server will also cause all virtual machines on the server to go down.
			</div></li><li><div class="para">
				Use a central location for virtual machine installations and images. Virtual machine images should be stored under <code class="filename">/var/lib/libvirt/images/</code>. If you are using a different directory for your virtual machine images make sure you add the directory to your SELinux policy and relabel it before starting the installation.
			</div></li><li><div class="para">
				Installation sources, trees, and images should be stored in a central location, usually the location of your <code class="systemitem">vsftpd</code> server.
			</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests.html"><strong>Prev</strong>5.3.Â Using GFS2 for storing guests</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Security_for_virtualization.html"><strong>Next</strong>ChapterÂ 7.Â Security for virtualization</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Shared_storage_and_virtualization.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 5.Â Shared storage and virtualization</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Configuration.html" title="PartÂ II.Â Configuration"/><link rel="prev" href="sect-Virtualization_Guide-Virtualized_block_devices-Add_a_virtualized_CD_ROM_or_DVD_device_to_a_guest.html" title="4.4.Â Add a virtualized CD-ROM or DVD device to a guest"/><link rel="next" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests.html" title="5.2.Â Using NFS for storing guests"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"
 /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Virtualized_block_devices-Add_a_virtualized_CD_ROM_or_DVD_device_to_a_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Shared_storage_and_virtualization">ChapterÂ 5.Â Shared storage and virtualization</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html#sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_iSCSI_for_storing_guests">5.1. Using iSCSI for storing guests</a></sp
 an></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests.html">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.html">5.3. Using GFS2 for storing guests</a></span></dt></dl></div><div class="para">
		This chapter covers using shared, networked storage with virtualization on Fedora.
	</div><div class="para">
		The following methods are supported for virtualization:
	</div><div class="itemizedlist"><ul><li><div class="para">
				Fibre Channel
			</div></li><li><div class="para">
				iSCSI
			</div></li><li><div class="para">
				NFS
			</div></li><li><div class="para">
				GFS2
			</div></li></ul></div><div class="para">
		Networked storage is essential for live and offline guest migrations. You cannot migrate guests without shared storage.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_iSCSI_for_storing_guests">5.1.Â Using iSCSI for storing guests</h2></div></div></div><div class="para">
			This section covers using iSCSI-based devices to store virtualized guests.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Virtualized_block_devices-Add_a_virtualized_CD_ROM_or_DVD_device_to_a_guest.html"><strong>Prev</strong>4.4.Â Add a virtualized CD-ROM or DVD device to a ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests.html"><strong>Next</strong>5.2.Â Using NFS for storing guests</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-The_xm_command_quick_reference.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 20.Â The xm command quick reference</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html" title="PartÂ IV.Â Virtualization Reference Guide"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Creating_a_virtual_network.html" title="19.15.Â Creating a virtual network"/><link rel="next" href="chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters.html" title="ChapterÂ 21.Â Configuring the Xen kernel boot parameters"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_le
 ft.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Creating_a_virtual_network.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-The_xm_command_quick_reference">ChapterÂ 20.Â The xm command quick reference</h2></div></div></div><div class="para">
		The <code class="command">xm</code> command can manage the Xen hypervisor. Most operations can be performed with the libvirt tools, <span class="application"><strong>virt-manager</strong></span> application or the <code class="command">virsh</code> command. The <code class="command">xm</code> command does not have the error checking capacity of the libvirt tools and should not be used for tasks the libvirt tools support.
	</div><div class="para">
		There are a few operations which currently can not be performed using <span class="application"><strong>virt-manager</strong></span>. Some options for other Xen implementations of the <code class="command">xm</code> command do not work in Fedora. The list below provides an overview of command options available and unavailable.
	</div><div class="warning"><h2>Warning</h2><div class="para">
			It is advised to use <code class="command">virsh</code> or <code class="command">virt-manager</code> instead of <code class="command">xm</code>. The <code class="command">xm</code> command does not handle error checking or configuration file errors very well and mistakes can lead to system instability or errors in virtual machines. Editing Xen configuration files manually is dangerous and should be avoided. Use this chapter at your own risk.
		</div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-The_xm_command_quick_reference-Basic_management_options">Basic management options</h5>
			The following are basic and commonly used <code class="command">xm</code> commands:
		</div><div class="itemizedlist"><ul><li><div class="para">
				<code class="command">xm help [--long]</code>: view available options and help text.
			</div></li><li><div class="para">
				use the <code class="command">xm list</code> command to list active domains:
			</div><pre class="screen">$ xm list
Name                                ID  Mem(MiB)   VCPUs      State      Time(s)
Domain-0                            0     520       2         r-----     1275.5
r5b2-mySQL01                       13     500       1         -b----       16.1
</pre></li><li><div class="para">
				<code class="command">xm create [-c] <em class="replaceable"><code>DomainName/ID</code></em></code>: start a virtual machine. If the -c option is used, the start up process will attach to the guest's console.
			</div></li><li><div class="para">
				<code class="command">xm console <em class="replaceable"><code>DomainName/ID</code></em></code>: attach to a virtual machine's console.
			</div></li><li><div class="para">
				<code class="command">xm destroy <em class="replaceable"><code>DomainName/ID</code></em></code>: terminates a virtual machine , similar to a power off.
			</div></li><li><div class="para">
				<code class="command">xm reboot <em class="replaceable"><code>DomainName/ID</code></em></code>: reboot a virtual machine, runs through the normal system shut down and start up process.
			</div></li><li><div class="para">
				<code class="command">xm shutdown <em class="replaceable"><code>DomainName/ID</code></em></code>: shut down a virtual machine, runs a normal system shut down procedure.
			</div></li><li><div class="para">
				<code class="command">xm pause</code>
			</div></li><li><div class="para">
				<code class="command">xm unpause</code>
			</div></li><li><div class="para">
				<code class="command">xm save</code>
			</div></li><li><div class="para">
				<code class="command">xm restore</code>
			</div></li><li><div class="para">
				<code class="command">xm migrate</code>
			</div></li></ul></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-The_xm_command_quick_reference-Resource_management_options">Resource management options</h5>
			Use the following <code class="command">xm</code> commands to manage resources:
		</div><div class="itemizedlist"><ul><li><div class="para">
				<code class="command">xm mem-set</code>
			</div></li><li><div class="para">
				use the <code class="command">xm vcpu-list</code> to list virtualized CPU affinities:
			</div><pre class="screen">$ xm vcpu-list
Name                          ID  VCPUs   CPU State  Time(s)  CPU Affinity
Domain-0                       0    0      0    r--   708.9    any cpu
Domain-0                       0    1      1   -b-    572.1    any cpu
r5b2-mySQL01                  13    0      1   -b-     16.1    any cpu
</pre></li><li><div class="para">
				<code class="command">xm vcpu-pin</code>
			</div></li><li><div class="para">
				<code class="command">xm vcpu-set</code>
			</div></li><li><div class="para">
				use the <code class="command">xm sched-credit</code> command to display scheduler parameters for a given domain:
			</div><pre class="screen">$ xm sched-credit -d 0
{'cap': 0, 'weight': 256}
$ xm sched-credit -d 13
{'cap': 25, 'weight': 256}
</pre></li></ul></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-The_xm_command_quick_reference-Monitoring_and_troubleshooting_options">Monitoring and troubleshooting options</h5>
			Use the following <code class="command">xm</code> commands for monitoring and troubleshooting:
		</div><div class="itemizedlist"><ul><li><div class="para">
				<code class="command">xm top</code>
			</div></li><li><div class="para">
				<code class="command">xm dmesg</code>
			</div></li><li><div class="para">
				<code class="command">xm info</code>
			</div></li><li><div class="para">
				<code class="command">xm log</code>
			</div></li><li><div class="para">
				use the <code class="command">xm uptime</code> to display the uptime of guests and hosts:
			</div><pre class="screen">$ xm uptime
Name                       ID  Uptime
Domain-0                    0  3:42:18
r5b2-mySQL01               13  0:06:27
</pre></li><li><div class="para">
				<code class="command">xm sysrq</code>
			</div></li><li><div class="para">
				<code class="command">xm dump-core</code>
			</div></li><li><div class="para">
				<code class="command">xm rename</code>
			</div></li><li><div class="para">
				<code class="command">xm domid</code>
			</div></li><li><div class="para">
				<code class="command">xm domname</code>
			</div></li></ul></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-The_xm_command_quick_reference-Currently_unsupported_options">Currently unsupported options</h5>
			The <code class="command">xm vnet-list</code> is currently unsupported.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Creating_a_virtual_network.html"><strong>Prev</strong>19.15.Â Creating a virtual network</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters.html"><strong>Next</strong>ChapterÂ 21.Â Configuring the Xen kernel boot param...</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Tips_and_tricks.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 23.Â Tips and tricks</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Tips_and_Tricks.html" title="PartÂ V.Â Tips and Tricks"/><link rel="prev" href="part-Virtualization_Guide-Tips_and_Tricks.html" title="PartÂ V.Â Tips and Tricks"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html" title="23.2.Â Changing between the KVM and Xen hypervisors"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/imag
 es/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Tips_and_Tricks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Tips_and_tricks">ChapterÂ 23.Â Tips and tricks</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Tips_and_tricks.html#sect-Virtualization_Guide-Tips_and_tricks-Automatically_starting_guests">23.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html">23.2. Changing between the KVM and Xen hypervisors</a></span></dt><dd><dl><dt><span cla
 ss="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html#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.html">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.html">23.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html">23.4. Overcommitting with KVM</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html">23.5. Modifying /etc/grub.conf</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html">23.6. Verifying virtualization ext
 ensions</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation.html">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.html">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.html">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.html">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.html">23.11. Modifying the Xen hypervisor</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks
 -Very_Secure_ftpd.html">23.12. Very Secure ftpd</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html">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.html">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.html">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.html">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.html">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.html">23.18. Duplicating an existing guest and its configuration file</a></span></dt></dl></div><div class="para">
		This chapter contain useful hints and tips to improve virtualization performance, scale and stability.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Automatically_starting_guests">23.1.Â Automatically starting guests</h2></div></div></div><div class="para">
			This section covers how to make virtualized guests start automatically during the host system's boot phase.
		</div><div class="para">
			This example uses <code class="command">virsh</code> to set a guest, <em class="parameter"><code>TestServer</code></em>, to automatically start when the host boots.
		</div><pre class="screen"># virsh autostart <em class="parameter"><code>TestServer</code></em>
Domain TestServer marked as autostarted
</pre><div class="para">
			The guest now automatically starts with the host.
		</div><div class="para">
			To stop a guest automatically booting use the <em class="parameter"><code>--disable</code></em> parameter
		</div><pre class="screen"># virsh autostart --disable <em class="parameter"><code>TestServer</code></em>
Domain TestServer unmarked as autostarted
</pre><div class="para">
			The guest no longer automatically starts with the host.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Tips_and_Tricks.html"><strong>Prev</strong>PartÂ V.Â Tips and Tricks</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html"><strong>Next</strong>23.2.Â Changing between the KVM and Xen hypervisors</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Troubleshooting.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 26.Â Troubleshooting</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Troubleshooting.html" title="PartÂ VI.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-The_layout_of_the_log_directories.html" title="25.15.Â The layout of the log directories"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes.html" title="26.2.Â After rebooting Xen-based guests the console freezes"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="ri
 ght" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-The_layout_of_the_log_directories.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Troubleshooting">ChapterÂ 26.Â Troubleshooting</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Troubleshooting.html#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-Trouble
 shooting-After_rebooting_Xen_based_guests_the_console_freezes.html">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.html">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.html">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_shortage.html">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.html">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_kerne
 l_on_a_PAE_platform.html">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.html">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.html">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.html">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.html">26.11. Wrong bridge configured on the guest causing hot plug script timeouts</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Gui
 de-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine.html">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.html">26.13. Enabling Intel VT and AMD-V virtualization hardware extensions in BIOS</a></span></dt></dl></div><div class="para">
		This chapter covers common problems and solutions with Fedora virtualization.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting-Identifying_available_storage_and_partitions">26.1.Â Identifying available storage and partitions</h2></div></div></div><div class="para">
			Verify the block driver is loaded and the devices and partitions are available to the guest. This can be done by executing "<code class="command">cat /proc/partitions</code>" as seen below.
		</div><pre class="screen"># cat /proc/partitions
major minor  #blocks   name 
 202    16  104857600  xvdb
   3     0    8175688  hda
</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-The_layout_of_the_log_directories.html"><strong>Prev</strong>25.15.Â The layout of the log directories</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes.html"><strong>Next</strong>26.2.Â After rebooting Xen-based guests the consol...</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Troubleshooting_Xen.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 25.Â Troubleshooting Xen</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Troubleshooting.html" title="PartÂ VI.Â Troubleshooting"/><link rel="prev" href="part-Virtualization_Guide-Troubleshooting.html" title="PartÂ VI.Â Troubleshooting"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html" title="25.2.Â Log files overview"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Sit
 e"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Troubleshooting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Troubleshooting_Xen">ChapterÂ 25.Â Troubleshooting Xen</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Troubleshooting_Xen.html#sect-Virtualization_Guide-Troubleshooting_Xen-Debugging_and_troubleshooting_Xen">25.1. Debugging and troubleshooting Xen</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html">25.2. Log files overview</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html">
 25.3. Log file descriptions</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html">25.4. Important directory locations</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs.html">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.html">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.html">25.7. Para-virtualized guest console access</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html">25.8. Fully virtualized guest console access</a></span></dt><dt><span class="section"><a href="sect-Virtualizati
 on_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image.html">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.html">25.10. Common Xen problems</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html">25.11. Guest creation errors</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html">25.12. Troubleshooting with serial consoles</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html#sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_for_Xen">25.12.1. Serial console output for Xen</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-X
 en_serial_console_output_from_para_virtualized_guests.html">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.html">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.html">25.13. Guest configuration files</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html">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.html">25.15. The layout of the log directories</a></span></dt></dl></div><div class="para">
		This chapter covers essential concepts to assist you in troubleshooting problems in Xen. Troubleshooting topics covered in this chapter include: 
		<div class="itemizedlist"><ul><li><div class="para">
					troubleshooting tools for Fedora and virtualization.
				</div></li><li><div class="para">
					troubleshooting techniques for identifying problems.
				</div></li><li><div class="para">
					The location of log files and explanations of the information in logs.
				</div></li></ul></div>
	</div><div class="para">
		This chapter is to give you, the reader, a background to identify where problems with virtualization technologies are. Troubleshooting takes practice and experience which are difficult to learn from a book. It is recommended that you experiment and test virtualization on Fedora to develop your troubleshooting skills.
	</div><div class="para">
		If you cannot find the answer in this document there may be an answer online from the virtualization community. Refer to <a class="xref" href="appe-Virtualization_Guide-Additional_resources.html#sect-Virtualization_Guide-Additional_resources-Online_resources" title="B.1.Â Online resources">SectionÂ B.1, â€œOnline resourcesâ€</a> for a list of Linux virtualization websites.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Debugging_and_troubleshooting_Xen">25.1.Â Debugging and troubleshooting Xen</h2></div></div></div><div class="para">
			This section summarizes the System Administrator applications, the networking utilities, and debugging tools. You can employ these standard System administration tools and logs to assist with troubleshooting:
		</div><div class="variablelist" id="vari-Virtualization_Guide-Debugging_and_troubleshooting_Xen-Useful_commands_and_applications_for_troubleshooting"><h6>Useful commands and applications for troubleshooting</h6><dl><dt><span class="term"><code class="command">xentop</code></span></dt><dd><div class="para">
						<code class="command">xentop</code> displays real-time information about a host system and the guest domains.
					</div></dd><dt><span class="term"><code class="command">xm</code></span></dt><dd><div class="para">
						Using the <code class="command">dmesg</code> and <code class="command">log</code>
					</div></dd></dl></div><div class="itemizedlist"><ul><li><div class="para">
					<code class="command">vmstat</code>
				</div></li><li><div class="para">
					<code class="command">iostat</code>
				</div></li><li><div class="para">
					<code class="command">lsof</code>
				</div></li></ul></div><div class="para">
			The <code class="command">iostat</code>, <code class="command">mpstat</code> and <code class="command">sar</code> commands are all provided by the <code class="filename">sysstat</code> package.
		</div><div class="para">
			You can employ these Advanced Debugging Tools and logs to assist with troubleshooting:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="command">XenOprofile</code>
				</div></li><li><div class="para">
					<code class="command">systemtap</code>
				</div></li><li><div class="para">
					<code class="command">crash</code>
				</div></li><li><div class="para">
					<code class="command">sysrq</code>
				</div></li><li><div class="para">
					<code class="command">sysrq t</code>
				</div></li><li><div class="para">
					<code class="command">sysrq w</code>
				</div></li></ul></div><div class="para">
			These networking tools can assist with troubleshooting virtualization networking problems:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="command">ifconfig</code>
				</div></li><li><div class="para">
					<code class="command">tcpdump</code>
				</div><div class="para">
					The <code class="command">tcpdump</code> command 'sniffs' network packets. <code class="command">tcpdump</code> is useful for finding network abnormalities and problems with network authentication. There is a graphical version of <code class="command">tcpdump</code> named <code class="command">wireshark</code>.
				</div></li><li><div class="para">
					<code class="command">brctl</code>
				</div><div class="para">
					<code class="command">brctl</code> is a networking tool that inspects and configures the Ethernet bridge configuration in the Virtualization Linux kernel. You must have root access before performing these example commands:
				</div><pre class="screen"># brctl show 

bridge-name    bridge-id          STP  enabled  interfaces  
-----------------------------------------------------------------------------
xenbr0             8000.feffffff       no        vif13.0
xenbr1             8000.ffffefff       yes       pddummy0
xenbr2             8000.ffffffef       no        vif0.0

# brctl showmacs xenbr0

port-no           mac-addr                  local?       aging timer

1                 fe:ff:ff:ff:ff:           yes            0.00
2                 fe:ff:ff:fe:ff:           yes            0.00

# brctl showstp xenbr0

xenbr0 

bridge-id              8000.fefffffffff

designated-root        8000.fefffffffff

root-port              0                   path-cost             0

max-age                20.00               bridge-max-age        20.00

hello-time             2.00                bridge-hello-time     2.00

forward-delay          0.00                bridge-forward-delay  0.00

aging-time            300.01

hello-timer            1.43                tcn-timer             0.00

topology-change-timer  0.00                gc-timer              0.02
</pre></li></ul></div><div class="para">
			Listed below are some other useful commands for troubleshooting virtualization on Fedora. 
		</div><div class="itemizedlist"><ul><li><div class="para">
					<span class="application"><strong>strace</strong></span> is a command which traces system calls and events received and used by another process.
				</div></li><li><div class="para">
					<span class="application"><strong>vncviewer</strong></span>: connect to a VNC server running on your server or a virtual machine. Install <span class="application"><strong>vncviwer</strong></span> using the <code class="command"> yum install vnc</code> command.
				</div></li><li><div class="para">
					<span class="application"><strong>vncserver</strong></span>: start a remote desktop on your server. Gives you the ability to run graphical user interfaces such as virt-manager via a remote session. Install <span class="application"><strong>vncserver</strong></span> using the <code class="command">yum install vnc-server</code> command.
				</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Troubleshooting.html"><strong>Prev</strong>PartÂ VI.Â Troubleshooting</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html"><strong>Next</strong>25.2.Â Log files overview</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 27.Â Troubleshooting the Xen para-virtualized drivers</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Troubleshooting.html" title="PartÂ VI.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html" title="26.13.Â Enabling Intel VT and AMD-V virtualization hardware extensions in BIOS"/><link rel="next" 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.html" title="27.2.Â Para-virtualized guest fail to load on a Red Hat Enterprise
  Linux 3 guest operating system"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" 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.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers">ChapterÂ 27.Â Troubleshootin
 g the Xen para-virtualized drivers</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html#sect-Virtualization_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.html">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.html">27.3. Manually loading the para-virtualized drivers</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Gu
 ide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_have_successfully_loaded.html">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.html">27.5. The system has limited throughput with para-virtualized drivers</a></span></dt></dl></div><div class="para">
		This chapter deals with issues you may encounter with Xen hosts and fully virtualized Linux guests using the para-virtualized drivers.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Fedora_Virtualization_log_file_and_directories">27.1.Â Fedora Virtualization log file and directories</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Linux_5_Virtualization_log_file_and_directories-Fedora_Virtualization_related_log_file">Linux 5 Virtualization related log file</h5>
				In Fedora, the log file written by the <code class="command">xend</code> daemon and the <code class="command">qemu-dm</code> process are all kept in the following directories:
			</div><div class="variablelist"><dl><dt><span class="term"><code class="filename">/var/log/xen/</code></span></dt><dd><div class="para">
						directory holding all log file generated by the <code class="command">xend</code> daemon and qemu-dm process.
					</div></dd><dt><span class="term"><code class="filename">xend.log</code></span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
								This logfile is used by xend to log any events generate by either normal system events or operator initiated events.
							</div></li><li><div class="para">
								virtual machine operations such as create, shutdown, destroy etc are all logged in this logfile.
							</div></li><li><div class="para">
								Usually this logfile will be the first place to look at in the event of a problem. In many cases you will be able to identify the root cause by scanning the logfile and review the entries logged just prior to the actual error message.
							</div></li></ul></div></dd><dt><span class="term"><code class="filename">xend-debug.log</code></span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
								Records error events from xend and its subsystems (from the framebuffer and Python scripts)
							</div></li></ul></div></dd><dt><span class="term"><code class="filename">xen-hotplug.log</code></span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
								Logs events from hotplug events.
							</div></li><li><div class="para">
								Event notifications from devices not coming online or network bridges not online are logged in this file.
							</div></li></ul></div></dd><dt><span class="term"><code class="filename">qemu-dm.<em class="replaceable"><code>PID</code></em>.log</code></span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
								This file is created by the <code class="command">qemu-dm</code> process which is started for each fully virtualized guest.
							</div></li><li><div class="para">
								The <code class="computeroutput">PID</code> is replaced with the <code class="computeroutput">PID</code> of the process of the related qemu-dm process
							</div></li><li><div class="para">
								You can retrieve the <code class="computeroutput">PID</code> for a given <code class="command">qemu-dm</code> process using the <code class="command">ps</code> command and in looking at the process arguments you can identify the virtual machine the <code class="command">qemu-dm</code> process belongs to.
							</div></li></ul></div></dd></dl></div><div class="para">
			If you are troubleshooting a problem with the <span class="application"><strong>virt-manager</strong></span> application you can also review the logfile generated by it. The logfile for <span class="application"><strong>virt-manager</strong></span> will be in a directory called <code class="filename">.virt-manager</code> in the user's <code class="filename">home</code> directory whom ran <span class="application"><strong>virt-manager</strong></span>. This directory will usually be <code class="filename">~/.virt-manager/virt-manager</code>.
		</div><div class="note"><h2>Note</h2><div class="para">
				The logfile is overwritten every time you start <span class="application"><strong>virt-manager</strong></span>. If you are troubleshooting a problem with <span class="application"><strong>virt-manager</strong></span> make sure you save the logfile before you restart <span class="application"><strong>virt-manager</strong></span> after an error has occurred.
			</div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Fedora_Virtualization_log_file_and_directories-Linux_5_Virtualization_related_directories">Fedora Virtualization related directories</h5>
				There are a few other directories and files which may be of interest when troubleshooting a Fedora Virtualization environment:
			</div><div class="variablelist"><dl><dt><span class="term"><code class="filename">/var/lib/libvirt/images/</code></span></dt><dd><div class="para">
						the standard directory for file-based guest images.
					</div></dd><dt><span class="term"><code class="filename">/var/lib/xen/xend-db/</code></span></dt><dd><div class="para">
						directory that hold the xend database which is generated every time the daemon is restarted.
					</div></dd><dt><span class="term"><code class="filename">/etc/xen/</code></span></dt><dd><div class="para">
						Stores a number of configuration files for the Xen hypervisor.
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="filename">/etc/xen/xend-config.sxp</code> is the main configuration for the xend daemon. The <code class="command">xend-config.sxp</code> file enables or disables migration and other features not configured by <code class="command">libvirt</code>. Use the <code class="command">libvirt</code> tools for all other features.
							</div></li></ul></div></dd><dt><span class="term"><code class="filename">/var/xen/dump/</code></span></dt><dd><div class="para">
						Holds dumps generate by virtual machines or when using the <code class="command">xm dump-core</code> command.
					</div></dd><dt><span class="term"><code class="filename">/proc/xen/</code></span></dt><dd><div class="para">
						Stores <code class="command">xen-kernel</code> information in the following files:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="filename">/proc/xen/capabilities</code>
							</div></li><li><div class="para">
								<code class="filename">/proc/xen/privcmd</code>
							</div></li><li><div class="para">
								<code class="filename">/proc/xen/balloon</code>
							</div></li><li><div class="para">
								<code class="filename">/proc/xen/xenbus</code>
							</div></li><li><div class="para">
								<code class="filename">/proc/xen/xsd_port</code>
							</div></li><li><div class="para">
								<code class="filename">/proc/xen/xsd_kva</code>
							</div></li></ul></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html"><strong>Prev</strong>26.13.Â Enabling Intel VT and AMD-V virtualization...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" 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.html"><strong>Next</strong>27.2.Â Para-virtualized guest fail to load on a Re...</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Virtualization_tools.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 17.Â Virtualization tools</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html" title="PartÂ IV.Â Virtualization Reference Guide"/><link rel="prev" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html" title="PartÂ IV.Â Virtualization Reference Guide"/><link rel="next" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html" title="ChapterÂ 18.Â Managing guests with virsh"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img sr
 c="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Virtualization_tools">ChapterÂ 17.Â Virtualization tools</h2></div></div></div><div class="para">
		The following is a list of tools for virtualization administration, debugging and networking tools that are useful for systems running Xen.
	</div><div class="variablelist"><dl><dt><span class="term">System Administration Tools</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
							<code class="command">vmstat</code>
						</div></li><li><div class="para">
							<code class="command">iostat</code>
						</div></li><li><div class="para">
							<code class="command">lsof</code>
						</div><pre class="screen"># lsof -i :5900
xen-vncfb 10635  root  5u  IPv4 218738  TCP grumble.boston.redhat.com:5900 (LISTEN)
</pre></li><li><div class="para">
							<code class="command">qemu-img</code>
						</div></li></ul></div></dd><dt><span class="term">Advanced Debugging Tools</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
							<code class="command">systemTap</code>
						</div></li><li><div class="para">
							<code class="command">crash</code>
						</div></li><li><div class="para">
							<code class="command">xen-gdbserver</code>
						</div></li><li><div class="para">
							<code class="command">sysrq</code>
						</div></li><li><div class="para">
							<code class="command">sysrq t</code>
						</div></li><li><div class="para">
							<code class="command">sysrq w</code>
						</div></li><li><div class="para">
							<code class="command">sysrq c</code>
						</div></li></ul></div></dd><dt><span class="term">Networking</span></dt><dd><div class="para">
					<code class="command">brtcl</code>
				</div><div class="itemizedlist"><ul><li><pre class="screen"># brctl show
bridge name  bridge id            STP enabled    interfaces
xenbr0       8000.feffffffffff    no             vif13.0
						 pdummy0
                                                 vif0.0
</pre></li><li><pre class="screen"># brctl showmacs xenbr0
port no  mac addr                is local?       aging timer
  1      fe:ff:ff:ff:ff:ff       yes             0.00
</pre></li><li><pre class="screen"># brctl showstp xenbr0
xenbr0
bridge id              8000.feffffffffff
designated root        8000.feffffffffff
root port              0                    path cost                 0
max age                20.00                bridge max age            20.00
hello time             2.00                 bridge hello time         2.00
forward delay          0.00                 bridge forward delay      0.00
aging time            300.01
hello timer            1.43                 tcn timer                 0.00
topology change timer  0.00                 gc timer                  0.02
flags

vif13.0 (3)
port id                8003                 state                    forwarding
designated root        8000.feffffffffff    path cost                100
designated bridge      8000.feffffffffff    message age timer        0.00
designated port        8003                 forward delay timer      0.00
designated cost        0                    hold timer               0.43
flags

pdummy0 (2)
port id                8002                 state                    forwarding
designated root        8000.feffffffffff    path cost                100
designated bridge      8000.feffffffffff    message age timer        0.00
designated port        8002                 forward delay timer      0.00
designated cost        0                    hold timer               0.43
flags

vif0.0 (1)
port id                8001                 state                    forwarding
designated root        8000.feffffffffff    path cost                100
designated bridge      8000.feffffffffff    message age timer        0.00
designated port        8001                 forward delay timer      0.00
designated cost        0                    hold timer               0.43
flags
</pre></li><li><div class="para">
							<code class="command">ifconfig</code>
						</div></li><li><div class="para">
							<code class="command">tcpdump</code>
						</div></li></ul></div></dd><dt><span class="term">KVM tools</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
							<code class="command">ps</code>
						</div></li><li><div class="para">
							<code class="command">pstree</code>
						</div></li><li><div class="para">
							<code class="command">top</code>
						</div></li><li><div class="para">
							<code class="command">kvmtrace</code>
						</div></li><li><div class="para">
							<code class="command">kvm_stat</code>
						</div></li></ul></div></dd><dt><span class="term">Xen tools</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
							<code class="command">xentop</code>
						</div></li><li><div class="para">
							<code class="command">xm dmesg</code>
						</div></li><li><div class="para">
							<code class="command">xm log</code>
						</div></li></ul></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html"><strong>Prev</strong>PartÂ IV.Â Virtualization Reference Guide</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html"><strong>Next</strong>ChapterÂ 18.Â Managing guests with virsh</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Virtualized_block_devices.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 4.Â Virtualized block devices</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Configuration.html" title="PartÂ II.Â Configuration"/><link rel="prev" href="part-Virtualization_Guide-Configuration.html" title="PartÂ II.Â Configuration"/><link rel="next" href="sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests.html" title="4.2.Â Adding storage devices to guests"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_rig
 ht.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Virtualized_block_devices">ChapterÂ 4.Â Virtualized block devices</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Virtualized_block_devices.html#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.html">4.2. Adding storage devices to gues
 ts</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html">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.html">4.4. Add a virtualized CD-ROM or DVD device to a guest</a></span></dt></dl></div><div class="para">
		This chapter covers installing and configuring block devices in virtualized guests. The term block devices refers to various forms of storage devices.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Virtualized_block_devices-Creating_a_virtualized_floppy_disk_controller">4.1.Â Creating a virtualized floppy disk controller</h2></div></div></div><div class="para">
			Floppy disk controllers are required for a number of older operating systems, especially for installing drivers. Presently, physical floppy disk devices cannot be accessed from virtualized guests. However, creating and accessing floppy disk images from virtualized floppy drives is supported. This section covers creating a virtualized floppy device.
		</div><div class="para">
			An image file of a floppy disk is required. Create floppy disk image files with the <code class="command">dd</code> command. Replace /dev/fd0 with the name of a floppy device and name the disk appropriately. 
<pre class="screen"># dd if=/dev/fd0 of=~/legacydrivers.img
</pre>
		</div><div class="note"><h2>Para-virtualized drivers note</h2><div class="para">
				The para-virtualized drivers can map physical floppy devices to fully virtualized guests. For more information on using para-virtualized drivers read <a class="xref" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html" title="ChapterÂ 10.Â Xen Para-virtualized Drivers">ChapterÂ 10, <i>Xen Para-virtualized Drivers</i></a>.
			</div></div><div class="para">
			This example uses a guest created with <code class="command">virt-manager</code> running a fully virtualized Linux installation with an image located in <code class="filename">/var/lib/libvirt/images/rhel5FV.img</code>. The Xen hypervisor is used in the example.
		</div><div class="procedure"><ol class="1"><li><div class="para">
					Create the XML configuration file for your guest image using the <code class="command">virsh</code> command on a running guest.
				</div><pre class="screen"># virsh dumpxml rhel5FV > rhel5FV.xml
</pre><div class="para">
					This saves the configuration settings as an XML file which can be edited to customize the operations and devices used by the guest. For more information on using the virsh XML configuration files, refer to <a class="xref" href="chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html" title="ChapterÂ 24.Â Creating custom libvirt scripts">ChapterÂ 24, <i>Creating custom libvirt scripts</i></a>.
				</div></li><li><div class="para">
					Create a floppy disk image for the guest.
				</div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/rhel5FV-floppy.img bs=512 count=2880
</pre></li><li><div class="para">
					Add the content below, changing where appropriate, to your guest's configuration XML file. This example creates a guest with a floppy device as a file based virtual device.
				</div><pre class="screen"><disk type='file' device='floppy'>
	<source file='/var/lib/libvirt/images/rhel5FV-floppy.img'/>
	<target dev='fda'/>
</disk>
</pre></li><li><div class="para">
					Stop the guest.
				</div><pre class="screen"># virsh stop rhel5FV
</pre></li><li><div class="para">
					Restart the guest using the XML configuration file.
				</div><pre class="screen"># virsh create rhel5FV.xml
</pre></li></ol></div><div class="para">
			The floppy device is now available in the guest and stored as an image file on the host.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Virtualization_Guide-Configuration.html"><strong>Prev</strong>PartÂ II.Â Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Next</strong>4.2.Â Adding storage devices to guests</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Virtualized_guest_installation_overview.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 2.Â Virtualized guest installation overview</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Installation.html" title="PartÂ I.Â Installation"/><link rel="prev" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system.html" title="1.4.Â Installing KVM packages on an existing Fedora system"/><link rel="next" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager.html" title="2.2.Â Creating guests with virt-manager"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/ima
 ges/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Virtualized_guest_installation_overview">ChapterÂ 2.Â Virtualized guest installation overview</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html#sect-Virtualization_Guide-Virtualized_guest_installa
 tion_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.html">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.html">2.3. Installing guests with PXE</a></span></dt></dl></div><div class="para">
		After you have installed the virtualization packages on the host system you can create guest operating systems. This chapter describes the general processes for installing guest operating systems on virtual machines. You can create guests using the <span class="guibutton"><strong>New</strong></span> button in <span class="application"><strong>virt-manager</strong></span> or use the command line interface <code class="command">virt-install</code>. Both methods are covered by this chapter.
	</div><div class="para">
		Detailed installation instructions are available for specific versions of Fedora, other Linux distributions, Solaris and Windows. Refer to <a class="xref" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html" title="ChapterÂ 3.Â Guest operating system installation procedures">ChapterÂ 3, <i>Guest operating system installation procedures</i></a> for those procedures.
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_install">2.1.Â Creating guests with virt-install</h2></div></div></div><div class="para">
			You can use the <code class="command">virt-install</code> command to create virtualized guests from the command line. <code class="command">virt-install</code> is used either interactively or as part of a script to automate the creation of virtual machines. Using <code class="command">virt-install</code> with Kickstart files allows for unattended installation of virtual machines.
		</div><div class="para">
			The <code class="command">virt-install</code> tool provides a number of options one can pass on the command line. To see a complete list of options run:
		</div><pre class="screen">$ virt-install --help
</pre><div class="para">
			The <code class="command">virt-install</code> man page also documents each command option and important variables.
		</div><div class="para">
			<code class="command">qemu-img</code> is a related command which may be used before <code class="command">virt-install</code> to configure storage options.
		</div><div class="para">
			An important option is the <em class="parameter"><code>--vnc</code></em> option which opens a graphical window for the guest's installation.
		</div><div class="example" id="exam-Virtualization_Guide-Creating_guests_with_virt_install-Using_virt_install_with_KVM_to_create_a_Linux_3_guest"><div class="example-contents"><div class="para">
				This example creates a Red Hat Enterprise Linux 3 guest, named <em class="parameter"><code>rhel3support</code></em>, from a CD-ROM, with virtual networking and with a 5 GB file-based block device image. This example uses the KVM hypervisor.
			</div><pre class="screen"># virt-install --accelerate --hvm --connect qemu:///system \
	--network network:default \
	--name rhel3support --ram=756\
	--file=/var/lib/libvirt/images/rhel3support.img \
	--file-size=6 --vnc --cdrom=/dev/sr0
</pre></div><h6>ExampleÂ 2.1.Â Using virt-install with KVM to create a Red Hat Enterprise Linux 3 guest</h6></div><br class="example-break"/><div class="example" id="exam-Virtualization_Guide-Creating_guests_with_virt_install-Using_virt_install_to_create_a_Fedora_11_guest"><div class="example-contents"><pre class="screen"># virt-install --name Fedora11 --ram 512 --file=/var/lib/libvirt/images/Fedora11.img \
	--file-size=3 --vnc --cdrom=/var/lib/libvirt/images/Fedora11.iso
</pre></div><h6>ExampleÂ 2.2.Â Using virt-install to create a Fedora 11 guest</h6></div><br class="example-break"/></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system.html"><strong>Prev</strong>1.4.Â Installing KVM packages on an existing Fedor...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager.html"><strong>Next</strong>2.2.Â Creating guests with virt-manager</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 10.Â Xen Para-virtualized Drivers</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Configuration.html" title="PartÂ II.Â Configuration"/><link rel="prev" href="sect-Virtualization_Guide-Xen_networking-Laptop_network_configuration.html" title="9.2.Â Laptop network configuration"/><link rel="next" href="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html" title="10.2.Â Installing the Para-virtualized Drivers"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src
 ="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Xen_networking-Laptop_network_configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers">ChapterÂ 10.Â Xen Para-virtualized Drivers</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html#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.html">10.2. Installing the Para-v
 irtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html#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.html">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.html">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.html">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.html">10.3. Para-virtualized Network Driver Configuration</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html">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.html#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.html">10.4.2. Virtual Storage Devices</a></span></dt></dl></dd></dl></div><div c
 lass="para">
		<a class="firstterm" href="go01.html#glos-Virtualization_Guide-Para_virtualized_drivers"><em class="firstterm">Para-virtualized drivers</em></a> provide increased performance for fully virtualized Linux guests. Use these drivers if you are using fully virtualized Linux guests and require better performance.
	</div><div class="note"><h2>Other para-virtualized drivers</h2><div class="para">
			There are other para-virtualized drivers for Windows for both Xen and KVM hypervisors.
		</div><div class="para">
			For Windows guests on Xen hosts, refer to the <em class="citetitle">Windows Para-virtualized Drivers Guide</em> which covers installation and administration.
		</div><div class="para">
			For Windows guests on KVM hosts, refer to <a class="xref" href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html" title="ChapterÂ 11.Â KVM Para-virtualized Drivers">ChapterÂ 11, <i>KVM Para-virtualized Drivers</i></a>.
		</div></div><div class="para">
		The RPM packages for the para-virtualized drivers include the modules for storage and networking para-virtualized drivers for the supported Linux guest operating systems. These drivers enable high performance throughput of I/O operations in unmodified Linux guest operating systems.
	</div><div class="note"><h2>Architecture support for para-virtualized drivers</h2><div class="para">
			The minimum guest operating system requirements are architecture dependent. Only x86 and x86-64 guests are supported.
		</div></div><div class="para">
		Using Fedora as the virtualization platform allows System Administrators to consolidate Linux and Windows workloads onto newer, more powerful hardware with increased power and cooling efficiency. Red Hat Enterprise Linux 4 (as of update 6) and Red Hat Enterprise Linux 5 guest operating systems are aware of the underlying virtualization technology and can interact with it efficiently using specific interfaces and capabilities. This approach can achieve similar throughput and performance characteristics compared to running on the bare metal system.
	</div><div class="para">
		As this approach requires modifications in the guest operating system not all operating systems and use models can use para-virtualized virtualization. For operating systems which can not be modified the underlying virtualization infrastructure has to emulate the server hardware (CPU, Memory as well as IO devices for storage and network). Emulation for IO devices can be very slow and will be especially troubling for high-throughput disk and network subsystems. The majority of the performance loss occurs in this area.
	</div><div class="para">
		The para-virtualized device drivers part of the distributed RPM packages bring many of the performance advantages of para-virtualized guest operating systems to unmodified operating systems because only the para-virtualized device driver (but not the rest of the operating system) is aware of the underlying virtualization platform.
	</div><div class="para">
		After installing the para-virtualized device drivers, a disk device or network card will continue to appear as a normal, physical disk or network card to the operating system. However, now the device driver interacts directly with the virtualization platform (with no emulation) to efficiently deliver disk and network access, allowing the disk and network subsystems to operate at near native speeds even in a virtualized environment, without requiring changes to existing guest operating systems.
	</div><div class="para">
		The para-virtualized drivers have certain host requirements. 64 bit hosts can run: 
		<div class="itemizedlist"><ul><li><div class="para">
					32 bit guests.
				</div></li><li><div class="para">
					64 bit guests.
				</div></li><li><div class="para">
					a mixture of 32 bit and 64 bit guests.
				</div></li></ul></div>

	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Para_virtualization_Restrictions_and_Support">10.1.Â Para-virtualization Restrictions and Support</h2></div></div></div><div class="para">
		This section outlines support restrictions and requirements for using para-virtualized drivers on Fedora. 
	</div><div class="note"><h2>Finding which kernel you are using</h2><div class="para">
			Write the output of the command below down or remember it. This is the value that determines which packages and modules you need to download.
		</div><div class="para">
			<code class="command"># rpm -q --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' kernel </code>
		</div><div class="para">
			Your output should appear similar to this:
		</div><div class="para">
			<code class="command">kernel-PAE-2.6.18-53.1.4.el5.i686</code>
		</div><div class="para">
			The name of the kernel is PAE (an abbreviation of Physical Address Extensions), kernel version is 2.6.18, the release is 53.1.4.el5 and the architecture is i686. The kernel rpm should always be in the format <span class="application"><strong>kernel-name-version-release.arch.rpm</strong></span>.
		</div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Para_virtualization_Restrictions_and_Support-Important_Restrictions">Important Restrictions</h5>
			Para-virtualized device drivers can be installed after successfully installing a guest operating system. You will need a functioning host and guest before you can install these drivers.
		</div><div class="para">
		<div class="note"><h2>Para-virtualized block devices and GRUB</h2><div class="para">
				<span class="application"><strong>GRUB</strong></span> can not presently, access para-virtualized block devices. Therefore, a guest can not be booted from a device that uses the para-virtualized block device drivers. Specifically, the disk that contains the Master Boot Record(MBR), a disk containing a boot loader (<code class="command">GRUB</code>), or a disk that contains the kernel <code class="filename">initrd</code> images. That is, any disk which contains the <code class="filename">/boot</code> directory or partition can not use the para-virtualized block device drivers.
			</div></div>
	</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Para_virtualization_Restrictions_and_Support-Red_Hat_Enterprise_Linux_3_kernel_variant_architecture_dependencies">Red Hat Enterprise Linux 3 kernel variant architecture dependencies</h5>
			For Red Hat Enterprise Linux 3 based guest operating systems you must use the processor specific kernel and para-virtualized driver RPMs as seen in the tables below. If you fail to install the matching para-virtualized driver package loading of the <code class="command">xen-pci-platform</code> module will fail.
		</div><div class="para">
		The table below shows which host kernel is required to run a Red Hat Enterprise Linux 3 guest on if the guest was compiled for an Intel processor.
	</div><div class="table" id="tabl-Virtualization_Guide-Para_virtualization_Restrictions_and_Support-Required_host_kernel_architecture_for_guests_using_para_virtualized_drivers_on_Red_Hat_Enterprise_Linux_3_for_Intel_processors"><div class="table-contents"><table summary="Required host kernel architecture for guests using para-virtualized drivers on Red Hat Enterprise Linux 3 for Intel processors" border="1"><colgroup><col align="left"/><col align="left"/></colgroup><thead><tr><th align="left">
						Guest kernel type
					</th><th align="left">
						Required host kernel type
					</th></tr></thead><tbody><tr><td align="left">
						ia32e (UP and SMP)
					</td><td align="left">
						x86_64
					</td></tr><tr><td align="left">
						i686
					</td><td align="left">
						i686
					</td></tr><tr><td align="left">
						i686-SMP
					</td><td align="left">
						i686
					</td></tr><tr><td align="left">
						i686-HUGEMEM
					</td><td align="left">
						i686
					</td></tr></tbody></table></div><h6>TableÂ 10.1.Â Required host kernel architecture for guests using para-virtualized drivers on Red Hat Enterprise Linux 3 for Intel processors</h6></div><br class="table-break"/><div class="para">
		The table below shows which host kernel is required to run a Red Hat Enterprise Linux 3 guest on if the guest was compiled for an AMD processor.
	</div><div class="table" id="tabl-Virtualization_Guide-Para_virtualization_Restrictions_and_Support-Required_host_kernel_architectures_for_guests_using_para_virtualized_drivers_on_Red_Hat_Enterprise_Linux_3_for_AMD_processors"><div class="table-contents"><table summary="Required host kernel architectures for guests using para-virtualized drivers on Red Hat Enterprise Linux 3 for AMD processors" border="1"><colgroup><col align="left"/><col align="left"/></colgroup><thead><tr><th align="left">
						Guest kernel type
					</th><th align="left">
						Required host kernel type
					</th></tr></thead><tbody><tr><td align="left">
						athlon
					</td><td align="left">
						i686
					</td></tr><tr><td align="left">
						athlon-SMP
					</td><td align="left">
						i686
					</td></tr><tr><td align="left">
						x86_64
					</td><td align="left">
						x86_64
					</td></tr><tr><td align="left">
						x86_64-SMP
					</td><td align="left">
						x86_64
					</td></tr></tbody></table></div><h6>TableÂ 10.2.Â Required host kernel architectures for guests using para-virtualized drivers on Red Hat Enterprise Linux 3 for AMD processors</h6></div><br class="table-break"/></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Xen_networking-Laptop_network_configuration.html"><strong>Prev</strong>9.2.Â Laptop network configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html"><strong>Next</strong>10.2.Â Installing the Para-virtualized Drivers</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Xen_configuration_files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 22.Â Xen configuration files</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html" title="PartÂ IV.Â Virtualization Reference Guide"/><link rel="prev" href="chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters.html" title="ChapterÂ 21.Â Configuring the Xen kernel boot parameters"/><link rel="next" href="part-Virtualization_Guide-Tips_and_Tricks.html" title="PartÂ V.Â Tips and Tricks"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><im
 g src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Tips_and_Tricks.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Xen_configuration_files">ChapterÂ 22.Â Xen configuration files</h2></div></div></div><div class="para">
		Fedora uses <code class="command">libvirt</code> configuration files for most tasks. Some users may need Xen configuration files which contain the following standard variables. Configuration items within these files must be enclosed in single quotes('). These configuration files reside in the <code class="command">/etc/xen</code> directory.
	</div><div class="table" id="tabl-Virtualization_Guide-Xen_configuration_files-libvirt_configuration_files"><div class="table-contents"><table summary="libvirt configuration files" border="1"><colgroup><col/><col/></colgroup><thead><tr><th>
						Item
					</th><th>
						Description
					</th></tr></thead><tbody><tr><td>
						<div class="para">
							<em class="parameter"><code>pae</code></em>
						</div>
					</td><td>
						<div class="para">
							Specifies the physical address extension configuration data.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>apic</code></em>
						</div>
					</td><td>
						<div class="para">
							Specifies the advanced programmable interrupt controller configuration data.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>memory</code></em>
						</div>
					</td><td>
						<div class="para">
							Specifies the memory size in megabytes.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>vcpus</code></em>
						</div>
					</td><td>
						<div class="para">
							Specifies the numbers of virtual CPUs.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>console</code></em>
						</div>
					</td><td>
						<div class="para">
							Specifies the port numbers to export the domain consoles to.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>nic</code></em>
						</div>
					</td><td>
						<div class="para">
							Specifies the number of virtual network interfaces.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>vif</code></em>
						</div>
					</td><td>
						<div class="para">
							Lists the randomly-assigned MAC addresses and bridges assigned to use for the domain's network addresses.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>disk</code></em>
						</div>
					</td><td>
						<div class="para">
							Lists the block devices to export to the domain and exports physical devices to domain with read only access.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>dhcp</code></em>
						</div>
					</td><td>
						<div class="para">
							Enables networking using DHCP.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>netmask</code></em>
						</div>
					</td><td>
						<div class="para">
							Specifies the configured IP netmasks.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>gateway</code></em>
						</div>
					</td><td>
						<div class="para">
							Specifies the configured IP gateways.
						</div>
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>acpi</code></em>
						</div>
					</td><td>
						<div class="para">
							Specifies the advanced configuration power interface configuration data.
						</div>
					</td></tr></tbody></table></div><h6>TableÂ 22.1.Â libvirt configuration files</h6></div><br class="table-break"/><div class="para">
		The table below, <a class="xref" href="chap-Virtualization_Guide-Xen_configuration_files.html#tabl-Virtualization_Guide-Xen_configuration_files-Xen_configuration_file_reference" title="TableÂ 22.2.Â Xen configuration file reference">TableÂ 22.2, â€œXen configuration file referenceâ€</a>, is formatted output from <code class="command">xm create --help_config</code>.
	</div><div class="table" id="tabl-Virtualization_Guide-Xen_configuration_files-Xen_configuration_file_reference"><div class="table-contents"><table summary="Xen configuration file reference" border="1"><colgroup><col/><col/></colgroup><thead><tr><th>
						<div class="para">
							Parameter
						</div>
					</th><th>
						<div class="para">
							Description
						</div>
					</th></tr></thead><tbody><tr><td>
						<em class="parameter"><code>vncpasswd</code></em>=<em class="replaceable"><code>NAME</code></em>
					</td><td>
						Password for VNC console on HVM domain.
					</td></tr><tr><td>
						vncviewer=<code class="command">no</code> | <code class="command"> yes </code>
					</td><td>
						Spawn a vncviewer listening for a vnc server in the domain. The address of the vncviewer is passed to the domain on the kernel command line using <em class="parameter"><code>VNC_SERVER=<host>:<port></code></em>. The port used by vnc is 5500 + DISPLAY. A display value with a free port is chosen if possible. Only valid when vnc=1.
					</td></tr><tr><td>
						<em class="parameter"><code>vncconsole</code></em>=<code class="command">no</code> | <code class="command">yes</code>
					</td><td>
						Spawn a vncviewer process for the domain's graphical console. Only valid when vnc=1.
					</td></tr><tr><td>
						<em class="parameter"><code>name</code></em>=<em class="replaceable"><code>NAME</code></em>
					</td><td>
						Domain name. Must be unique.
					</td></tr><tr><td>
						<em class="parameter"><code>bootloader</code></em>=<em class="replaceable"><code>FILE</code></em>
					</td><td>
						Path to boot loader.
					</td></tr><tr><td>
						<em class="parameter"><code>bootargs</code></em>=<em class="replaceable"><code>NAME</code></em>
					</td><td>
						Arguments to pass to boot loader.
					</td></tr><tr><td>
						<em class="parameter"><code>bootentry</code></em>=<em class="replaceable"><code>NAME</code></em>
					</td><td>
						DEPRECATED. Entry to boot via boot loader. Use <em class="parameter"><code>bootargs</code></em>.
					</td></tr><tr><td>
						<em class="parameter"><code>kernel</code></em>=<em class="replaceable"><code>FILE</code></em>
					</td><td>
						Path to kernel image.
					</td></tr><tr><td>
						<em class="parameter"><code>ramdisk</code></em>=<em class="replaceable"><code>FILE </code></em>
					</td><td>
						Path to ramdisk.
					</td></tr><tr><td>
						<em class="parameter"><code>features</code></em>=<em class="replaceable"><code>FEATURES</code></em>
					</td><td>
						Features to enable in guest kernel
					</td></tr><tr><td>
						<em class="parameter"><code>builder</code></em>=<em class="replaceable"><code>FUNCTION</code></em>
					</td><td>
						Function to use to build the domain.
					</td></tr><tr><td>
						<em class="parameter"><code>memory</code></em>=<em class="replaceable"><code>MEMORY</code></em>
					</td><td>
						Domain memory in MB.
					</td></tr><tr><td>
						<em class="parameter"><code>maxmem</code></em>=<em class="replaceable"><code>MEMORY</code></em>
					</td><td>
						Maximum domain memory in MB.
					</td></tr><tr><td>
						<em class="parameter"><code>shadow_memory</code></em>=<em class="replaceable"><code>MEMORY</code></em>
					</td><td>
						Domain shadow memory in MB.
					</td></tr><tr><td>
						<em class="parameter"><code>cpu</code></em>=<em class="replaceable"><code>CPU</code></em>
					</td><td>
						CPU which hosts VCPU0.
					</td></tr><tr><td>
						<em class="parameter"><code>cpus</code></em>=<em class="replaceable"><code>CPUS</code></em>
					</td><td>
						CPUS to run the domain on.
					</td></tr><tr><td>
						<em class="parameter"><code>pae</code></em>=<em class="replaceable"><code>PAE </code></em>
					</td><td>
						Disable or enable PAE of HVM domain.
					</td></tr><tr><td>
						<em class="parameter"><code>acpi</code></em>=<em class="replaceable"><code>ACPI</code></em>
					</td><td>
						Disable or enable ACPI of HVM domain.
					</td></tr><tr><td>
						<em class="parameter"><code>apic</code></em>=<em class="replaceable"><code>APIC </code></em>
					</td><td>
						Disable or enable APIC of HVM domain.
					</td></tr><tr><td>
						<em class="parameter"><code>vcpus</code></em>=<em class="replaceable"><code>VCPUs</code></em>
					</td><td>
						The number of Virtual CPUS in domain.
					</td></tr><tr><td>
						<em class="parameter"><code>cpu_weight</code></em>=<em class="replaceable"><code>WEIGHT</code></em>
					</td><td>
						Set the new domain's cpu weight. <em class="replaceable"><code>WEIGHT</code></em> is a float that controls the domain's share of the cpu.
					</td></tr><tr><td>
						<em class="parameter"><code>restart</code></em>=<em class="replaceable"><code>onreboot</code></em> | <em class="replaceable"><code> always</code></em> | <em class="replaceable"><code>never</code></em>
					</td><td>
						Deprecated. Use <em class="parameter"><code>on_poweroff,</code></em> <em class="parameter"><code>on_reboot</code></em>, and <em class="parameter"><code>on_crash</code></em> instead. Whether the domain should be restarted on exit. - <em class="parameter"><code>onreboot</code></em>: restart on exit with shutdown code reboot - always: always restart on exit, ignore exit code - never: never restart on exit, ignore exit code
					</td></tr><tr><td>
						<em class="parameter"><code>on_poweroff</code></em>=<em class="replaceable"><code>destroy </code></em>|<em class="replaceable"><code> restart </code></em>|<em class="replaceable"><code> preserve </code></em>|<em class="replaceable"><code> destroy </code></em>
					</td><td>
						Behavior when a domain exits with reason 'poweroff'. - destroy: the domain is cleaned up as normal; - restart: a new domain is started in place of the old one; - preserve: no clean-up is done until the domain is manually destroyed (using <code class="command">xm</code> destroy, for example); - rename-restart: the old domain is not cleaned up, but is renamed and a new domain started in its place.
					</td></tr><tr><td>
						<em class="parameter"><code>on_reboot</code></em>=<em class="replaceable"><code>destroy </code></em>|<em class="replaceable"><code> restart </code></em>|<em class="replaceable"><code> preserve </code></em>|<em class="replaceable"><code> destroy </code></em>
					</td><td>
						Behavior when a domain exits with reason 'reboot'. - destroy: the domain is cleaned up as normal; - restart: a new domain is started in place of the old one; - preserve: no clean-up is done until the domain is manually destroyed (using xm destroy, for example); - rename-restart: the old domain is not cleaned up, but is renamed and a new domain started in its place.
					</td></tr><tr><td>
						<em class="parameter"><code>on_crash</code></em>=<em class="replaceable"><code>destroy </code></em>|<em class="replaceable"><code> restart </code></em>|<em class="replaceable"><code> preserve </code></em>|<em class="replaceable"><code> destroy </code></em>
					</td><td>
						Behavior when a domain exits with reason 'crash'. - destroy: the domain is cleaned up as normal; - restart: a new domain is started in place of the old one; - preserve: no clean-up is done until the domain is manually destroyed (using xm destroy, for example); - rename-restart: the old domain is not cleaned up, but is renamed and a new domain started in its place.
					</td></tr><tr><td>
						<em class="parameter"><code>blkif</code></em>=<code class="command">no</code> | <code class="command">yes</code>
					</td><td>
						Make the domain a block device backend.
					</td></tr><tr><td>
						<em class="parameter"><code>netif</code></em>=<code class="command">no</code> | <code class="command">yes</code>
					</td><td>
						Make the domain a network interface backend.
					</td></tr><tr><td>
						<em class="parameter"><code>tpmif</code></em>=<code class="command">no</code> | <code class="command">yes</code>
					</td><td>
						Make the domain a TPM interface backend.
					</td></tr><tr><td>
						<em class="parameter"><code>disk</code></em>=<em class="replaceable"><code>phy:DEV,VDEV,MODE[,DOM]</code></em>
					</td><td>
						Add a disk device to a domain. The physical device is <em class="replaceable"><code>DEV</code></em>, which is exported to the domain as <em class="replaceable"><code>VDEV</code></em>. The disk is read-only if <em class="replaceable"><code>MODE</code></em> is <code class="command">r</code>, read-write if <em class="replaceable"><code>MODE</code></em> is <code class="command">w</code>. If <em class="replaceable"><code>DOM</code></em> is specified it defines the backend driver domain to use for the disk. The option may be repeated to add more than one disk.
					</td></tr><tr><td>
						<em class="parameter"><code>pci</code></em>=<em class="replaceable"><code>BUS:DEV.FUNC</code></em>
					</td><td>
						Add a PCI device to a domain, using given parameters (in hex). For example <em class="parameter"><code>pci=c0:02.1a</code></em>. The option may be repeated to add more than one pci device.
					</td></tr><tr><td>
						<em class="parameter"><code>ioports</code></em>=<em class="replaceable"><code>FROM[-TO]</code></em>
					</td><td>
						Add a legacy I/O range to a domain, using given params (in hex). For example <em class="parameter"><code>ioports=02f8-02ff</code></em>. The option may be repeated to add more than one i/o range.
					</td></tr><tr><td>
						<em class="parameter"><code>irq</code></em>=<em class="replaceable"><code>IRQ</code></em>
					</td><td>
						Add an IRQ (interrupt line) to a domain. For example <em class="parameter"><code>irq=7</code></em>. This option may be repeated to add more than one IRQ.
					</td></tr><tr><td>
						<em class="parameter"><code>usbport</code></em>=<em class="replaceable"><code>PATH</code></em>
					</td><td>
						Add a physical USB port to a domain, as specified by the path to that port. This option may be repeated to add more than one port.
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>vfb=type=<em class="replaceable"><code>{vnc,sdl}</code></em>, vncunused=<em class="replaceable"><code>1</code></em>, vncdisplay=<em class="replaceable"><code>N</code></em>,</code></em>
						</div>
						<div class="para">
							<em class="parameter"><code>vnclisten=<em class="replaceable"><code>ADDR</code></em>, display=<em class="replaceable"><code>DISPLAY</code></em>, </code></em>
						</div>
						<div class="para">
							<em class="parameter"><code>xauthority=<em class="replaceable"><code>XAUTHORITY</code></em>, vncpasswd=<em class="replaceable"><code>PASSWORD</code></em>,</code></em>
						</div>
						<div class="para">
							<em class="parameter"><code>keymap</code></em>=<em class="replaceable"><code>KEYMAP</code></em>
						</div>
					</td><td>
						Make the domain a framebuffer backend. The backend type should be either <em class="parameter"><code>sdl</code></em> or <em class="parameter"><code>vnc</code></em>. For <em class="parameter"><code>type=vnc</code></em>, connect an external vncviewer. The server will listen on <em class="replaceable"><code>ADDR</code></em> (default 127.0.0.1) on port N+5900. <em class="replaceable"><code>N</code></em> defaults to the domain id. If <em class="parameter"><code>vncunused=1</code></em>, the server will try to find an arbitrary unused port above 5900. For <em class="parameter"><code>type=sdl</code></em>, a viewer will be started automatically using the given <em class="replaceable"><code>DISPLAY</code></em> and <em class="replaceable"><code>XAUTHORITY</code></em>, which default to the current user's ones.
					</td></tr><tr><td>
						<div class="para">
							<em class="parameter"><code>vif=type=<em class="replaceable"><code>TYPE</code></em>, mac=<em class="replaceable"><code>MAC</code></em>, bridge=<em class="replaceable"><code>BRIDGE</code></em>, ip=<em class="replaceable"><code>IPADDR</code></em>,</code></em>
						</div>
						<div class="para">
							<em class="parameter"><code>script=<em class="replaceable"><code>SCRIPT</code></em>, backend=<em class="replaceable"><code>DOM</code></em>, vifname</code></em>=<em class="replaceable"><code>NAME</code></em>
						</div>
					</td><td>
						Add a network interface with the given <em class="replaceable"><code>MAC</code></em> address and bridge. The <em class="parameter"><code>vif</code></em> is configured by calling the given configuration script. If type is not specified, default is netfront not ioemu device. If mac is not specified a random <em class="replaceable"><code>MAC</code></em> address is used. If not specified then the network backend chooses it's own <em class="replaceable"><code>MAC</code></em> address. If bridge is not specified the first bridge found is used. If script is not specified the default script is used. If backend is not specified the default backend driver domain is used. If vifname is not specified the backend virtual interface will have name vifD.N where D is the domain id and N is the interface id. This option may be repeated to add more than one vif. Specifying vifs will increase the number of interfaces as needed.
					</td></tr><tr><td>
						<em class="parameter"><code>vtpm=instance=</code></em><em class="replaceable"><code>INSTANCE</code></em>,backend=<em class="replaceable"><code>DOM</code></em>
					</td><td>
						Add a TPM interface. On the backend side use the given instance as virtual TPM instance. The given number is merely the preferred instance number. The hotplug script will determine which instance number will actually be assigned to the domain. The association between virtual machine and the TPM instance number can be found in <code class="filename">/etc/xen/vtpm.db</code>. Use the backend in the given domain.
					</td></tr><tr><td>
						<em class="parameter"><code>access_control=policy=</code></em><em class="replaceable"><code>POLICY</code></em>,label=<em class="replaceable"><code>LABEL</code></em>
					</td><td>
						Add a security label and the security policy reference that defines it. The local ssid reference is calculated when starting or resuming the domain. At this time, the policy is checked against the active policy as well. This way, migrating through the save or restore functions are covered and local labels are automatically created correctly on the system where a domain is started or resumed.
					</td></tr><tr><td>
						<em class="parameter"><code>nics</code></em>=<em class="replaceable"><code>NUM</code></em>
					</td><td>
						DEPRECATED. Use empty vif entries instead. Set the number of network interfaces. Use the vif option to define interface parameters, otherwise defaults are used. Specifying vifs will increase the number of interfaces as needed.
					</td></tr><tr><td>
						<em class="parameter"><code>root</code></em>=<em class="replaceable"><code>DEVICE </code></em>
					</td><td>
						Set the <em class="parameter"><code>root</code></em>= parameter on the kernel command line. Use a device, e.g. <code class="filename">/dev/sda1</code>, or <code class="filename">/dev/nfs</code> for NFS root.
					</td></tr><tr><td>
						<em class="parameter"><code>extra</code></em>=<em class="replaceable"><code>ARGS</code></em>
					</td><td>
						Set extra arguments to append to the kernel command line.
					</td></tr><tr><td>
						<em class="parameter"><code>ip</code></em>=<em class="replaceable"><code>IPADDR </code></em>
					</td><td>
						Set the kernel IP interface address.
					</td></tr><tr><td>
						<em class="parameter"><code>gateway</code></em>=<em class="replaceable"><code>IPADDR</code></em>
					</td><td>
						Set the kernel IP gateway.
					</td></tr><tr><td>
						<em class="parameter"><code>netmask</code></em>=<em class="replaceable"><code>MASK</code></em>
					</td><td>
						Set the kernel IP netmask.
					</td></tr><tr><td>
						<em class="parameter"><code>hostname</code></em>=<em class="replaceable"><code>NAME</code></em>
					</td><td>
						Set the kernel IP hostname.
					</td></tr><tr><td>
						<em class="parameter"><code>interface</code></em>=<em class="replaceable"><code>INTF</code></em>
					</td><td>
						Set the kernel IP interface name.
					</td></tr><tr><td>
						<em class="parameter"><code>dhcp</code></em>=<em class="replaceable"><code>off|dhcp</code></em>
					</td><td>
						Set the kernel dhcp option.
					</td></tr><tr><td>
						<em class="parameter"><code>nfs_server</code></em>=<em class="replaceable"><code>IPADDR</code></em>
					</td><td>
						Set the address of the NFS server for NFS root.
					</td></tr><tr><td>
						<em class="parameter"><code>nfs_root</code></em>=<em class="replaceable"><code>PATH</code></em>
					</td><td>
						Set the path of the root NFS directory.
					</td></tr><tr><td>
						<em class="parameter"><code>device_model</code></em>=<em class="replaceable"><code>FILE</code></em>
					</td><td>
						Path to device model program.
					</td></tr><tr><td>
						<em class="parameter"><code>fda</code></em>=<em class="replaceable"><code>FILE</code></em>
					</td><td>
						Path to fda
					</td></tr><tr><td>
						<em class="parameter"><code>fdb</code></em>=<em class="replaceable"><code>FILE </code></em>
					</td><td>
						Path to fdb
					</td></tr><tr><td>
						<em class="parameter"><code>serial</code></em>=<em class="replaceable"><code>FILE</code></em>
					</td><td>
						Path to serial or pty or vc
					</td></tr><tr><td>
						<em class="parameter"><code>localtime</code></em>=<code class="command">no</code> | <code class="command">yes</code>
					</td><td>
						Is RTC set to localtime
					</td></tr><tr><td>
						<em class="parameter"><code>keymap</code></em>=<em class="replaceable"><code>FILE</code></em>
					</td><td>
						Set keyboard layout used
					</td></tr><tr><td>
						<em class="parameter"><code>usb</code></em>=<code class="command">no</code> | <code class="command">yes</code>
					</td><td>
						Emulate USB devices
					</td></tr><tr><td>
						<em class="parameter"><code>usbdevice</code></em>=<em class="replaceable"><code>NAME</code></em>
					</td><td>
						Name of a <code class="systemitem">USB</code> device to add
					</td></tr><tr><td>
						<em class="parameter"><code>stdvga</code></em>=<code class="command">no</code> | <code class="command">yes</code>
					</td><td>
						Use <em class="parameter"><code>std vga</code></em> or <span class="orgname">Cirrus Logic</span>
						 graphics
					</td></tr><tr><td>
						<em class="parameter"><code>isa</code></em>=<code class="command">no</code> | <code class="command">yes</code>
					</td><td>
						Simulate an <code class="systemitem">ISA</code> only system
					</td></tr><tr><td>
						<em class="parameter"><code>boot</code></em>=<em class="replaceable"><code>a|b|c|d</code></em>
					</td><td>
						Default boot device
					</td></tr><tr><td>
						<em class="parameter"><code>nographic</code></em>=<code class="command">no</code> | <code class="command">yes</code>
					</td><td>
						Should device models use graphics?
					</td></tr><tr><td>
						<em class="parameter"><code>soundhw</code></em>=<em class="replaceable"><code>audiodev</code></em>
					</td><td>
						Should device models enable audio device?
					</td></tr><tr><td>
						<em class="parameter"><code>vnc</code></em>
					</td><td>
						Should the device model use VNC?
					</td></tr><tr><td>
						<em class="parameter"><code>vncdisplay</code></em>
					</td><td>
						VNC display to use
					</td></tr><tr><td>
						<em class="parameter"><code>vnclisten</code></em>
					</td><td>
						Address for VNC server to listen on.
					</td></tr><tr><td>
						<em class="parameter"><code>vncunused</code></em>
					</td><td>
						Try to find an unused port for the VNC server. Only valid when vnc=1.
					</td></tr><tr><td>
						<em class="parameter"><code>sdl</code></em>
					</td><td>
						Should the device model use SDL?
					</td></tr><tr><td>
						<em class="parameter"><code>display</code></em>=<em class="replaceable"><code>DISPLAY</code></em>
					</td><td>
						X11 display to use
					</td></tr><tr><td>
						<em class="parameter"><code>xauthority</code></em>=<em class="replaceable"><code>XAUTHORITY</code></em>
					</td><td>
						X11 Authority to use
					</td></tr><tr><td>
						<em class="parameter"><code>uuid</code></em>
					</td><td>
						xenstore UUID (universally unique identifier) to use. One will be randomly generated if this option is not set, just like MAC addresses for virtual network interfaces. This must be a unique value across the entire cluster.
					</td></tr></tbody></table></div><h6>TableÂ 22.2.Â Xen configuration file reference</h6></div><br class="table-break"/><div class="para">
		<a class="xref" href="chap-Virtualization_Guide-Xen_configuration_files.html#tabl-Virtualization_Guide-Xen_configuration_files-Configuration_parameter_default_values" title="TableÂ 22.4.Â Configuration parameter default values">TableÂ 22.4, â€œConfiguration parameter default valuesâ€</a> lists all configuration parameters available, the Python parser function which sets the value and default values. The setter function gives an idea of what the parser does with the values you specify. It reads them as Python values, then feeds them to a setter function to store them. If the value is not valid Python, you get an obscure error message. If the setter rejects your value, you should get a reasonable error message, except it appears to get lost somehow, along with your bogus setting. If the setter accepts, but the value makes no sense, the program proceeds, and you can expect it to fall flat on its face somewhere down the road.
	</div><div class="table" id="tabl-Virtualization_Guide-Xen_configuration_files-Python_functions_which_set_parameter_values"><div class="table-contents"><table summary="Python functions which set parameter values" border="1"><colgroup><col/><col/></colgroup><thead><tr><th>
						Parser function
					</th><th>
						Valid arguments
					</th></tr></thead><tbody><tr><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<div class="para">
							Accepted values:
						</div>
						<div class="para">
							<div class="itemizedlist"><ul><li><div class="para">
										<code class="literal">yes</code>
									</div></li><li><div class="para">
										<code class="literal">y</code>
									</div></li><li><div class="para">
										<code class="literal">no</code>
									</div></li><li><div class="para">
										<code class="literal">yes</code>
									</div></li></ul></div>
						</div>
					</td></tr><tr><td>
						<em class="parameter"><code>set_float</code></em>
					</td><td>
						<div class="para">
							Accepts a floating point number with Python's float(). For example:
						</div>
						<div class="para">
							<div class="itemizedlist"><ul><li><div class="para">
										<code class="literal">3.14</code>
									</div></li><li><div class="para">
										<code class="literal">10.</code>
									</div></li><li><div class="para">
										<code class="literal">.001</code>
									</div></li><li><div class="para">
										<code class="literal">1e100</code>
									</div></li><li><div class="para">
										<code class="literal">3.14e-10</code>
									</div></li></ul></div>
						</div>
					</td></tr><tr><td>
						<em class="parameter"><code>set_int</code></em>
					</td><td>
						<div class="para">
							Accepts an integer with Python's int().
						</div>
					</td></tr><tr><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<div class="para">
							accepts any Python value.
						</div>
					</td></tr><tr><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<div class="para">
							accepts any Python value, and appends it to the previous value which is stored in an array.
						</div>
					</td></tr></tbody></table></div><h6>TableÂ 22.3.Â Python functions which set parameter values</h6></div><br class="table-break"/><div class="table" id="tabl-Virtualization_Guide-Xen_configuration_files-Configuration_parameter_default_values"><div class="table-contents"><table summary="Configuration parameter default values" border="1"><colgroup><col/><col/><col/></colgroup><thead><tr><th>
						Parameter
					</th><th>
						Parser function
					</th><th>
						Default value
					</th></tr></thead><tbody><tr><td>
						<em class="parameter"><code>name</code></em>
					</td><td>
						<em class="parameter"><code>setter</code></em>
					</td><td>
						<em class="replaceable"><code>default value</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vncpasswd</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vncviewer</code></em>
					</td><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vncconsole</code></em>
					</td><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>name</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>bootloader</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>bootargs</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>bootentry</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>kernel</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>ramdisk</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>features</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>builder</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>'linux'</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>memory</code></em>
					</td><td>
						<em class="parameter"><code>set_int</code></em>
					</td><td>
						<em class="replaceable"><code>128</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>maxmem</code></em>
					</td><td>
						<em class="parameter"><code>set_int</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>shadow_memory</code></em>
					</td><td>
						<em class="parameter"><code>set_int</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>cpu</code></em>
					</td><td>
						<em class="parameter"><code>set_int</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>cpus</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>pae</code></em>
					</td><td>
						<em class="parameter"><code>set_int</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>acpi</code></em>
					</td><td>
						<em class="parameter"><code>set_int</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>apic</code></em>
					</td><td>
						<em class="parameter"><code>set_int</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vcpus</code></em>
					</td><td>
						<em class="parameter"><code>set_int</code></em>
					</td><td>
						<em class="replaceable"><code>1</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>cpu_weight</code></em>
					</td><td>
						<em class="parameter"><code>set_float</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>restart</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>on_poweroff</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>on_reboot</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>on_crash</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>blkif</code></em>
					</td><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>netif</code></em>
					</td><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>tpmif</code></em>
					</td><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>disk</code></em>
					</td><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<em class="replaceable"><code>[]</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>pci</code></em>
					</td><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<em class="replaceable"><code>[]</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>ioports</code></em>
					</td><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<em class="replaceable"><code>[]</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>irq</code></em>
					</td><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<em class="replaceable"><code>[]</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>usbport</code></em>
					</td><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<em class="replaceable"><code>[]</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vfb</code></em>
					</td><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<em class="replaceable"><code>[]</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vif</code></em>
					</td><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<em class="replaceable"><code>[]</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vtpm</code></em>
					</td><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<em class="replaceable"><code>[]</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>access_control</code></em>
					</td><td>
						<em class="parameter"><code>append_value</code></em>
					</td><td>
						<em class="replaceable"><code>[]</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>nics</code></em>
					</td><td>
						<em class="parameter"><code>set_int</code></em>
					</td><td>
						<em class="replaceable"><code>-1</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>root</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>extra</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>ip</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>gateway</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>netmask</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>hostname</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>interface</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>"eth0"</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>dhcp</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>'off'</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>nfs_server</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>nfs_root</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>device_model</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>fda</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>fdb</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>serial</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>localtime</code></em>
					</td><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>keymap</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>usb</code></em>
					</td><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>usbdevice</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>stdvga</code></em>
					</td><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>isa</code></em>
					</td><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>boot</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>'c'</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>nographic</code></em>
					</td><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<em class="replaceable"><code>0</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>soundhw</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>''</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vnc</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vncdisplay</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vnclisten</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>vncunused</code></em>
					</td><td>
						<em class="parameter"><code>set_bool</code></em>
					</td><td>
						<em class="replaceable"><code>1</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>sdl</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>display</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>xauthority</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr><tr><td>
						<em class="parameter"><code>uuid</code></em>
					</td><td>
						<em class="parameter"><code>set_value</code></em>
					</td><td>
						<em class="replaceable"><code>None</code></em>
					</td></tr></tbody></table></div><h6>TableÂ 22.4.Â Configuration parameter default values</h6></div><br class="table-break"/></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters.html"><strong>Prev</strong>ChapterÂ 21.Â Configuring the Xen kernel boot param...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Tips_and_Tricks.html"><strong>Next</strong>PartÂ V.Â Tips and Tricks</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Xen_live_migration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 14.Â Xen live migration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Administration.html" title="PartÂ III.Â Administration"/><link rel="prev" href="chap-Virtualization_Guide-KVM_guest_timing_management.html" title="ChapterÂ 13.Â KVM guest timing management"/><link rel="next" href="sect-Virtualization_Guide-Xen_live_migration-Configuring_guest_live_migration.html" title="14.2.Â Configuring guest live migration"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Co
 ntent/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-KVM_guest_timing_management.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Xen_live_migration-Configuring_guest_live_migration.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Xen_live_migration">ChapterÂ 14.Â Xen live migration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Xen_live_migration.html#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.html">14.2. Configuring guest live migration</a></span></dt></dl></div><div class="para
 ">
		The Xen hypervisor supports <a class="firstterm" href="go01.html#glos-Virtualization_Guide-Migration"><em class="firstterm">migration</em></a> for para-virtualized guests and fully virtualized guests.  Migration can be performed offline or live.
	</div><div class="itemizedlist"><ul><li><div class="para">
				Offline migration suspends the virtualized guest on the original host, transfers it to the destination host and then resumes it once the guest is fully transferred. Offline migration uses the <code class="command">virsh migrate</code> command.
			</div><pre class="screen"># virsh migrate <em class="replaceable"><code>GuestName</code></em> <em class="replaceable"><code>libvirtURI</code></em>
</pre></li><li><div class="para">
				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 is 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">
				Live migration uses the <code class="command">--live</code> option for the <code class="command">virsh migrate</code> command.
			</div><pre class="screen"># virsh migrate--live <em class="replaceable"><code>GuestName</code></em> <em class="replaceable"><code>libvirtURI</code></em>
</pre></li></ul></div><div class="para">
		To enable migration with Xen a few changes must be made to the <code class="filename">/etc/xen/xend-config.sxp</code> configuration file. By default, migration is disabled as migration can be a potential security hazard if incorrectly configured. Opening the migration port can allow an unauthorized host to initiate a migration or connect to the migration ports. Authentication and authorization are not configured for migration requests and the only control mechanism is based on hostnames and IP addresses. Special care should be taken to ensure the migration port is not accessible to unauthorized hosts.
	</div><div class="important"><h2>Virtualization migration security</h2><div class="para">
			IP address and hostname filters only offer minimal security. Both of these attributes can be forged if the attacker knows the address or hostname of the migration client. The best method for securing migration is to isolate the network from external and unauthorized internal connections.
		</div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Xen_live_migration-Enabling_migration">Enabling migration</h5>
			Modify the following entries in <code class="filename">/etc/xen/xend-config.sxp</code> to enable migration. Modify the values, when necessary, and remove the comments (the <code class="command">#</code> symbol) preceding the following parameters:
		</div><div class="variablelist"><dl><dt><span class="term"><code class="computeroutput">(xend-relocation-server yes)</code></span></dt><dd><div class="para">
					The default value, which disables migration, is <code class="computeroutput">no</code>. Change the value of <code class="command">xend-relocation-server</code> to yes to enable migration.
				</div></dd><dt><span class="term"><code class="computeroutput">(xend-relocation-port 8002)</code></span></dt><dd><div class="para">
					The parameter, <code class="computeroutput">(xend-relocation-port)</code>, specifies the port <code class="systemitem">xend</code> should use for the relocation interface, if <code class="computeroutput">xend-relocation-server</code> is set to <code class="computeroutput">yes</code>
				</div><div class="para">
					The default value of this variable should work for most installations. If you change the value make sure you are using an unused port on the relocation server.
				</div><div class="para">
					The port set by the <code class="command">xend-relocation-port</code> parameter must be open on both systems.
				</div></dd><dt><span class="term"><code class="computeroutput">(xend-relocation-address '')</code></span></dt><dd><div class="para">
					<code class="computeroutput">(xend-relocation-address)</code>is the address the <code class="systemitem">xend</code> listens for migration commands on the <code class="filename">relocation-socket</code> connection if <code class="computeroutput">xend-relocation-server</code> is set.
				</div><div class="para">
					The default is listen on all active interfaces, the parameter can restrict the relocation server to only listen to a specific interface. The default value in <code class="filename">/etc/xen/xend-config.sxp</code> is an empty string(<em class="parameter"><code>''</code></em>). This value should be replaced with a single, valid IP address. For example:
				</div><pre class="screen">(xend-relocation-address '10.0.0.1')
</pre></dd><dt><span class="term"><code class="computeroutput">(xend-relocation-hosts-allow '')</code></span></dt><dd><div class="para">
					The <code class="computeroutput">(xend-relocation-hosts-allow 'hosts')</code> parameter controls which hostnames can communicate on the relocation port.
				</div><div class="para">
					Unless you are using SSH or TLS, the guest's virtual memory is transferred in raw form without encryption of the communication. Modify the <code class="computeroutput">xend-relocation-hosts-allow</code> option to restrict access to the migration server.
				</div><div class="para">
					If the value is empty, as denoted in the example above by an empty string surrounded by single quotes, then all connections are allowed. This assumes the connection arrives on a port and interface which the relocation server listens on, see also <code class="computeroutput">xend-relocation-port</code> and <code class="computeroutput">xend-relocation-address</code> above).
				</div><div class="para">
					Otherwise, the <code class="computeroutput">(xend-relocation-hosts-allow)</code> parameter should be a sequence of regular expressions separated by spaces. Any host with a fully-qualified domain name or an IP address which matches one of these regular expressions will be accepted.
				</div><div class="para">
					An example of a <code class="computeroutput">(xend-relocation-hosts-allow)</code> attribute:
				</div><pre class="screen">(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
</pre></dd></dl></div><div class="para">
		After you have configured the parameters in your configuration file, restart the Xen service.
	</div><pre class="screen"># service xend restart
</pre><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Xen_live_migration-A_live_migration_example">14.1.Â A live migration example</h2></div></div></div><div class="para">
			Below is an example of how to setup a simple environment for live migration. This configuration is using <span class="application"><strong>NFS</strong></span> for the shared storage. <span class="application"><strong>NFS</strong></span> is suitable for demonstration environments but for a production environment a more robust shared storage configuration using Fibre Channel or iSCSI and <span class="application"><strong>GFS</strong></span> is recommended.
		</div><div class="para">
			The configuration below consists of two servers (<code class="computeroutput">et-virt07</code> and <code class="computeroutput">et-virt08</code>), both of them are using <code class="command">eth1</code> as their default network interface hence they are using <code class="command">xenbr1</code> as their Xen networking bridge. We are using a locally attached SCSI disk (<code class="filename">/dev/sdb</code>) on <code class="computeroutput">et-virt07</code> for shared storage using <span class="application"><strong>NFS</strong></span>.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-A_live_migration_example-Setup_for_live_migration">Setup for live migration</h5>
				Create and mount the directory used for the migration:
			</div><pre class="screen"># mkdir /var/lib/libvirt/images
# mount /dev/sdb /var/lib/libvirt/images
</pre><div class="warning"><h2>Important</h2><div class="para">
				Ensure the directory is exported with the correct options. If you are exporting the default directory <code class="filename">/var/lib/libvirt/images/</code> make sure you <span class="emphasis"><em>only</em></span> export <code class="filename">/var/lib/libvirt/images/</code> and <span class="emphasis"><em>not</em></span><code class="filename">/var/lib/xen/</code> as this directory is used by the <code class="systemitem">xend</code> daemon and other tools. Sharing <code class="filename">/var/lib/xen/</code> will cause unpredictable behavior.
			</div></div><pre class="screen"># cat /etc/exports
/var/lib/libvirt/images  *(rw,async,no_root_squash)
</pre><div class="para">
			Verify it is exported via <span class="application"><strong>NFS</strong></span>:
		</div><pre class="screen"># showmount -e et-virt07
Export list for et-virt07:
/var/lib/libvirt/images *
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-A_live_migration_example-Install_the_guest">Install the guest</h5>
				The install command in the example used for installing the guest:
			</div><pre class="screen"># virt-install -p -f /var/lib/libvirt/images/testvm1.dsk -s 5 -n\
testvm1 --vnc -r 1024 -l http://porkchop.devel.redhat.com/rel-eng/CentOS5-\
Server-20070105.0/4.92/x86_64/os/ -b xenbr1
</pre><div class="para">
			For step by step installation instructions, refer to <a class="xref" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html" title="ChapterÂ 3.Â Guest operating system installation procedures">ChapterÂ 3, <i>Guest operating system installation procedures</i></a>
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-A_live_migration_example-Verify_environment_for_migration">Verify environment for migration</h5>
				Make sure the virtualized network bridges are configured correctly and have the same name on both hosts:
			</div><pre class="screen">[et-virt08 ~]# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr1          8000.feffffffffff       no              peth1
vif0.1
</pre><pre class="screen">[et-virt07 ~]# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr1          8000.feffffffffff       no              peth1
vif0.1
</pre><div class="para">
			Verify the relocation parameters are configured on both hosts:
		</div><pre class="screen">[et-virt07 ~]# grep xend-relocation /etc/xen/xend-config.sxp |grep -v '#'
(xend-relocation-server yes)
(xend-relocation-port 8002)
(xend-relocation-address '')
(xend-relocation-hosts-allow '')
</pre><pre class="screen">[et-virt08 ~]# grep xend-relocation /etc/xen/xend-config.sxp |grep -v '#'
(xend-relocation-server yes)
(xend-relocation-port 8002)
(xend-relocation-address '')
(xend-relocation-hosts-allow '')
</pre><div class="para">
			Make sure the relocation server has started and is listening on the dedicated port for Xen migrations (8002):
		</div><pre class="screen">[et-virt07 ~]# lsof -i :8002
COMMAND  PID  USER   FD   TYPE  DEVICE SIZE NODE NAME
python 3445 root 14u IPv4 10223 TCP *:teradataordbms (LISTEN)
</pre><pre class="screen">[et-virt08 ~]# lsof -i :8002
COMMAND  PID USER   FD   TYPE DEVICE SIZE NODE NAME
python 3252 root 14u IPv4 10901 TCP *:teradataordbms (LISTEN)
</pre><div class="para">
			Verify the NFS directory has been mounted on the other host and you can see and access the virtual machine image and file system:
		</div><pre class="screen">[et-virt08 ~]# df /var/lib/libvirt/images
Filesystem           1K-blocks      Used Available Use% Mounted on
et-virt07:/var/lib/libvirt/images    70562400   2379712  64598336   4% /var/lib/libvirt/images
</pre><pre class="screen">[et-virt08 ~]# file /var/lib/libvirt/images/testvm1.dsk 
/var/lib/libvirt/images/testvm1.dsk: x86 boot sector; partition 1: ID=0x83,
active, starthead 1, startsector 63, 208782 sectors; partition 2: ID=0x8e, 
starthead 0, startsector 208845, 10265535 sectors, code offset 0x48
</pre><pre class="screen">[et-virt08 ~]# touch /var/lib/libvirt/images/foo
[et-virt08 ~]# rm -f /var/lib/libvirt/images/foo
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-A_live_migration_example-Verification_of_save_and_restore_on_local_host">Verification of save and restore on local host</h5>
				Start up the virtual machine (if it has not yet):
			</div><pre class="screen">[et-virt07 ~]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
</pre><pre class="screen">[et-virt07 ~]# virsh start testvm1
Domain testvm1 started
</pre><div class="para">
			Verify the virtual machine is running:
		</div><pre class="screen">[et-virt07 ~]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
testvm1        blocked
</pre><div class="para">
			Save the virtual machine on the local host:
		</div><pre class="screen">[et-virt07 images]# time virsh save testvm1 testvm1.sav
real    0m15.744s
user    0m0.188s
sys     0m0.044s
</pre><pre class="screen">[et-virt07 images]# ls -lrt testvm1.sav
-rwxr-xr-x 1 root root 1075657716 Jan 12 06:46 testvm1.sav
</pre><pre class="screen">[et-virt07 images]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
</pre><div class="para">
			Restore the virtual machine on the local host:
		</div><pre class="screen">[et-virt07 images]# virsh restore testvm1.sav
</pre><pre class="screen">[et-virt07 images]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
testvm1        blocked
</pre><div class="para">
			Initiate the live migration to <code class="computeroutput">et-virt08</code>. in the example below <code class="computeroutput">et-virt07</code> is the hostname you are migrating to and <domain-id> must be replaced with a guest domain available to the host system.
		</div><pre class="screen">[et-virt08 ~]# xm migrate --live <domain-id> et-virt07
</pre><div class="para">
			Verify the virtual machine has been shut down on <code class="computeroutput">et-virt07</code>
		</div><pre class="screen">[et-virt07 ~]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
</pre><div class="para">
			Verify the virtual machine has been migrated to <code class="computeroutput">et-virt08</code>:
		</div><pre class="screen">[et-virt08 ~]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
testvm1        blocked
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-A_live_migration_example-Testing_the_progress_and_initiating_the_live_migration">Testing the progress and initiating the live migration</h5>
				Create the following script inside the virtual machine to log date and hostname during the migration. This script performs I/O tasks on the guest's file system.
			</div><pre class="screen">#!/bin/bash

while true
do
touch /var/tmp/$$.log
echo `hostname` >>  /var/tmp/$$.log
	echo `date`     >>  /var/tmp/$$.log
	cat  /var/tmp/$$.log
	df /var/tmp
	ls -l  /var/tmp/$$.log
	sleep 3
	done
</pre><div class="para">
			Remember, that script is only for testing purposes and unnecessary for a live migration in a production environment.
		</div><div class="para">
			Verify the virtual machine is running on et-virt08 before we try to migrate it to <code class="computeroutput">et-virt07</code>:
		</div><pre class="screen">[et-virt08 ~]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
testvm1        blocked
</pre><div class="para">
			Initiate a live migration to <code class="computeroutput">et-virt07</code>. You can add the <code class="command">time</code> command to see how long the migration takes:
		</div><pre class="screen">[et-virt08 ~]# xm migrate --live testvm1 et-virt07
</pre><div class="para">
			run the script inside the guest:
		</div><pre class="screen"># ./doit
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:26:27 EST 2007
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2983664   2043120    786536  73% /
-rw-r--r-- 1 root root 62 Jan 12 02:26 /var/tmp/2279.log
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:26:27 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:26:30 EST 2007
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2983664   2043120    786536  73% /
-rw-r--r-- 1 root root 124 Jan 12 02:26 /var/tmp/2279.log
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:26:27 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:26:30 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:26:33 EST 2007
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2983664   2043120    786536  73% /
-rw-r--r-- 1 root root 186 Jan 12 02:26 /var/tmp/2279.log
Fri Jan 12 02:26:45 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:26:48 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:26:51 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:54:57 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:55:00 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:55:03 EST 2007
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2983664   2043120    786536  73% /
-rw-r--r-- 1 root root 744 Jan 12 06:55 /var/tmp/2279.log
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:26:27 EST 2007
</pre><div class="para">
			Verify the virtual machine has been shut down on <code class="computeroutput">et-virt08</code>:
		</div><pre class="screen">[et-virt08 ~]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
</pre><div class="para">
			Verify the virtual machine has started up on <code class="computeroutput">et-virt07</code>:
		</div><pre class="screen">[et-virt07 images]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
testvm1        blocked
</pre><div class="para">
			Run through another cycle migrating from <code class="computeroutput">et-virt07</code> to <code class="computeroutput">et-virt08</code>. Initiate a migration from <code class="computeroutput">et-virt07</code> to <code class="computeroutput">et-virt08</code>:
		</div><pre class="screen">[et-virt07 images]# xm migrate --live testvm1 et-virt08
</pre><div class="para">
			Verify the virtual machine has been shut down:
		</div><pre class="screen">[et-virt07 images]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
</pre><div class="para">
			Before initiating the migration start the simple script in the guest and note the change in time when migrating the guest:
		</div><pre class="screen"># ./doit
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:53 EST 2007
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2983664   2043120    786536  73% /
-rw-r--r-- 1 root root 62 Jan 12 06:57 /var/tmp/2418.log
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:53 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:56 EST 2007
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2983664   2043120    786536  73% /
-rw-r--r-- 1 root root 124 Jan 12 06:57 /var/tmp/2418.log
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:53 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:56 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:58:00 EST 2007
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2983664   2043120    786536  73% /
-rw-r--r-- 1 root root 186 Jan 12 06:57 /var/tmp/2418.log
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:53 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:56 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:58:00 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:30:00 EST 2007
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2983664   2043120    786536  73% /
-rw-r--r-- 1 root root 248 Jan 12 02:30 /var/tmp/2418.log
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:53 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:56 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:58:00 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:30:00 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:30:03 EST 2007
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2983664   2043120    786536  73% /
-rw-r--r-- 1 root root 310 Jan 12 02:30 /var/tmp/2418.log
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:53 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:57:56 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 06:58:00 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:30:00 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:30:03 EST 2007
dhcp78-218.lab.boston.redhat.com
Fri Jan 12 02:30:06 EST 2007
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2983664   2043120    786536  73% /
-rw-r--r-- 1 root root 372 Jan 12 02:30 /var/tmp/2418.log
</pre><div class="para">
			After the migration command completes on <code class="computeroutput">et-virt07</code> verify on <code class="computeroutput">et-virt08</code> that the virtual machine has started:
		</div><pre class="screen">[et-virt08 ~]# virsh list
 Id Name                 State
----------------------------------
Domain-0                 running
testvm1        blocked
</pre><div class="para">
			and run another cycle:
		</div><pre class="screen">[et-virt08 ~]# time virsh migrate --live testvm1 et-virt07
real    0m10.378s
user    0m0.068s
sys     0m0.052s
</pre><div class="para">
			At this point you have successfully performed an offline and a live migration test.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-KVM_guest_timing_management.html"><strong>Prev</strong>ChapterÂ 13.Â KVM guest timing management</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Xen_live_migration-Configuring_guest_live_migration.html"><strong>Next</strong>14.2.Â Configuring guest live migration</a></li></ul></body></html>

--- NEW FILE chap-Virtualization_Guide-Xen_networking.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>ChapterÂ 9.Â Xen networking</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="part-Virtualization_Guide-Configuration.html" title="PartÂ II.Â Configuration"/><link rel="prev" href="sect-Virtualization_Guide-Network_Configuration-Bridged_networking_with_libvirt.html" title="8.2.Â Bridged networking with libvirt"/><link rel="next" href="sect-Virtualization_Guide-Xen_networking-Laptop_network_configuration.html" title="9.2.Â Laptop network configuration"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_C
 ontent/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Xen_networking-Laptop_network_configuration.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="chap-Virtualization_Guide-Xen_networking">ChapterÂ 9.Â Xen networking</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Xen_networking.html#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_configurat
 ion.html">9.2. Laptop network configuration</a></span></dt></dl></div><div class="para">
		This chapter covers special topics for networking and network configuration with the Xen hypervisor.
	</div><div class="para">
		Most guest network configuration occurs during the guest initialization and installation process. To learn about configuring networking during the guest installation process, read the relevant sections of the installation process, <a class="xref" href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html" title="ChapterÂ 2.Â Virtualized guest installation overview">ChapterÂ 2, <i>Virtualized guest installation overview</i></a>.
	</div><div class="para">
		Network configuration is also covered in the tool specific reference chapters for <code class="command">virsh</code> (<a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html" title="ChapterÂ 18.Â Managing guests with virsh">ChapterÂ 18, <i>Managing guests with virsh</i></a>) and <code class="command">virt-manager</code> (<a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)">ChapterÂ 19, <i>Managing guests with the Virtual Machine Manager (virt-manager)</i></a>). Those chapters provide a detailed description of the networking configuration tasks using both tools.
	</div><div class="note"><h2>Tip</h2><div class="para">
			Using para-virtualized network drivers improves performance on fully virtualized Linux guests. <a class="xref" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html" title="ChapterÂ 10.Â Xen Para-virtualized Drivers">ChapterÂ 10, <i>Xen Para-virtualized Drivers</i></a> explains how to utilize para-virtualized network drivers.
		</div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></div></div><div class="para">
			Process to setup network bridges (with the Xen hypervisor):
		</div><div class="procedure"><ol class="1"><li><div class="para">
					Configure another network interface using either the <code class="command">system-config-network</code> application. Alternatively, create a new configuration file named <code class="filename">ifcfg-ethX</code> in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory where <em class="parameter"><code>X</code></em> is any number not already in use. Below is an example configuration file for a second network interface called <code class="computeroutput">eth1</code>
				</div><pre class="screen">$ cat /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
BOOTPROTO=static
ONBOOT=yes
USERCTL=no
IPV6INIT=no
PEERDNS=yes
TYPE=Ethernet
NETMASK=255.255.255.0
IPADDR=10.1.1.1
GATEWAY=10.1.1.254
ARP=yes
</pre></li><li><div class="para">
					Copy the file, <code class="filename">/etc/xen/scripts/network-bridge</code>, to <code class="filename">/etc/xen/scripts/network-bridge.xen</code>.
				</div></li><li><div class="para">
					Comment out any existing network scripts in <code class="filename">/etc/xen/xend-config.sxp</code> and add the line <em class="parameter"><code>(network-xen-multi-bridge)</code></em>.
				</div></li><li><div class="para">
					Create a custom script to create multiple network bridges. A sample scripts is below, this example script will create two Xen network bridges (xenbr0 and xenbr1) one will be attached to eth1 and the other one to eth0. If you want to create additional bridges just follow the example in the script and copy/paste the lines accordingly:
				</div><pre class="screen">#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
	$script start vifnum=1 bridge=xenbr1 netdev=eth1
	$script start vifnum=0 bridge=xenbr0 netdev=eth0
	;;
stop)
	$script stop vifnum=1 bridge=xenbr1 netdev=eth1
	$script stop vifnum=0 bridge=xenbr0 netdev=eth0
	;;
status)
	$script status vifnum=1 bridge=xenbr1 netdev=eth1
	$script status vifnum=0 bridge=xenbr0 netdev=eth0
	;;
*)
	echo 'Unknown command: ' ${OP}
	echo 'Valid commands are: start, stop, status'
	exit 1
esac
</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Prev</strong>8.2.Â Bridged networking with libvirt</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Xen_networking-Laptop_network_configuration.html"><strong>Next</strong>9.2.Â Laptop network configuration</a></li></ul></body></html>

--- NEW FILE go01.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>Glossary</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="sect-Virtualization_Guide-Additional_resources-Installed_documentation.html" title="B.2.Â Installed documentation"/><link rel="next" href="appe-Virtualization_Guide-Revision_History.html" title="AppendixÂ C.Â Revision History"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous">
 <a accesskey="p" href="sect-Virtualization_Guide-Additional_resources-Installed_documentation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-Virtualization_Guide-Revision_History.html"><strong>Next</strong></a></li></ul><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="go01.html#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="go01.html#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="go01.html#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="go01.html#glos-Virtualization_Guide-domU" title="domU">domU</a> and <a class="xref" href="go01.html#glos-Virtualization_Guide-Domains" title="Domains">Domains</a> are both domains. Domains run on the <a class="xref" href="go01.html#glos-Virtualization_Guide-Hypervisor" title="Hypervisor">Hypervisor</a>. The term domains has a similar meaning to <a class="xref" href="go01.html#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="go01.html#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="go01.html#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="go01.html#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="go01.html#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="go01.html#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="go01.html#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="go01.html#glos-Virtualization_Guide-Fully_virtualized" title="Fully virtualized">Fully virtualized</a> and <a class="xref" href="go01.html#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="go01.html#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="go01.html#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="go01.html#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="go01.html#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="go01.html#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="go01.html#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><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Additional_resources-Installed_documentation.html"><strong>Prev</strong>B.2.Â Installed documentation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="appe-Virtualization_Guide-Revision_History.html"><strong>Next</strong>AppendixÂ C.Â Revision History</a></li></ul></body></html>

--- NEW FILE index.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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="Fedora-Virtualization_Guide-12-en-US-1-2"/><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."/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="next" href="pref-Virtualization_Guide-Preface.html" title="Preface"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"/><li 
 class="next"><a accesskey="n" href="pref-Virtualization_Guide-Preface.html"><strong>Next</strong></a></li></ul><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.html">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Virtualization_Guide-Preface.html#sect-Virtualization_Guide-About_this_book">1. About this book</a></span></dt><dt><span class="section"><a href="pr01s02.html">2. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="pr01s02.html#d0e96">2.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="pr01s02s02.html">2.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="pr01s02s03.html">2.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="pr01s03.html">3. We Need Feedback!</a></span></dt></dl></dd><dt><span class="part"><a href="part-Virtualization_Guide-Installation.html">I. Installation</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Installing_
 the_virtualization_packages.html">1. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html#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.html">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.html">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.html
 ">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.html">2. Virtualized guest installation overview</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html#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.html">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.html">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.html">3. Guest operating system installation procedures</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html#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.html">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.html">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.html">3.4. Installing Windows Server 2003 as a fully virtualized gu
 est</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest.html">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.html">II. Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Virtualized_block_devices.html">4. Virtualized block devices</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Virtualized_block_devices.html#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.html">4.2. Adding storage devices to guests</a></span></dt><dt><span class="section"><a href="sect-Vir
 tualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html">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.html">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_storage_and_virtualization.html">5. Shared storage and virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html#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.html">5.2. Using NFS for storing guests</a></span></dt><dt><span class="section"><a href="sect-Virtualizat
 ion_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests.html">5.3. Using GFS2 for storing guests</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-Server_best_practices.html">6. Server best practices</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-Security_for_virtualization.html">7. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Security_for_virtualization.html#sect-Virtualization_Guide-Security_for_virtualization-SELinux_and_virtualization">7.1. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html">7.2. SELinux considerations</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-Network_Configuration.html">8. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-
 Virtualization_Guide-Network_Configuration.html#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.html">8.2. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-Xen_networking.html">9. Xen networking</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Xen_networking.html#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.html">9.2. Laptop network configuration</a></span></dt></dl></dd><dt><span cla
 ss="chapter"><a href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html">10. Xen Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html#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.html">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.html#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.html">10.2.2. Installation and Configuratio
 n 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.html">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.html">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.html">10.3. Para-virtualized Network Driver Configuration</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html">10.4. Additional Para-virtualized Hardware Configuration</a></span></d
 t><dd><dl><dt><span class="section"><a href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html#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.html">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.html">11. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html#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-Virtu
 alization_Guide-Administration.html">III. Administration</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Managing_guests_with_xend.html">12. Managing guests with xend</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-KVM_guest_timing_management.html">13. KVM guest timing management</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-Xen_live_migration.html">14. Xen live migration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Xen_live_migration.html#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.html">14.2. Configuring guest live migration</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-KVM_live_migration.html">15. KVM live migration</a>
 </span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-KVM_live_migration.html#sect-Virtualization_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.html">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.html">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.html">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.html">16. Remote management of virtualized guests</a></span></dt><dd><dl><dt><span class="section"><a href="chap-V
 irtualization_Guide-Remote_management_of_virtualized_guests.html#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.html">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.html">16.3. Transport modes</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="part-Virtualization_Guide-Virtualization_Reference_Guide.html">IV. Virtualization Reference Guide</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Virtualization_tools.html">17. Virtualization tools</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-Managing_guests_with_virsh.html">18. Managing guests with virs
 h</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html">19. Managing guests with the Virtual Machine Manager (virt-manager)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html#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.html">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_.html">19.3. The Virtual Machine Manager details window </a></sp
 an></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html">19.4. Virtual Machine graphical console </a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager.html">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_.html">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.html">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.html">19.8. Status mon
 itoring</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers.html">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-Displaying_a_guests_status_.html">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_.html">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.html">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_.html">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.html">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-Creating_a_virtual_network.html">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.html">20. The xm command quick reference</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters.html">21. Configuring the Xen kernel boot parameters</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-Xen_configuration_files.html">22. Xen configuration files</a></span></dt></dl></dd><dt><span class="part"><a href="part-Virtualization_Guide-Ti
 ps_and_Tricks.html">V. Tips and Tricks</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Tips_and_tricks.html">23. Tips and tricks</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Tips_and_tricks.html#sect-Virtualization_Guide-Tips_and_tricks-Automatically_starting_guests">23.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html">23.2. Changing between the KVM and Xen hypervisors</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html#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.html">23.2.2. KVM to Xen</a></sp
 an></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img.html">23.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html">23.4. Overcommitting with KVM</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html">23.5. Modifying /etc/grub.conf</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html">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.html">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.html">23.8. Generating a new unique MAC address</a></spa
 n></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest.html">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.html">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.html">23.11. Modifying the Xen hypervisor</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd.html">23.12. Very Secure ftpd</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html">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.html">23.14. Disable SMART disk monito
 ring for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files.html">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.html">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.html">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.html">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.html">24. Creating custom libvirt scripts</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Gui
 de-Creating_custom_libvirt_scripts.html#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.html">VI. Troubleshooting</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Troubleshooting_Xen.html">25. Troubleshooting Xen</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Troubleshooting_Xen.html#sect-Virtualization_Guide-Troubleshooting_Xen-Debugging_and_troubleshooting_Xen">25.1. Debugging and troubleshooting Xen</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html">25.2. Log files overview</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html">25.3. Log file descriptions</a></
 span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html">25.4. Important directory locations</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs.html">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.html">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.html">25.7. Para-virtualized guest console access</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html">25.8. Fully virtualized guest console access</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Acce
 ssing_data_on_guest_disk_image.html">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.html">25.10. Common Xen problems</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html">25.11. Guest creation errors</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html">25.12. Troubleshooting with serial consoles</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html#sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_for_Xen">25.12.1. Serial console output for Xen</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_par
 a_virtualized_guests.html">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.html">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.html">25.13. Guest configuration files</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html">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.html">25.15. The layout of the log directories</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-Troubleshooting.html">26. Troubleshooting</a></span></dt><d
 d><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Troubleshooting.html#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.html">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.html">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.html">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_shortage.html">26.5. Failed domain creation ca
 used by a memory shortage</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error.html">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.html">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.html">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.html">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.html">26.10. Microcode error during guest boot</a></spa
 n></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting-Wrong_bridge_configured_on_the_guest_causing_hot_plug_script_timeouts.html">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.html">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.html">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.html">27. Troubleshooting the Xen para-virtualized drivers</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtu
 alization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html#sect-Virtualization_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.html">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.html">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.html">
 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.html">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_.html">A. Xen system architecture </a></span></dt><dt><span class="appendix"><a href="appe-Virtualization_Guide-Additional_resources.html">B. Additional resources</a></span></dt><dd><dl><dt><span class="section"><a href="appe-Virtualization_Guide-Additional_resources.html#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.html">B.2. Installed documentation</a></span></dt></
 dl></dd><dt><span class="glossary"><a href="go01.html">Glossary</a></span></dt><dt><span class="appendix"><a href="appe-Virtualization_Guide-Revision_History.html">C. Revision History</a></span></dt><dt><span class="appendix"><a href="appe-Virtualization_Guide-Colophon.html">D. Colophon</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"/><li class="next"><a accesskey="n" href="pref-Virtualization_Guide-Preface.html"><strong>Next</strong>Preface</a></li></ul></body></html>

--- NEW FILE part-Virtualization_Guide-Administration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>PartÂ III.Â Administration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html" title="ChapterÂ 11.Â KVM Para-virtualized Drivers"/><link rel="next" href="chap-Virtualization_Guide-Managing_guests_with_xend.html" title="ChapterÂ 12.Â Managing guests with xend"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul cla
 ss="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Managing_guests_with_xend.html"><strong>Next</strong></a></li></ul><div class="part" lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="part-Virtualization_Guide-Administration">PartÂ III.Â Administration</h1></div></div></div><div class="partintro" lang="en-US"><div><div><div><h1 id="part-Virtualization_Guide-Administration-Administering_virtualized_systems" class="title">Administering virtualized systems</h1></div></div></div><div class="para">
				These chapters contain information for administering host and virtualized guests using tools included in Fedora.
			</div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Managing_guests_with_xend.html">12. Managing guests with xend</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-KVM_guest_timing_management.html">13. KVM guest timing management</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-Xen_live_migration.html">14. Xen live migration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Xen_live_migration.html#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.html">14.2. Configuring guest live migration</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-KVM_live_migration.html">15. KVM live migration</a></span></dt><dd><dl>
 <dt><span class="section"><a href="chap-Virtualization_Guide-KVM_live_migration.html#sect-Virtualization_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.html">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.html">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.html">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.html">16. Remote management of virtualized guests</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-
 Remote_management_of_virtualized_guests.html#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.html">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.html">16.3. Transport modes</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html"><strong>Prev</strong>ChapterÂ 11.Â KVM Para-virtualized Drivers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guid
 e-Managing_guests_with_xend.html"><strong>Next</strong>ChapterÂ 12.Â Managing guests with xend</a></li></ul></body></html>

--- NEW FILE part-Virtualization_Guide-Configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>PartÂ II.Â Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest.html" title="3.5.Â Installing Windows Server 2008 as a fully virtualized guest"/><link rel="next" href="chap-Virtualization_Guide-Virtualized_block_devices.html" title="ChapterÂ 4.Â Virtualized block devices"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_r
 ight.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Virtualized_block_devices.html"><strong>Next</strong></a></li></ul><div class="part" lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="part-Virtualization_Guide-Configuration">PartÂ II.Â Configuration</h1></div></div></div><div class="partintro" lang="en-US"><div><div><div><h1 id="part-Virtualization_Guide-Configuration-Configuring_Virtualization_in_Linux" class="title">Configuring Virtualization in Fedora</h1></div></div></div><div class="para">
				These chapters cover configuration procedures for various advanced virtualization tasks. These tasks include adding network and storage devices, enhancing security, improving performance, and using the para-virtualized drivers on fully virtualized guests.
			</div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Virtualized_block_devices.html">4. Virtualized block devices</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Virtualized_block_devices.html#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.html">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.html">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.html">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_storage_and_virtualization.html">5. Shared storage and virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html#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.html">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.html">5.3. Using GFS2 for storing guests</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-Server_best_practices.html">6. Server best practices</a></span></dt><dt><span class="chapter"><a href="c
 hap-Virtualization_Guide-Security_for_virtualization.html">7. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Security_for_virtualization.html#sect-Virtualization_Guide-Security_for_virtualization-SELinux_and_virtualization">7.1. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html">7.2. SELinux considerations</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-Network_Configuration.html">8. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Network_Configuration.html#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_netwo
 rking_with_libvirt.html">8.2. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-Xen_networking.html">9. Xen networking</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Xen_networking.html#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.html">9.2. Laptop network configuration</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html">10. Xen Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html#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.html">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.html#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.html">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.html">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.html">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.html">10.3. Para-virtualized Network Driver Configuration</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html">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.html#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.html">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.html">11. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html#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></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest.html"><strong>Prev</strong>3.5.Â Installing Windows Server 2008 as a fully vi...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accessk
 ey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Virtualized_block_devices.html"><strong>Next</strong>ChapterÂ 4.Â Virtualized block devices</a></li></ul></body></html>

--- NEW FILE part-Virtualization_Guide-Installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>PartÂ I.Â Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="pr01s03.html" title="3.Â We Need Feedback!"/><link rel="next" href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html" title="ChapterÂ 1.Â Installing the virtualization packages"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="
 p" href="pr01s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html"><strong>Next</strong></a></li></ul><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.html">1. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html#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.html">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.html">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.html">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.html">2. Virtualized guest installation overview</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html#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.html">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.html">2.3. Inst
 alling guests with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html">3. Guest operating system installation procedures</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html#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.html">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.html">3.3. Installing Windows XP as a fully virtualized guest</a></span></dt><dt><span class="section"><a href="sect-Virtualization_G
 uide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest.html">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.html">3.5. Installing Windows Server 2008 as a fully virtualized guest</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s03.html"><strong>Prev</strong>3.Â We Need Feedback!</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html"><strong>Next</strong>ChapterÂ 1.Â Installing the virtualization packages</a></li></ul></body></html>

--- NEW FILE part-Virtualization_Guide-Tips_and_Tricks.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>PartÂ V.Â Tips and Tricks</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="chap-Virtualization_Guide-Xen_configuration_files.html" title="ChapterÂ 22.Â Xen configuration files"/><link rel="next" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous
 "><a accesskey="p" href="chap-Virtualization_Guide-Xen_configuration_files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Tips_and_tricks.html"><strong>Next</strong></a></li></ul><div class="part" lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="part-Virtualization_Guide-Tips_and_Tricks">PartÂ V.Â Tips and Tricks</h1></div></div></div><div class="partintro" lang="en-US"><div><div><div><h1 id="part-Virtualization_Guide-Tips_and_Tricks-Tips_and_Tricks_to_Enhance_Productivity" class="title">Tips and Tricks to Enhance Productivity</h1></div></div></div><div class="para">
				These chapters contain useful hints and tips to improve virtualization performance, scale and stability.
			</div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Tips_and_tricks.html">23. Tips and tricks</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Tips_and_tricks.html#sect-Virtualization_Guide-Tips_and_tricks-Automatically_starting_guests">23.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html">23.2. Changing between the KVM and Xen hypervisors</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html#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.html">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.html">23.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html">23.4. Overcommitting with KVM</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html">23.5. Modifying /etc/grub.conf</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html">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.html">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.html">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.html">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.html">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.html">23.11. Modifying the Xen hypervisor</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd.html">23.12. Very Secure ftpd</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html">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.html">23.14. Disable SMART disk monitori
 ng for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files.html">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.html">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.html">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.html">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.html">24. Creating custom libvirt scripts</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide
 -Creating_custom_libvirt_scripts.html#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></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Xen_configuration_files.html"><strong>Prev</strong>ChapterÂ 22.Â Xen configuration files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Tips_and_tricks.html"><strong>Next</strong>ChapterÂ 23.Â Tips and tricks</a></li></ul></body></html>

--- NEW FILE part-Virtualization_Guide-Troubleshooting.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>PartÂ VI.Â Troubleshooting</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html" title="ChapterÂ 24.Â Creating custom libvirt scripts"/><link rel="next" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="do
 cnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Troubleshooting_Xen.html"><strong>Next</strong></a></li></ul><div class="part" lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="part-Virtualization_Guide-Troubleshooting">PartÂ VI.Â Troubleshooting</h1></div></div></div><div class="partintro" lang="en-US"><div><div><div><h1 id="part-Virtualization_Guide-Troubleshooting-Introduction_to_Troubleshooting_and_Problem_Solving" class="title">Introduction to Troubleshooting and Problem Solving</h1></div></div></div><div class="para">
				The following chapters provide information to assist you in troubleshooting issues you may encounter using virtualization.
			</div><div class="note"><h2>Important note on virtualization issues</h2><div class="para">
					Your particular problem may not appear in this book due to ongoing development which creates and fixes bugs. For the most up to date list of known bugs, issues and bug fixes read the Fedora <em class="citetitle">Release Notes</em> for your version and hardware architecture. The <em class="citetitle">Release Notes</em> can be found in the documentation section of the Fedora website, <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a>.
				</div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Troubleshooting_Xen.html">25. Troubleshooting Xen</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Troubleshooting_Xen.html#sect-Virtualization_Guide-Troubleshooting_Xen-Debugging_and_troubleshooting_Xen">25.1. Debugging and troubleshooting Xen</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html">25.2. Log files overview</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html">25.3. Log file descriptions</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html">25.4. Important directory locations</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_wit
 h_the_logs.html">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.html">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.html">25.7. Para-virtualized guest console access</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html">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.html">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.html">25.10. Common Xen problems</a></span></dt><dt><span class="section"><a href="s
 ect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html">25.11. Guest creation errors</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html">25.12. Troubleshooting with serial consoles</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html#sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_for_Xen">25.12.1. Serial console output for Xen</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_para_virtualized_guests.html">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.html">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.html">25.13. Guest configuration files</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html">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.html">25.15. The layout of the log directories</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Guide-Troubleshooting.html">26. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Troubleshooting.html#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="s
 ect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes.html">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.html">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.html">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_shortage.html">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.html">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.html">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.html">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.html">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.html">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.html">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.html">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.html">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.html">27. Troubleshooting the Xen para-virtualized drivers</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html#sect-Virtualization_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.html">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.html">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.html">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.html">27.5. The sys
 tem has limited throughput with para-virtualized drivers</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html"><strong>Prev</strong>ChapterÂ 24.Â Creating custom libvirt scripts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Troubleshooting_Xen.html"><strong>Next</strong>ChapterÂ 25.Â Troubleshooting Xen</a></li></ul></body></html>

--- NEW FILE part-Virtualization_Guide-Virtualization_Reference_Guide.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>PartÂ IV.Â Virtualization Reference Guide</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes.html" title="16.3.Â Transport modes"/><link rel="next" href="chap-Virtualization_Guide-Virtualization_tools.html" title="ChapterÂ 17.Â Virtualization tools"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a
 ></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Virtualization_tools.html"><strong>Next</strong></a></li></ul><div class="part" lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="part-Virtualization_Guide-Virtualization_Reference_Guide">PartÂ IV.Â Virtualization Reference Guide</h1></div></div></div><div class="partintro" lang="en-US"><div><div><div><h1 id="part-Virtualization_Guide-Virtualization_Reference_Guide-Virtualization_commands_system_tools_applications_and_additional_systems_reference" class="title">Virtualization commands, system tools, applications and additional systems reference</h1></div></div></div><div class="para">
				These chapters provide detailed descriptions of virtualization commands, system tools, and applications included in Fedora. These chapters are designed for users requiring information on advanced functionality and other features.
			</div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="chap-Virtualization_Guide-Virtualization_tools.html">17. Virtualization tools</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-Managing_guests_with_virsh.html">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.html">19. Managing guests with the Virtual Machine Manager (virt-manager)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html#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_Manage
 r_main_window.html">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_.html">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_.html">19.4. Virtual Machine graphical console </a></span></dt><dt><span class="section"><a href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager.html">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_.html">19.6. Restoring a saved machine </a></span></dt><dt><span class="section"><a href="sect-Virtualizati
 on_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html">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.html">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.html">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-Displaying_a_guests_status_.html">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_.html">19.11. Displaying virtual CPUs </a></span></dt><dt><span class="section"><a href="sec
 t-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html">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_.html">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.html">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-Creating_a_virtual_network.html">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.html">20. The xm command quick reference</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-Conf
 iguring_the_Xen_kernel_boot_parameters.html">21. Configuring the Xen kernel boot parameters</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Guide-Xen_configuration_files.html">22. Xen configuration files</a></span></dt></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes.html"><strong>Prev</strong>16.3.Â Transport modes</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Virtualization_tools.html"><strong>Next</strong>ChapterÂ 17.Â Virtualization tools</a></li></ul></body></html>

--- NEW FILE pr01s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>2.Â Document Conventions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="pref-Virtualization_Guide-Preface.html" title="Preface"/><link rel="prev" href="pref-Virtualization_Guide-Preface.html" title="Preface"/><link rel="next" href="pr01s02s02.html" title="2.2.Â Pull-quote Conventions"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Virtualization_Guide-Preface.html"
 ><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pr01s02s02.html"><strong>Next</strong></a></li></ul><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><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Virtualization_Guide-Preface.html"><strong>Prev</strong>Preface</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pr01s02s02.html"><strong>Next</strong>2.2.Â Pull-quote Conventions</a></li></ul></body></html>

--- NEW FILE pr01s02s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>2.2.Â Pull-quote Conventions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="pr01s02.html" title="2.Â Document Conventions"/><link rel="prev" href="pr01s02.html" title="2.Â Document Conventions"/><link rel="next" href="pr01s02s03.html" title="2.3.Â Notes and Warnings"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Prev</strong></a></li><li class="ne
 xt"><a accesskey="n" href="pr01s02s03.html"><strong>Next</strong></a></li></ul><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><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Prev</strong>2.Â Document Conventions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pr01s02s03.html"><strong>Next</strong>2.3.Â Notes and Warnings</a></li></ul></body></html>

--- NEW FILE pr01s02s03.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>2.3.Â Notes and Warnings</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="pr01s02.html" title="2.Â Document Conventions"/><link rel="prev" href="pr01s02s02.html" title="2.2.Â Pull-quote Conventions"/><link rel="next" href="pr01s03.html" title="3.Â We Need Feedback!"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02s02.html"><strong>Prev</strong></a></li><li class="ne
 xt"><a accesskey="n" href="pr01s03.html"><strong>Next</strong></a></li></ul><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><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02s02.html"><strong>Prev</strong>2.2.Â Pull-quote Conventions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pr01s03.html"><strong>Next</strong>3.Â We Need Feedback!</a></li></ul></body></html>

--- NEW FILE pr01s03.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>3.Â We Need Feedback!</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="pref-Virtualization_Guide-Preface.html" title="Preface"/><link rel="prev" href="pr01s02s03.html" title="2.3.Â Notes and Warnings"/><link rel="next" href="part-Virtualization_Guide-Installation.html" title="PartÂ I.Â Installation"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02s03.html"><strong>P
 rev</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Installation.html"><strong>Next</strong></a></li></ul><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><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02s03.html"><strong>Prev</strong>2.3.Â Notes and Warnings</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Installation.html"><strong>Next</strong>PartÂ I.Â Installation</a></li></ul></body></html>

--- NEW FILE pref-Virtualization_Guide-Preface.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>Preface</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="index.html" title="Virtualization Guide"/><link rel="prev" href="index.html" title="Virtualization Guide"/><link rel="next" href="pr01s02.html" title="2.Â Document Conventions"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.htm
 l"><strong>Next</strong></a></li></ul><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><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong>Virtualization Guide</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>Next</strong>2.Â Document Conventions</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtual_Storage_Devices.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>10.4.2.Â Virtual Storage Devices</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html" title="10.4.Â Additional Para-virtualized Hardware Configuration"/><link rel="prev" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html" title="10.4.Â Additional Para-virtualized Hardware Configuration"/><link rel="next" href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html" title="ChapterÂ 11.Â KVM Para-virtualized Drivers"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Produc
 t Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtual_Storage_Devices">10.4.2.Â Virtual Storage Devices</h3></div></div></div><div class="para">
			Perform the following steps to configure additional virtual storage devices for your guest.
		</div><div class="para">
			Edit your guest configuration file in <code class="filename">/etc/xen/YourGuestName</code> replacing <code class="command">YourGuestName</code> with the name of your guest. The original entry may look like the one below.
		</div><pre class="screen">disk = [ "file:/var/lib/libvirt/images/rhel5_64_fv.dsk,hda,w"]
</pre><div class="para">
			Now, add an additional entry for your new physical device, LUN, partition or volume to the â€œ<code class="command">disk=</code>â€ parameter in the configuration file. Storage entities which use the para-virtualized driver resemble the entry below. The â€œ<code class="command">tap:aio</code>â€ parameter instructs the hypervisor to use the para-virtualized driver.
		</div><pre class="screen">disk = [ "file:/var/lib/libvirt/images/rhel5_64_fv.dsk,hda,w",
    "tap:aio:/var/lib/libvirt/images/UserStorage1.dsk,xvda,w" ]
</pre><div class="para">
			If you want to add more entries just add them to the â€œ<code class="command">disk=</code>â€ section as a comma separated list.
		</div><div class="note"><h2>Note</h2><div class="para">
				You need to increment the letter for the '<code class="command">xvd</code>' device, that is for your second storage entity it would be '<code class="command">xvdb</code>' instead of '<code class="command">xvda</code>'.
			</div></div><pre class="screen">disk = [ "file:/var/lib/libvirt/images/rhel5_64_fv.dsk,hda,w",
    "tap:aio:/var/lib/libvirt/images/UserStorage1.dsk,xvda,w",
    "tap:aio:/var/lib/libvirt/images/UserStorage2.dsk,xvdb,w" ]
</pre><div class="para">
			Verify the partitions have been created and are available.
		</div><pre class="screen"># cat /proc/partitions
major minor  #blocks    name
   3     0   10485760   hda
   3     1     104391   hda1
   3     2   10377990   hda2
 202     0      64000   xvda
 202     1      64000   xvdb
 253     0    8257536   dm-0
 253     1    2031616   dm-1
</pre><div class="para">
			In the above output you can see the partition or device â€œ<code class="command">xvdb</code>â€ is available to the system.
		</div><div class="para">
			Mount the new devices and disks to local mount points and update the <code class="filename">/etc/fstab</code> inside the guest to mount the devices and partitions at boot time.
		</div><pre class="screen"># mkdir /mnt/pvdisk_xvda
# mkdir /mnt/pvdisk_xvdb
# mount /dev/xvda /mnt/pvdisk_xvda
# mount /dev/xvdb /mnt/pvdisk_xvdb
# df /mnt
Filesystem           1K-blocks      Used   Available Use%  Mounted on
/dev/xvda                64000        15       63985   1%  /mnt/pvdisk_xvda
/dev/xvdb                64000        15       63985   1%  /mnt/pvdisk_xvdb
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html"><strong>Prev</strong>10.4.Â Additional Para-virtualized Hardware Config...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-KVM_Para_virtualized_Drivers.html"><strong>Next</strong>ChapterÂ 11.Â KVM Para-virtualized Drivers</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>10.4.Â Additional Para-virtualized Hardware Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html" title="ChapterÂ 10.Â Xen Para-virtualized Drivers"/><link rel="prev" href="sect-Virtualization_Guide-Para_virtualized_Network_Driver_Configuration.html" title="10.3.Â Para-virtualized Network Driver Configuration"/><link rel="next" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtual_Storage_Devices.html" title="10.4.2.Â Virtual Storage Devices"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.pn
 g" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Para_virtualized_Network_Driver_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtual_Storage_Devices.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration">10.4.Â Additional Para-virtualized Hardware Configuration</h2></div></div></div><div class="para">
		This section will explain how to add additional virtual network or storage to a guest operating system. 
	</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtualized_Network_Interfaces">10.4.1.Â Virtualized Network Interfaces</h3></div></div></div><div class="para">
			Perform the following steps to configure additional network devices for your guest.
		</div><div class="para">
			Edit your guest configuration file in <code class="filename">/etc/xen/YourGuestName</code> replacing <code class="command">YourGuestName</code> with the name of your guest.
		</div><div class="para">
			The original entry may look like the one below.
		</div><pre class="screen">vif = [ "mac=00:16:3e:2e:c5:a9,bridge=xenbr0" ]
</pre><div class="para">
			Add an additional entry to the â€œ<code class="command">vif=</code>â€ section of the configuration file similar to the one seen below.
		</div><pre class="screen">vif = [ "mac=00:16:3e:2e:c5:a9,bridge=xenbr0",
    "mac=00:16:3e:2f:d5:a9,bridge=xenbr0" ]
</pre><div class="para">
			Make sure you generate a unique MAC address for the new interface. You can use the command below.
		</div><pre class="screen"># echo 'import virtinst.util ; print virtinst.util.randomMAC()' | python
</pre><div class="para">
			After the guest has been rebooted perform the following step in the guest operating system. Verify the update has been added to your <code class="filename">/etc/modules.conf</code> in Red Hat Enterprise Linux 3 or <code class="filename">/etc/modprobe.conf</code> in Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5. Add a new alias for each new interface you added.
		</div><pre class="screen">alias eth1 xen-vnif
</pre><div class="para">
			Now test that each new interface you added make sure it is available inside the guest.
		</div><pre class="screen"># ifconfig eth1
</pre><div class="para">
			The command above should display the properties of <span class="application"><strong>eth1</strong></span>, repeat the command for <span class="application"><strong>eth2</strong></span> if you added a third interface, and so on.
		</div><div class="para">
			Now you can configure the new network interfaces using <code class="command">redhat-config-network</code> or Red Hat Enterprise Linux 3 or <code class="command">system-config-network</code> on Red Hat Enterprise Linux 3, Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Para_virtualized_Network_Driver_Configuration.html"><strong>Prev</strong>10.3.Â Para-virtualized Network Driver Configurati...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration-Virtual_Storage_Devices.html"><strong>Next</strong>10.4.2.Â Virtual Storage Devices</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Additional_resources-Installed_documentation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>B.2.Â Installed documentation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="appe-Virtualization_Guide-Additional_resources.html" title="AppendixÂ B.Â Additional resources"/><link rel="prev" href="appe-Virtualization_Guide-Additional_resources.html" title="AppendixÂ B.Â Additional resources"/><link rel="next" href="go01.html" title="Glossary"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a 
 accesskey="p" href="appe-Virtualization_Guide-Additional_resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="go01.html"><strong>Next</strong></a></li></ul><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><ul class="docnav"><li class="previous"><a accesskey="p" href="appe-Virtualization_Guide-Additional_resources.html"><strong>Prev</strong>AppendixÂ B.Â Additional resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="go01.html"><strong>Next</strong>Glossary</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-KVM_to_Xen.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.2.2.Â KVM to Xen</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html" title="23.2.Â Changing between the KVM and Xen hypervisors"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html" title="23.2.Â Changing between the KVM and Xen hypervisors"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img.html" title="23.3.Â Using qemu-img"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="r
 ight" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-KVM_to_Xen">23.2.2.Â KVM to Xen</h3></div></div></div><div class="para">
				The following procedure covers changing from the KVM hypervisor to the Xen hypervisor. This procedure assumes the <span class="package">kvm</span> package is installed and enabled.
			</div><div class="procedure"><ol class="1"><li id="step-Virtualization_Guide-KVM_to_Xen-Install_the_Xen_packages"><p class="title"><b>Install the Xen packages</b></p><div class="para">
						Install the <span class="package">kernel-xen</span> and <span class="package">xen</span> package if you have not already done so.
					</div><pre class="screen"># yum install kernel-xen xen
</pre><div class="para">
						The <span class="package">kernel-xen</span> package may be installed but disabled.
					</div></li><li id="step-Virtualization_Guide-KVM_to_Xen-Verify_which_kernel_is_in_use"><p class="title"><b>Verify which kernel is in use</b></p><div class="para">
						Use the <code class="command">uname</code> command to determine which kernel is running.
					</div><pre class="screen">$ uname -r
2.6.23.14-107.fc8
</pre><div class="para">
						The "<code class="command">2.6.23.14-107.fc8</code>" kernel is running on the system. This is the default kernel. If the kernel has <code class="command">xen</code> on the end (for example, <code class="command">2.6.23.14-107.fc8xen</code>) then the Xen kernel is running and you can skip the substep.
					</div><ol class="a"><li id="step-Virtualization_Guide-Verify_which_kernel_is_in_use-Changing_the_default_kernel_to_the_Xen_kernel"><p class="title"><b>Changing the default kernel to the Xen kernel</b></p><div class="para">
								The <code class="filename">grub.conf</code> file determines which kernel is booted. To change the default kernel edit the <code class="filename">/boot/grub/grub.conf</code> file as shown below.
							</div><pre class="screen"><span class="bold bold"><strong>default=0</strong></span>
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.23.14-107.fc8)
        root (hd0,0)
        kernel /vmlinuz-2.6.23.14-107.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.23.14-107.fc8.img
title Fedora (2.6.23.14-107.fc8xen)
        root (hd0,0)
        kernel /xen.gz-2.6.23.14-107.fc8
        module /vmlinuz-2.6.23.14-107.fc8xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        module /initrd-2.6.23.14-107.fc8xen.img
</pre><div class="para">
								Notice the <span class="bold bold"><strong>default=0</strong></span> parameter. This is instructing the GRUB boot loader to boot the first entry, the default kernel. Change the default to <em class="parameter"><code>1</code></em> (or the number for the Xen kernel):
							</div><pre class="screen"><span class="bold bold"><strong>default=1</strong></span>
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.23.14-107.fc8)
        root (hd0,0)
        kernel /vmlinuz-2.6.23.14-107.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.23.14-107.fc82.6.23.14-107.fc8.img
title Fedora (2.6.23.14-107.fc8xen)
        root (hd0,0)
        kernel /xen.gz-2.6.23.14-107.fc8
        module /vmlinuz-2.6.23.14-107.fc8xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        module /initrd-2.6.23.14-107.fc8xen.img
</pre></li></ol></li><li id="step-Virtualization_Guide-KVM_to_Xen-Reboot_to_load_the_new_kernel"><p class="title"><b>Reboot to load the new kernel</b></p><div class="para">
						Reboot the system. The computer will restart with the Xen kernel. Verify with the <code class="command">uname</code> command:
					</div><pre class="screen">$ uname -r
2.6.23.14-107.fc8xen
</pre><div class="para">
						If the output has <code class="computeroutput">xen</code> on the end the Xen kernel is running.
					</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html"><strong>Prev</strong>23.2.Â Changing between the KVM and Xen hypervisors</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img.html"><strong>Next</strong>23.3.Â Using qemu-img</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_3.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>10.2.2.Â Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 3</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html" title="10.2.Â Installing the Para-virtualized Drivers"/><link rel="prev" href="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html" title="10.2.Â Installing the Para-virtualized Drivers"/><link rel="next" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_4.html" title="10.2.3.Â Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 4"/></head><body clas
 s="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_4.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="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</h3></div></div></div><div class="para"
 >
		This section contains detailed instructions for the para-virtualized drivers in a Red Hat Enterprise 3 guest operating system.
	</div><div class="note"><h2>Please note</h2><div class="para">
			These packages do not support booting from a para-virtualized disk. Booting the guest operating system kernel still requires the use of the emulated IDE driver, while any other (non-system) user-space applications and data can use the para-virtualized block device drivers.
		</div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_3-Driver_Installation">Driver Installation</h5>
			The list below covers the steps to install a Red Hat Enterprise Linux 3 guest with para-virtualized drivers.
		</div><div class="orderedlist"><ol class="arabic"><li><div class="para">
				Copy the <code class="filename">kmod-xenpv</code> rpm for your hardware architecture and kernel variant to your guest operating system.
			</div></li><li><div class="para">
				Use the <code class="command">rpm</code> utility to install the RPM packages. Ensure you have correctly identified which package you need for your guest operating system variant and architecture.
			</div><pre class="screen">[root at rhel3]# rpm -ivh kmod-xenpv*
</pre></li><li><div class="para">
				You need to perform the commands below to enable the correct and automated loading of the para-virtualized drivers. <span class="emphasis"><em>%kvariant</em></span> is the kernel variant the para-virtualized drivers have been build against and <span class="emphasis"><em>%release</em></span> corresponds to the release version of the para-virtualized drivers.
			</div><pre class="screen">[root at rhel3]# mkdir -p /lib/modules/'uname -r'/extra/xenpv	
[root at rhel3]# cp -R /lib/modules/2.4.21-52.EL[%kvariant]/extra/xenpv/%release \
/lib/modules/'uname -r'/extra/xenpv
[root at rhel3]# cd /lib/modules/'uname -r'/extra/xenpv/%release
[root at rhel3]# insmod xen-platform-pci.o
[root at rhel3]# insmod xen-balloon.o`	
[root at rhel3]# insmod xen-vbd.o
[root at rhel3]# insmod xen-vnif.o
</pre><div class="note"><h2>Note</h2><div class="para">
					Warnings will be generated by <code class="command">insmod</code> when installing the binary driver modules due to Red Hat Enterprise Linux 3 having <span class="application"><strong>MODVERSIONS</strong></span> enabled. These warnings can be ignored.
				</div></div></li><li><div class="para">
				Verify <code class="filename">/etc/modules.conf</code> and make sure you have an alias for <code class="systemitem">eth0</code> like the one below. If you are planning to configure multiple interfaces add an additional line for each interface.
			</div><pre class="screen">alias eth0 xen-vnif
</pre><div class="para">
				Edit <code class="filename">/etc/rc.local</code> and add the line:
			</div><pre class="screen">insmod /lib/modules/'uname -r'/extra/xenpv/%release/xen-vbd.o
</pre><div class="note"><h2>Note</h2><div class="para">
					Substitute â€œ%releaseâ€ with the actual release version (for example 0.1-5.el) for the para-virtualized drivers. If you update the para-virtualized driver RPM package make sure you update the release version to the appropriate version.
				</div></div></li><li><div class="para">
				Shutdown the virtual machine (use â€œ<code class="command">#shutdown -h now</code>â€ inside the guest).
			</div></li><li><div class="para">
				Edit the guest configuration file in <code class="filename">/etc/xen/YourGuestsName</code> in the following ways:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Remove the â€œ<code class="command">type=ioemu</code>â€ entry from the â€œ<code class="command">vif=</code>â€ entry.
					</div></li><li><div class="para">
						Add any additional disk partitions, volumes or LUNs to the guest so that they can be accessed via the para-virtualized (<code class="command">xen-vbd</code>) disk driver.
					</div></li><li><div class="para">
						For each additional physical device, LUN, partition or volume add an entry similar to the one below to the â€œ<code class="command">disk=</code>â€ section in the guest configuration file. The original â€œ<code class="command">disk=</code>â€ entry might also look like the entry below.
					</div><pre class="screen">disk = [ "file:/var/lib/libvirt/images/rhel3_64_fv.dsk,hda,w"]
</pre></li><li><div class="para">
						Once you have added additional physical devices, LUNs, partitions or volumes; the para-virtualized driver entry in your XML configuration file should resemble the entry shown below.
					</div><pre class="screen">disk = [ "file:/var/lib/libvirt/images/rhel3_64_fv.dsk,hda,w",
"tap:aio:/var/lib/libvirt/images/UserStorage.dsk,xvda,w" ]
</pre><div class="note"><h2>Note</h2><div class="para">
							Use â€œ<code class="command">tap:aio</code>â€ for the para-virtualized device if a file based image is used.
						</div></div></li></ul></div></li><li><div class="para">
				Boot the virtual machine using the <code class="command">virsh</code> command:
			</div><pre class="screen"># virsh start <em class="parameter"><code>YourGuestName</code></em>
</pre></li></ol></div><div class="warning"><h2>Be aware</h2><div class="para">
			The para-virtualized drivers are not automatically added and loaded to the system because <code class="command">weak-modules</code> and <code class="command">modversions</code> support is not provided in Red Hat Enterprise Linux 3. To insert the module execute the command below.
		</div><div class="para">
			<code class="command">insmod xen-vbd.ko</code>
		</div></div><div class="para">
		Red Hat Enterprise Linux 3 requires the manual creation of the special files for the block devices which use <code class="command">xen-vbd</code>. The steps below will cover how to create and register para-virtualized block devices.
	</div><div class="para">
		Use the following script to create the special files after the para-virtualized block device driver is loaded.
	</div><pre class="screen">#!/bin/sh
module="xvd"
mode="664"
major=`awk "\\$2==\"$module\" {print \\$1}" /proc/devices`
# < mknod for as many or few partitions on xvd disk attached to FV guest >
# change/add xvda to xvdb, xvbd, etc. for 2nd, 3rd, etc., disk added in
# in xen config file, respectively.
mknod /dev/xvdb b $major 0
mknod /dev/xvdb1 b $major 1
mknod /dev/xvdb2 b $major 2
chgrp disk /dev/xvd*
chmod $mode /dev/xvd*
</pre><div class="para">
		For each additional virtual disk, increment the minor number by 16. In the example below an additional device, minor number 16, is created.
	</div><pre class="screen">mknod /dev/xvdc b $major 16
mknod /dev/xvdc1 b $major 17
</pre><div class="para">
		This would make the next device 32 which can be created by:
	</div><pre class="screen">mknod /dev/xvdd b $major 32
mknod /dev/xvdd1 b $major 33
</pre><div class="para">
		Now you should verify the partitions which you have created are available.
	</div><pre class="screen">[root at rhel3]# cat /proc/partitions
major   minor     #blocks   name

  3        0      10485760  hda
  3        1        104391  hda1
  3        2      10377990  hda2
202        0         64000  xvdb
202        1         32000  xvdb1
202        2         32000  xvdb2
253        0       8257536  dm-0
253        1       2031616  dm-1
</pre><div class="para">
		In the above output, you can observe that the partitioned device â€œ<code class="filename">xvdb</code>â€ is available to the system.
	</div><div class="para">
		The commands below mount the new block devices to local mount points and updates the <code class="filename">/etc/fstab</code> inside the guest to mount the devices/partitions during boot.
	</div><pre class="screen">[root at rhel3]# mkdir /mnt/pvdisk_p1
[root at rhel3]# mkdir /mnt/pvdisk_p2
[root at rhel3]# mount /dev/xvdb1 /mnt/pvdisk_p1
[root at rhel3]# mount /dev/xvdb2 /mnt/pvdisk_p2
[root at rhel3]# df /mnt/pvdisk_p1
Filesystem           1K-blocks      Used   Available Use%  Mounted on
/dev/xvdb1               32000        15       31985   1%  /mnt/pvdisk_p1
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html"><strong>Prev</strong>10.2.Â Installing the Para-virtualized Drivers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_4.html"><strong>Next</strong>10.2.3.Â Installation and Configuration of Para-vi...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_4.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>10.2.3.Â Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 4</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html" title="10.2.Â Installing the Para-virtualized Drivers"/><link rel="prev" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_3.html" title="10.2.2.Â Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 3"/><link rel="next" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_5.html" title="10.2.4.Â Installa
 tion and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 5"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_3.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_5.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterpri
 se_Linux_4">10.2.3.Â Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 4</h3></div></div></div><div class="para">
		This section contains detailed instructions for the para-virtualized drivers in a Red Hat Enterprise 4 guest operating system.
	</div><div class="note"><h2>Please note</h2><div class="para">
			These packages do not support booting from a para-virtualized disk. Booting the guest operating system kernel still requires the use of the emulated IDE driver, while any other (non-system) user-space applications and data can use the para-virtualized block device drivers.
		</div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_4-Driver_Installation">Driver Installation</h5>
			The list below covers the steps to install a Red Hat Enterprise Linux 4 guest with para-virtualized drivers.
		</div><div class="orderedlist"><ol class="arabic"><li><div class="para">
				Copy the <code class="filename">kmod-xenpv</code>, <code class="filename">modules-init-tools</code> and <code class="filename">modversions</code> RPMs for your hardware architecture and kernel variant to your guest operating system.
			</div></li><li><div class="para">
				Use the <code class="command">rpm</code> utility to install the RPM packages. Make sure you have correctly identified which package you need for your guest operating system variant and architecture. An updated module-init-tools is required for this package, it is available with the Red Hat Enterprise Linux 4-6-z kernel or newer.
			</div><pre class="screen">[root at rhel4]# rpm -ivh modversions
[root at rhel4]# rpm -Uvh module-init-tools
[root at rhel4]# rpm -ivh kmod-xenpv*
</pre><div class="note"><h2>Note</h2><div class="para">
					There are different packages for UP, SMP, Hugemem and architectures so make sure you have the right RPMs for your kernel.
				</div></div></li><li><div class="para">
				Execute <code class="command">cat /etc/modules.conf</code> to verify you have an alias for <code class="systemitem">eth0</code> like the one below. If you are planning to configure multiple interfaces add an additional line for each interface. It it does not look like the entry below change it.
			</div><pre class="screen">alias eth0 xen-vnif
</pre></li><li><div class="para">
				Shutdown the virtual machine (use â€œ<code class="command">#shutdown -h now</code>â€ inside the guest).
			</div></li><li><div class="para">
				Edit the guest configuration file in <code class="filename">/etc/xen/YourGuestsName</code> in the following ways:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Remove the â€œ<code class="command">type=ioemu</code>â€ entry from the â€œ<code class="command">vif=</code>â€ entry.
					</div></li><li><div class="para">
						Add any additional disk partitions, volumes or LUNs to the guest so that they can be accessed via the para-virtualized (<code class="command">xen-vbd</code>) disk driver.
					</div></li><li><div class="para">
						For each additional physical device, LUN, partition or volume add an entry similar to the one shown below to the â€œ<code class="command">disk=</code>â€ section in the guest configuration file. The original â€œ<code class="command">disk=</code>â€ entry might also look like the entry below.
					</div><pre class="screen">disk = [ "file:/var/lib/libvirt/images/rhel4_64_fv.dsk,hda,w"]
</pre></li><li><div class="para">
						Once you have added additional physical devices, LUNs, partitions or volumes; the para-virtualized driver entry in your XML configuration file should resemble the entry shown below.
					</div><pre class="screen">disk = [ "file:/var/lib/libvirt/images/rhel3_64_fv.dsk,hda,w",
"tap:aio:/var/lib/libvirt/images/UserStorage.dsk,xvda,w" ]
</pre><div class="note"><h2>Note</h2><div class="para">
							Use â€œ<code class="command">tap:aio</code>â€ for the para-virtualized device if a file based image is used.
						</div></div></li></ul></div></li><li><div class="para">
				Boot the virtual machine using the <code class="command">virsh</code> command:
			</div><pre class="screen"># virsh start <em class="parameter"><code>YourGuestName</code></em>
</pre></li></ol></div><div class="para">
		On the first reboot of the virtual guest, <code class="command">kudzu</code> will ask you to "<span class="emphasis"><em>Keep or Delete the Realtek Network device</em></span>" and "<span class="emphasis"><em>Configure the xen-bridge device</em></span>". You should configure the <code class="command">xen-bridge</code> and delete the Realtek network device.
	</div><div class="para">

	</div><div class="para">
		Now, verify the partitions which you have created are available.
	</div><pre class="screen">[root at rhel4]# cat /proc/partitions
major    minor   #blocks   name

   3        0    10485760  hda
   3        1      104391  hda1
   3        2    10377990  hda2
 202        0       64000  xvdb
 202        1       32000  xvdb1
 202        2       32000  xvdb2
 253        0     8257536  dm-0
 253        1     2031616  dm-1
</pre><div class="para">
		In the above output, you can see the partitioned device â€œ<code class="filename">xvdb</code>â€ is available to the system.
	</div><div class="para">
		The commands below mount the new block devices to local mount points and updates the <code class="filename">/etc/fstab</code> inside the guest to mount the devices/partitions during boot.
	</div><pre class="screen">[root at rhel4]# mkdir /mnt/pvdisk_p1
[root at rhel4]# mkdir /mnt/pvdisk_p2
[root at rhel4]# mount /dev/xvdb1 /mnt/pvdisk_p1
[root at rhel4]# mount /dev/xvdb2 /mnt/pvdisk_p2
[root at rhel4]# df /mnt/pvdisk_p1
Filesystem           1K-blocks      Used   Available Use%  Mounted on
/dev/xvdb1               32000        15       31985   1%  /mnt/pvdisk_p1
</pre><div class="note"><h2>Automatic module loading</h2><div class="para">
			The <code class="command">xen-vbd</code> driver may not automatically load. Execute the following command on the guest, substituting <span class="emphasis"><em>%release</em></span> with the correct release version for the para-virtualized drivers.
		</div><div class="para">
			<code class="command"># insmod /lib/modules/'uname -r'/weak-updates/xenpv/%release/xen-vbd.ko</code>
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_3.html"><strong>Prev</strong>10.2.2.Â Installation and Configuration of Para-vi...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_5.html"><strong>Next</strong>10.2.4.Â Installation and Configuration of Para-vi...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_5.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>10.2.4.Â Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 5</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html" title="10.2.Â Installing the Para-virtualized Drivers"/><link rel="prev" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_4.html" title="10.2.3.Â Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 4"/><link rel="next" href="sect-Virtualization_Guide-Para_virtualized_Network_Driver_Configuration.html" title="10.3.Â Para-virtualized Network Driver Configuration"/></hea
 d><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_4.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Para_virtualized_Network_Driver_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="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</h3></div></div></div
 ><div class="para">
		This section contains detailed instructions for the para-virtualized drivers in a Red Hat Enterprise 5 guest operating system.
	</div><div class="note"><h2>Please note</h2><div class="para">
			These packages do not support booting from a para-virtualized disk. Booting the guest operating system kernel still requires the use of the emulated IDE driver, while any other (non-system) user-space applications and data can use the para-virtualized block device drivers.
		</div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_5-Driver_Installation">Driver Installation</h5>
			The list below covers the steps to install a Red Hat Enterprise Linux 5 guest with para-virtualized drivers.
		</div><div class="orderedlist"><ol class="arabic"><li><div class="para">
				Copy the <code class="filename">kmod-xenpv</code> rpm for your hardware architecture and kernel variant to your guest operating system.
			</div></li><li><div class="para">
				Use the <code class="command">rpm</code> utility to install the RPM packages. Make sure you correctly identify which package you need for your guest operating system variant and architecture.
			</div><pre class="screen">[root at rhel5]# rpm -ivh kmod-xenpv*
</pre></li><li><div class="para">
				Issue the command below to disable automatic hardware detection inside the guest operating system
			</div><pre class="screen">[root at rhel5]# chkconfig kudzu off
</pre></li><li><div class="para">
				Execute <code class="command">cat /etc/modules.conf</code> to verify you have an alias for <code class="systemitem">eth0</code> like the one below. If you are planning to configure multiple interfaces add an additional line for each interface. It it does not look like the entry below change it.
			</div><pre class="screen">alias eth0 xen-vnif
</pre></li><li><div class="para">
				Shutdown the virtual machine (use â€œ<code class="command">#shutdown -h now</code>â€ inside the guest).
			</div></li><li><div class="para">
				Edit the guest configuration file in <code class="filename">/etc/xen/<Your GuestsName></code> in the following ways:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Remove the â€œ<code class="command">type=ioemu</code>â€ entry from the â€œ<code class="command">vif=</code>â€ entry.
					</div></li><li><div class="para">
						Add any additional disk partitions, volumes or LUNs to the guest so that they can be accessed via the para-virtualized (<code class="command">xen-vbd</code>) disk driver.
					</div></li><li><div class="para">
						For each additional physical device, LUN, partition or volume add an entry similar to the one shown below to the â€œ<code class="command">disk=</code>â€ section in the guest configuration file. The original â€œ<code class="command">disk=</code>â€ entry might also look like the entry below.
					</div><pre class="screen">disk = [ "file:/var/lib/libvirt/images/rhel4_64_fv.dsk,hda,w"]
</pre></li><li><div class="para">
						Once you have added additional physical devices, LUNs, partitions or volumes; the para-virtualized driver entry in your XML configuration file should resemble the entry shown below.
					</div><pre class="screen">disk = [ "file:/var/lib/libvirt/images/rhel3_64_fv.dsk,hda,w",
"tap:aio:/var/lib/libvirt/images/UserStorage.dsk,xvda,w" ]
</pre><div class="note"><h2>Note</h2><div class="para">
							Use â€œ<code class="command">tap:aio</code>â€ for the para-virtualized device if a file based image is used.
						</div></div></li></ul></div></li><li><div class="para">
				Boot the virtual machine using the <code class="command">virsh</code> command:
			</div><pre class="screen"># virsh start <em class="parameter"><code>YourGuestName</code></em>
</pre></li></ol></div><div class="para">
		To verify the network interface has come up after installing the para-virtualized drivers issue the following command on the guest. It should display the interface information including an assigned IP address
	</div><pre class="screen">[root at rhel5]# ifconfig eth0
</pre><div class="para">
		Now, verify the partitions which you have created are available.
	</div><pre class="screen">[root at rhel5]# cat /proc/partitions
major minor  #blocks    name
   3     0   10485760   hda
   3     1     104391   hda1
   3     2   10377990   hda2
 202     0      64000   xvdb
 202     1      32000   xvdb1
 202     2      32000   xvdb2
 253     0    8257536   dm-0
 253     1    2031616   dm-1
</pre><div class="para">
		In the above output, you can see the partitioned device â€œ<code class="filename">xvdb</code>â€ is available to the system.
	</div><div class="para">
		The commands below mount the new block devices to local mount points and updates the <code class="filename">/etc/fstab</code> inside the guest to mount the devices/partitions during boot.
	</div><pre class="screen">[root at rhel5]# mkdir /mnt/pvdisk_p1
[root at rhel5]# mkdir /mnt/pvdisk_p2
[root at rhel5]# mount /dev/xvdb1 /mnt/pvdisk_p1
[root at rhel5]# mount /dev/xvdb2 /mnt/pvdisk_p2
[root at rhel5]# df /mnt/pvdisk_p1
Filesystem           1K-blocks      Used   Available Use%  Mounted on
/dev/xvdb1               32000        15       31985   1%  /mnt/pvdisk_p1
</pre><div class="para">

	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_4.html"><strong>Prev</strong>10.2.3.Â Installation and Configuration of Para-vi...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Para_virtualized_Network_Driver_Configuration.html"><strong>Next</strong>10.3.Â Para-virtualized Network Driver Configurati...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>3.2.Â Installing Red Hat Enterprise Linux as a fully virtualized guest</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html" title="ChapterÂ 3.Â Guest operating system installation procedures"/><link rel="prev" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html" title="ChapterÂ 3.Â Guest operating system installation procedures"/><link rel="next" href="sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest.html" title="3.3.Â Installing Windows XP as a fully virtualized guest"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedorapr
 oject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></div></div><div class="para">
		This section covers installing a fully virtualized Red Hat Enterprise Linux 5 guest. 
	</div><div class="procedure" id="proc-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager"><h6>ProcedureÂ 3.3.Â Creating a fully virtualized Red Hat Enterprise Linux 5 guest with virt-manager</h6><ol class="1"><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Open_virt_manager"><p class="title"><b>Open virt-manager</b></p><div class="para">
				Start <code class="command">virt-manager</code>. Launch the <span class="guimenuitem"><strong>Virtual Machine Manager</strong></span> application from the <span class="guimenuitem"><strong>Applications</strong></span> menu and <span class="guimenuitem"><strong>System Tools</strong></span> submenu. Alternatively, run the <code class="command">virt-manager</code> command as root.
			</div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Select_the_hypervisor"><p class="title"><b>Select the hypervisor</b></p><div class="para">
				Select the hypervisor. If installed, select Xen or KVM. For this example, select KVM. Note that presently KVM is named <code class="computeroutput">qemu</code>.
			</div><div class="para">
				Connect to a hypervisor if you have not already done so. Open the <span class="guilabel"><strong>File</strong></span> menu and select the <span class="guilabel"><strong>Add Connection...</strong></span> option. Refer to <a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html#sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window" title="19.1.Â The open connection window">SectionÂ 19.1, â€œThe open connection windowâ€</a>.
			</div><div class="para">
				Once a hypervisor connection is selected the <span class="guilabel"><strong>New</strong></span> button becomes available. Press the <span class="guilabel"><strong>New</strong></span> button.
			</div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Start_the_new_virtual_machine_wizard"><p class="title"><b>Start the new virtual machine wizard</b></p><div class="para">
				Pressing the <span class="guilabel"><strong>New</strong></span> button starts the virtual machine creation wizard. 
				<div class="mediaobject"><img src="images/Create-1.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Name_the_virtual_machine"><p class="title"><b>Name the virtual machine</b></p><div class="para">
				Provide a name for your virtualized guest. Punctuation and whitespace characters are not permitted. 
				<div class="mediaobject"><img src="images/EL5naming-2.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Choose_a_virtualization_method"><p class="title"><b>Choose a virtualization method</b></p><div class="para">
				Choose the virtualization method for the virtualized guest. Note you can only select an installed virtualization method. If you selected KVM or Xen earlier (<a class="xref" href="sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest.html#step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Name_the_virtual_machine" title="Name the virtual machine">Step 4</a>) you must use the hypervisor you selected. This example uses the KVM hypervisor. 
				<div class="mediaobject"><img src="images/KVM-3.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Select_the_installation_method"><p class="title"><b>Select the installation method</b></p><div class="para">
				Select <span class="guilabel"><strong>Local install media</strong></span> for installing from an optical disc or ISO image; <span class="guilabel"><strong>Network install tree</strong></span> to install from a HTTP, FTP, or NFS server; or <span class="guilabel"><strong>Network boot</strong></span> to install from a PXE server.
			</div><div class="para">
				Set <span class="guilabel"><strong>OS Type</strong></span> to <span class="guilabel"><strong>Linux</strong></span> and <span class="guilabel"><strong>OS Variant</strong></span> to <span class="guilabel"><strong>Red Hat Enterprise Linux 5</strong></span> as shown in the screenshot. 
				<div class="mediaobject"><img src="images/EL5method-4.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Locate_installation_media"><p class="title"><b>Locate installation media</b></p><div class="para">
				Select ISO image location or CD-ROM or DVD device. This example uses an ISO file image of the Red Hat Enterprise Linux 5 installation DVD.
			</div><ol class="a"><li><div class="para">
						Press the <span class="guibutton"><strong>Browse</strong></span> button.
					</div></li><li><div class="para">
						Search to the location of the ISO file and select the ISO image. Press <span class="guibutton"><strong>Open</strong></span> to confirm your selection.
					</div></li><li><div class="para">
						The file is selected and ready to install from. 
						<div class="mediaobject"><img src="images/EL5media-5.png"/></div>
						 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
					</div></li></ol><div class="warning"><h2>Image files and SELinux</h2><div class="para">
					For ISO image files and guest storage images, use the <code class="filename">/var/lib/libvirt/images/</code> directory. Any other location may require additional configuration for SELinux, refer to <a class="xref" href="chap-Virtualization_Guide-Security_for_virtualization.html#sect-Virtualization_Guide-Security_for_virtualization-SELinux_and_virtualization" title="7.1.Â SELinux and virtualization">SectionÂ 7.1, â€œSELinux and virtualizationâ€</a> for details.
				</div></div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Storage_setup"><p class="title"><b>Storage setup</b></p><div class="para">
				Assign a physical storage device (<span class="guilabel"><strong>Block device</strong></span>) or a file-based image (<span class="guilabel"><strong>File</strong></span>). File-based images must be stored in the <code class="filename">/var/lib/libvirt/images/</code> directory. Assign sufficient storage for your virtualized guest. Assign sufficient space for your virtualized guest and any application it requires. 
				<div class="mediaobject"><img src="images/EL5storage-6.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div><div class="note"><h2>To migrating this guest</h2><div class="para">
					Live and offline migrations require guests to be installed on shared network storage. For information on setting up shared storage for guests refer to <a class="xref" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html" title="ChapterÂ 5.Â Shared storage and virtualization">ChapterÂ 5, <i>Shared storage and virtualization</i></a>.
				</div></div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Network_setup"><p class="title"><b>Network setup</b></p><div class="para">
				Select either <span class="guilabel"><strong>Virtual network</strong></span> or <span class="guilabel"><strong>Shared physical device</strong></span>.
			</div><div class="para">
				The virtual network option uses Network Address Translation (NAT) to share the default network device with the virtualized guest. Use the virtual network option for wireless networks.
			</div><div class="para">
				The shared physical device option uses a network bond to give the virtualized guest full access to a network device. 
				<div class="mediaobject"><img src="images/Network-7.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Memory_and_CPU_allocation"><p class="title"><b>Memory and CPU allocation</b></p><div class="para">
				The Allocate memory and CPU window displays. Choose appropriate values for the virtualized CPUs and RAM allocation. These values affect the host's and guest's performance.
			</div><div class="para">
				Virtualized guests require sufficient physical memory (RAM) to run efficiently and effectively. Choose a memory value which suits your guest operating system and application requirements. Windows Server 2008. Remember, guests use physical RAM. Running too many guests or leaving insufficient memory for the host system results in significant usage of virtual memory and swapping. Virtual memory is significantly slower causing degraded system performance and responsiveness. Ensure to allocate sufficient memory for all guests and the host to operate effectively.
			</div><div class="para">
				Assign sufficient virtual CPUs for the virtualized guest. If the guest runs a multithreaded application assign the number of virtualized CPUs it requires to run most efficiently. Do not assign more virtual CPUs than there are physical processors (or hyper-threads) available on the host system. It is possible to over allocate virtual processors, however, over allocating has a significant, negative affect on guest and host performance due to processor context switching overheads.
			</div><div class="para">
				<div class="mediaobject"><img src="images/Memory_and_CPU-8.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Verify_and_start_guest_installation"><p class="title"><b>Verify and start guest installation</b></p><div class="para">
				Verify the configuration. 
				<div class="mediaobject"><img src="images/EL5finished.png"/></div>
				 Press <span class="guibutton"><strong>Finish</strong></span> to start the guest installation procedure.
			</div></li><li id="step-Virtualization_Guide-Creating_a_fully_virtualized_Red_Hat_Enterprise_Linux_5_guest_with_virt_manager-Installing_Linux"><p class="title"><b>Installing Linux</b></p><div class="para">
				Complete the Red Hat Enterprise Linux 5 installation sequence. The installation sequence is covered by the <em class="citetitle">Red Hat Enterprise Linux Installation Guide</em>, available from <a href="http://redhat.com/docs">http://redhat.com/docs</a>.
			</div></li></ol></div><div class="para">
		A fully virtualized Red Hat Enterprise Linux 5 Guest is now installed.
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html"><strong>Prev</strong>ChapterÂ 3.Â Guest operating system installation pr...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Next</strong>3.3.Â Installing Windows XP as a fully virtualized...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>3.4.Â Installing Windows Server 2003 as a fully virtualized guest</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html" title="ChapterÂ 3.Â Guest operating system installation procedures"/><link rel="prev" href="sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest.html" title="3.3.Â Installing Windows XP as a fully virtualized guest"/><link rel="next" href="sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest.html" title="3.5.Â Installing Windows Server 2008 as a fully virtualized guest"/></head><body class="draft "><p id="title"><a class="left" href="http:
 //www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest">3.4.Â Installing Windows Server 2003 as a fully virtualized guest</h2></div></div></div><div class="para">
		This chapter describes installing a fully virtualized Windows Server 2003 guest with the <code class="command">virt-install</code> command. <code class="command">virt-install</code> can be used instead of virt-manager This process is similar to the Windows XP installation covered in <a class="xref" href="sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest.html" title="3.3.Â Installing Windows XP as a fully virtualized guest">SectionÂ 3.3, â€œInstalling Windows XP as a fully virtualized guestâ€</a>.
	</div><div class="procedure"><ol class="1"><li><div class="para">
				Using <code class="command">virt-install</code> for installing Windows Server 2003 as the console for the Windows guest opens the virt-viewer window promptly. An example of using the <code class="command">virt-install</code> for installing a Windows Server 2003 guest:
			</div><div class="para">
				Start the installation with the <code class="command">virt-install</code> command.
			</div><pre class="screen"># virt-install -hvm -s 5 -f /var/lib/libvirt/images/windows2003spi1.dsk \
-n windows2003sp1 -cdrom=/ISOs/WIN/en_windows_server_2003_sp1.iso  \
-vnc -r 1024
</pre></li><li><div class="para">
				Once the guest boots into the installation you must quickly press <span class="keycap"><strong>F5</strong></span>. If you do not press <span class="keycap"><strong>F5</strong></span> at the right time you will need to restart the installation. Pressing <span class="keycap"><strong>F5</strong></span> allows you to select different <span class="guilabel"><strong>HAL</strong></span> or <span class="guilabel"><strong>Computer Type</strong></span>. Choose <code class="computeroutput">Standard PC</code> as the Computer Type. This is the only non standard step required.
			</div><div class="mediaobject"><img src="images/win2003_select_hal.png"/></div></li><li><div class="para">
				Complete the rest of the installation.
			</div><div class="mediaobject"><img src="images/win2003_setup_part1.png"/></div><div class="mediaobject"><img src="images/win2003_setup_part2.png"/></div><div class="mediaobject"><img src="images/win2003_setup_part3.png"/></div></li><li><div class="para">
				Windows Server 2003 is now installed as a fully virtualized guest.
			</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Prev</strong>3.3.Â Installing Windows XP as a fully virtualized...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest.html"><strong>Next</strong>3.5.Â Installing Windows Server 2008 as a fully vi...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>3.5.Â Installing Windows Server 2008 as a fully virtualized guest</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html" title="ChapterÂ 3.Â Guest operating system installation procedures"/><link rel="prev" href="sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest.html" title="3.4.Â Installing Windows Server 2003 as a fully virtualized guest"/><link rel="next" href="part-Virtualization_Guide-Configuration.html" title="PartÂ II.Â Configuration"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.p
 ng" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Configuration.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest">3.5.Â Installing Windows Server 2008 as a fully virtualized guest</h2></div></div></div><div class="para">
		This section covers installing a fully virtualized Windows Server 2008 guest. 
	</div><div class="procedure" id="proc-Virtualization_Guide-Installing_Windows_Server_2008_as_a_fully_virtualized_guest-Installing_Windows_Server_2008_with_virt_manager"><h6>ProcedureÂ 3.4.Â Installing Windows Server 2008 with virt-manager</h6><ol class="1"><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Open_virt_manager"><p class="title"><b>Open virt-manager</b></p><div class="para">
				Start <code class="command">virt-manager</code>. Launch the <span class="guimenuitem"><strong>Virtual Machine Manager</strong></span> application from the <span class="guimenuitem"><strong>Applications</strong></span> menu and <span class="guimenuitem"><strong>System Tools</strong></span> submenu. Alternatively, run the <code class="command">virt-manager</code> command as root.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Select_the_hypervisor"><p class="title"><b>Select the hypervisor</b></p><div class="para">
				Select the hypervisor. If installed, select Xen or KVM. For this example, select KVM. Note that presently KVM is named <code class="computeroutput">qemu</code>.
			</div><div class="para">
				Once the option is selected the <span class="guilabel"><strong>New</strong></span> button becomes available. Press the <span class="guilabel"><strong>New</strong></span> button.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Start_the_new_virtual_machine_wizard"><p class="title"><b>Start the new virtual machine wizard</b></p><div class="para">
				Pressing the <span class="guilabel"><strong>New</strong></span> button starts the virtual machine creation wizard. 
				<div class="mediaobject"><img src="images/Create-1.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Name_the_virtual_machine"><p class="title"><b>Name the virtual machine</b></p><div class="para">
				Provide a name for your virtualized guest. Punctuation and whitespace characters are not permitted. 
				<div class="mediaobject"><img src="images/Name-2.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Choose_a_virtualization_method"><p class="title"><b>Choose a virtualization method</b></p><div class="para">
				Choose the virtualization method for the virtualized guest. Note you can only select an installed virtualization method. If you selected KVM or Xen earlier (step 2) you must use the hypervisor you selected. This example uses the KVM hypervisor. 
				<div class="mediaobject"><img src="images/KVM-3.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Select_the_installation_method"><p class="title"><b>Select the installation method</b></p><div class="para">
				For all versions of Windows you must use <span class="guilabel"><strong>local install media</strong></span>, either an ISO image or physical optical media.
			</div><div class="para">
				PXE may be used if you have a PXE server configured for Windows network installation. PXE Windows installation is not covered by this guide.
			</div><div class="para">
				Set <span class="guilabel"><strong>OS Type</strong></span> to <span class="guilabel"><strong>Windows</strong></span> and <span class="guilabel"><strong>OS Variant</strong></span> to <span class="guilabel"><strong>Microsoft Windows 2008</strong></span> as shown in the screenshot. 
				<div class="mediaobject"><img src="images/Method-select-2008.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Locate_installation_media"><p class="title"><b>Locate installation media</b></p><div class="para">
				Select ISO image location or CD-ROM or DVD device. This example uses an ISO file image of the Windows Server 2008 installation CD.
			</div><ol class="a"><li><div class="para">
						Press the <span class="guibutton"><strong>Browse</strong></span> button.
					</div></li><li><div class="para">
						Search to the location of the ISO file and select it. 
						<div class="mediaobject"><img src="images/SelectISO-5.1.png"/></div>
						 Press <span class="guibutton"><strong>Open</strong></span> to confirm your selection.
					</div></li><li><div class="para">
						The file is selected and ready to install from. 
						<div class="mediaobject"><img src="images/Windows2008-selected-5.png"/></div>
						 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
					</div></li></ol><div class="warning"><h2>Image files and SELinux</h2><div class="para">
					For ISO image files and guest storage images, the recommended directory to use is the <code class="filename">/var/lib/libvirt/images/</code> directory. Any other location may require additional configuration for SELinux, refer to <a class="xref" href="chap-Virtualization_Guide-Security_for_virtualization.html#sect-Virtualization_Guide-Security_for_virtualization-SELinux_and_virtualization" title="7.1.Â SELinux and virtualization">SectionÂ 7.1, â€œSELinux and virtualizationâ€</a> for details.
				</div></div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Storage_setup"><p class="title"><b>Storage setup</b></p><div class="para">
				Assign a physical storage device (<span class="guilabel"><strong>Block device</strong></span>) or a file-based image (<span class="guilabel"><strong>File</strong></span>). File-based images must be stored in the <code class="filename">/var/lib/libvirt/images/</code> directory. Assign sufficient storage for your virtualized guest. Assign sufficient space for your virtualized guest and any application it requires. 
				<div class="mediaobject"><img src="images/Storage2008-6.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Network_setup"><p class="title"><b>Network setup</b></p><div class="para">
				Select either <span class="guilabel"><strong>Virtual network</strong></span> or <span class="guilabel"><strong>Shared physical device</strong></span>.
			</div><div class="para">
				The virtual network option uses Network Address Translation (NAT) to share the default network device with the virtualized guest. Use the virtual network option for wireless networks.
			</div><div class="para">
				The shared physical device option uses a network bond to give the virtualized guest full access to a network device. 
				<div class="mediaobject"><img src="images/Network-7.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Memory_and_CPU_allocation"><p class="title"><b>Memory and CPU allocation</b></p><div class="para">
				The Allocate memory and CPU window displays. Choose appropriate values for the virtualized CPUs and RAM allocation. These values affect the host's and guest's performance.
			</div><div class="para">
				Virtualized guests require sufficient physical memory (RAM) to run efficiently and effectively. Choose a memory value which suits your guest operating system and application requirements. Windows Server 2008. Remember, guests use physical RAM. Running too many guests or leaving insufficient memory for the host system results in significant usage of virtual memory and swapping. Virtual memory is significantly slower causing degraded system performance and responsiveness. Ensure to allocate sufficient memory for all guests and the host to operate effectively.
			</div><div class="para">
				Assign sufficient virtual CPUs for the virtualized guest. If the guest runs a multithreaded application assign the number of virtualized CPUs it requires to run most efficiently. Do not assign more virtual CPUs than there are physical processors (or hyper-threads) available on the host system. It is possible to over allocate virtual processors, however, over allocating has a significant, negative affect on guest and host performance due to processor context switching overheads.
			</div><div class="para">
				<div class="mediaobject"><img src="images/Memory_and_CPU-8.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Verify_and_start_guest_installation"><p class="title"><b>Verify and start guest installation</b></p><div class="para">
				Verify the configuration. 
				<div class="mediaobject"><img src="images/Windows-2008-finished-9.png"/></div>
				 Press <span class="guibutton"><strong>Finish</strong></span> to start the guest installation procedure.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_Server_2008_with_virt_manager-Installing_Windows"><p class="title"><b>Installing Windows</b></p><div class="para">
				<div class="mediaobject"><img src="images/2008installing.png"/></div>
				 Complete the Windows Server 2008 installation sequence. The installation sequence is not covered by this guide, refer to Microsoft's <a href="http://microsoft.com/support">documentation</a> for information on installing Windows.
			</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest.html"><strong>Prev</strong>3.4.Â Installing Windows Server 2003 as a fully vi...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Configuration.html"><strong>Next</strong>PartÂ II.Â Configuration</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>3.3.Â Installing Windows XP as a fully virtualized guest</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html" title="ChapterÂ 3.Â Guest operating system installation procedures"/><link rel="prev" href="sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest.html" title="3.2.Â Installing Red Hat Enterprise Linux as a fully virtualized guest"/><link rel="next" href="sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest.html" title="3.4.Â Installing Windows Server 2003 as a fully virtualized guest"/></head><body class="draft "><p id="title"><a class
 ="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest">3.3.Â Installing Windows XP as a fully virtualized guest</h2></div></div></div><div class="para">
		Windows XP can be installed as a fully virtualized guest. This section describes how to install Windows XP as a fully virtualized guest on Linux.
	</div><div class="para">
		Before commencing this procedure ensure you must have root access.
	</div><div class="procedure"><ol class="1"><li id="step-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest-Starting_virt_manager"><p class="title"><b>Starting virt-manager</b></p><div class="para">
				Open <span class="guimenuitem"><strong>Applications > System Tools > Virtual Machine Manager</strong></span>. Open a connection to the host (click <span class="guimenuitem"><strong>File > Open Connection</strong></span>). Click the <span class="guibutton"><strong>New</strong></span> button to create a new virtual machine.
			</div></li><li id="step-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest-Naming_your_virtual_system"><p class="title"><b>Naming your virtual system</b></p><div class="para">
				Enter the <span class="guilabel"><strong>System Name</strong></span> and click the <span class="guibutton"><strong>Forward</strong></span> button.
			</div><div class="mediaobject"><img src="images/windows_system_name.png"/></div></li><li id="step-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest-Choosing_a_virtualization_method"><p class="title"><b>Choosing a virtualization method</b></p><div class="para">
				If you selected KVM or Xen earlier (step <a class="xref" href="sect-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest.html#step-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest-Starting_virt_manager" title="Starting virt-manager">Step 1</a> ) you must use the hypervisor you selected. This example uses the KVM hypervisor.
			</div><div class="para">
				Windows can only be installed using full virtualization.
			</div><div class="mediaobject"><img src="images/KVM-3.png"/></div></li><li id="step-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest-Choosing_an_installation_method"><p class="title"><b>Choosing an installation method</b></p><div class="para">
				This screen enables you to specify the installation method and the type of operating system.
			</div><div class="para">
				For CD-ROM or DVD installation select the device with the Windows installation disc in it. If you chose <span class="guilabel"><strong>ISO Image Location</strong></span> enter the path to a Windows installation .iso image.
			</div><div class="para">
				Select <span class="guilabel"><strong>Windows</strong></span> from the <span class="guilabel"><strong>OS Type</strong></span> list and <span class="guilabel"><strong>Microsoft Windows XP</strong></span> from the <span class="guilabel"><strong>OS Variant</strong></span> list.
			</div><div class="para">
				PXE installation is not covered by this chapter.
			</div><div class="mediaobject"><img src="images/Method-select-xp.png"/></div><div class="para">
				Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div><div class="warning"><h2>Image files and SELinux</h2><div class="para">
					For ISO image files and guest storage images the the recommended to use the <code class="filename">/var/lib/libvirt/images/</code> directory. Any other location may require additional configuration for SELinux, refer to <a class="xref" href="chap-Virtualization_Guide-Security_for_virtualization.html#sect-Virtualization_Guide-Security_for_virtualization-SELinux_and_virtualization" title="7.1.Â SELinux and virtualization">SectionÂ 7.1, â€œSELinux and virtualizationâ€</a> for details.
				</div></div></li><li><div class="para">
				The <span class="guilabel"><strong>Assigning storage space</strong></span> window displays. Choose a disk partition, LUN or create a file based image for the guest storage.
			</div><div class="para">
				The convention for file based images in Fedora is that all file based guest images are in the <code class="filename">/var/lib/libvirt/images/</code> directory. Other directory locations for file based images are prohibited by SELinux. If you run SELinux in enforcing mode, refer to <a class="xref" href="chap-Virtualization_Guide-Security_for_virtualization.html#sect-Virtualization_Guide-Security_for_virtualization-SELinux_and_virtualization" title="7.1.Â SELinux and virtualization">SectionÂ 7.1, â€œSELinux and virtualizationâ€</a> for more information on installing guests.
			</div><div class="para">
				Your guest storage image should be larger than the size of the installation, any additional packages and applications, and the size of the guests swap file. The installation process will choose the size of the guest's swap file based on size of the RAM allocated to the guest.
			</div><div class="para">
				Allocate extra space if the guest needs additional space for applications or other data. For example, web servers require additional space for log files.
			</div><div class="mediaobject"><img src="images/windows_storage_space.png"/></div><div class="para">
				Choose the appropriate size for the guest on your selected storage type and click the <span class="guibutton"><strong>Forward</strong></span> button.
			</div><div class="note"><h2>Note</h2><div class="para">
					It is recommend that you use the default directory for virtual machine images, <code class="filename">/var/lib/libvirt/images/</code>. If you are using a different location (such as <code class="filename">/images/</code> in this example) make sure it is added to your SELinux policy and relabeled before you continue with the installation (later in the document you will find information on how to modify your SELinux policy)
				</div></div></li><li id="step-Virtualization_Guide-Installing_Windows_XP_as_a_fully_virtualized_guest-Network_setup"><p class="title"><b>Network setup</b></p><div class="para">
				Select either <span class="guilabel"><strong>Virtual network</strong></span> or <span class="guilabel"><strong>Shared physical device</strong></span>.
			</div><div class="para">
				The virtual network option uses Network Address Translation (NAT) to share the default network device with the virtualized guest. Use the virtual network option for wireless networks.
			</div><div class="para">
				The shared physical device option uses a network bond to give the virtualized guest full access to a network device. 
				<div class="mediaobject"><img src="images/Network-7.png"/></div>
				 Press <span class="guibutton"><strong>Forward</strong></span> to continue.
			</div></li><li><div class="para">
				The Allocate memory and CPU window displays. Choose appropriate values for the virtualized CPUs and RAM allocation. These values affect the host's and guest's performance.
			</div><div class="para">
				Virtualized guests require sufficient physical memory (RAM) to run efficiently and effectively. Choose a memory value which suits your guest operating system and application requirements. Most operating system require at least 512MB of RAM to work responsively. Remember, guests use physical RAM. Running too many guests or leaving insufficient memory for the host system results in significant usage of virtual memory and swapping. Virtual memory is significantly slower causing degraded system performance and responsiveness. Ensure to allocate sufficient memory for all guests and the host to operate effectively.
			</div><div class="para">
				Assign sufficient virtual CPUs for the virtualized guest. If the guest runs a multithreaded application assign the number of virtualized CPUs it requires to run most efficiently. Do not assign more virtual CPUs than there are physical processors (or hyper-threads) available on the host system. It is possible to over allocate virtual processors, however, over allocating has a significant, negative affect on guest and host performance due to processor context switching overheads.
			</div><div class="mediaobject"><img src="images/Memory_and_CPU-8.png"/></div></li><li><div class="para">
				Before the installation continues you will see the summary screen. Press <span class="guibutton"><strong>Finish</strong></span> to proceed to the guest installation:
			</div><div class="mediaobject"><img src="images/windows_summary.png"/></div></li><li><div class="para">
				You must make a hardware selection so open a console window quickly after the installation starts. Click <span class="guibutton"><strong>Finish</strong></span> then switch to the <span class="application"><strong>virt-manager</strong></span> summary window and select your newly started Windows guest. Double click on the system name and the console window opens. Quickly and repeatedly press <span class="keycap"><strong>F5</strong></span> to select a new <code class="systemitem">HAL</code>, once you get the dialog box in the Windows install select the '<code class="systemitem">Generic i486 Platform</code>' tab (scroll through selections with the <span class="keycap"><strong>Up</strong></span> and <span class="keycap"><strong>Down</strong></span> arrows.
			</div><div class="mediaobject"><img src="images/windows_install_start.png"/></div></li><li><div class="para">
				The installation continues with the standard Windows installation.
			</div><div class="mediaobject"><img src="images/windows_install_1.png"/></div><div class="mediaobject"><img src="images/windows_install_2.png"/></div></li><li><div class="para">
				Partition the hard drive when prompted.
			</div><div class="mediaobject"><img src="images/windows_partition_1.png"/></div><div class="mediaobject"><img src="images/windows_partition_2.png"/></div></li><li><div class="para">
				After the drive is formatted Windows starts copying the files to the hard drive.
			</div><div class="mediaobject"><img src="images/windows_copy_files.png"/></div><div class="mediaobject"><img src="images/windows_copy_files_2.png"/></div></li><li><div class="para">
				The files are copied to the storage device, Windows now reboots.
			</div><div class="mediaobject"><img src="images/windows_reboot.png"/></div></li><li><div class="para">
				Restart your Windows guest:
			</div><pre class="screen"># virsh start <em class="replaceable"><code>WindowsGuest</code></em>
</pre><div class="para">
				Where <em class="replaceable"><code>WindowsGuest</code></em> is the name of your virtual machine.
			</div></li><li><div class="para">
				When the console window opens, you will see the setup phase of the Windows installation.
			</div><div class="mediaobject"><img src="images/windows_continue_setup.png"/></div></li><li><div class="para">
				If your installation seems to get stuck during the setup phase, restart the guest with <code class="command">virsh reboot <em class="replaceable"><code>WindowsGuestName</code></em></code>. The will usually get the installation to continue. As you restart the virtual machine you will see a <code class="computeroutput">Setup is being restarted</code> message:
			</div><div class="mediaobject"><img src="images/windows_setup_restart.png"/></div></li><li><div class="para">
				After setup has finished you will see the Windows boot screen:
			</div><div class="mediaobject"><img src="images/windows_boot_screen.png"/></div></li><li><div class="para">
				Now you can continue with the standard setup of your Windows installation:
			</div><div class="mediaobject"><img src="images/windows_install_setup.png"/></div></li><li><div class="para">
				The setup process is complete, a Windows desktop displays.
			</div><div class="mediaobject"><img src="images/windows_desktop.png"/></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_Red_Hat_Enterprise_Linux_as_a_fully_virtualized_guest.html"><strong>Prev</strong>3.2.Â Installing Red Hat Enterprise Linux as a ful...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_Windows_Server_2003_as_a_fully_virtualized_guest.html"><strong>Next</strong>3.4.Â Installing Windows Server 2003 as a fully vi...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>10.2.Â Installing the Para-virtualized Drivers</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html" title="ChapterÂ 10.Â Xen Para-virtualized Drivers"/><link rel="prev" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html" title="ChapterÂ 10.Â Xen Para-virtualized Drivers"/><link rel="next" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_3.html" title="10.2.2.Â Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 3"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img
  src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_3.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers">10.2.Â Installing the Para-virtualized Drivers</h2></div></div></div><div class="para">
		The following three chapters describe how to install and configure your fully virtualized guests to run on Fedora 12 with para-virtualized drivers.
	</div><div class="important"><h2>Verify your architecture is supported before proceeding</h2><div class="para">
			Para-virtualized drivers are only supported on certain hardware and version combinations. Verify your hardware and operating system requirements are met before proceeding to install para-virtualized drivers.
		</div></div><div class="note"><h2>Maximizing the benefit of the para-virtualized drivers for new installations</h2><div class="para">
			If you are installing a new guest system, in order to gain maximal benefit from the para-virtualized block device drivers, you should create the guest with at least two disks.
		</div><div class="para">
			Using the para-virtualized drivers for the disk that contains the <code class="command">MBR</code> and the boot loader (<code class="command">GRUB</code>), and for the <code class="filename">/boot</code> partition. This partition can be very small, as it only needs to have enough capacity to hold the <code class="filename">/boot</code> partition.
		</div><div class="para">
			Use the second disk and any additional disks for all other partitions (for example, <code class="filename">/</code>, <code class="filename">/usr</code>) or logical volumes.
		</div><div class="para">
			Using this installation method, when the para-virtualized block device drivers are later installed after completing the install of the guest, only booting the guest and accessing the <code class="filename">/boot</code> partition will use the virtualized block device drivers.
		</div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sect-Virtualization_Guide-Installing_the_Para_virtualized_Drivers-Common_installation_steps">10.2.1.Â Common installation steps</h3></div></div></div><div class="para">
			The list below covers the high level steps common across all guest operating system versions.
		</div><div class="procedure"><ol class="1"><li><div class="para">
					Copy the RPMs for your hardware architecture to a suitable location in your guest operating system. Your home directory is sufficient. If you do not know which RPM you require verify against the table at <a class="xref" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html#sect-Virtualization_Guide-Para_virtualization_Restrictions_and_Support" title="10.1.Â Para-virtualization Restrictions and Support">SectionÂ 10.1, â€œPara-virtualization Restrictions and Supportâ€</a>.
				</div></li><li><div class="para">
					Use the <code class="command">rpm</code> utility to install the RPM packages. The <code class="command">rpm</code> utility will install the following four new kernel modules into <code class="filename">/lib/modules/[%kversion][%kvariant]/extra/xenpv/%release</code>: 
					<div class="itemizedlist"><ul><li><div class="para">
								the PCI infrastructure module, <code class="command">xen-platform-pci.ko</code>,
							</div></li><li><div class="para">
								the ballooning module, <code class="command">xen-balloon.ko</code>,
							</div></li><li><div class="para">
								the virtual block device module, <code class="command">xen-vbd.ko</code>,
							</div></li><li><div class="para">
								and the virtual network device module, <code class="command">xen.vnif.ko</code>.
							</div></li></ul></div>
				</div></li><li><div class="para">
					If the guest operating system does not support automatically loading the para-virtualized drivers (for example, Red Hat Enterprise Linux 3) perform the required post-install steps to copy the drivers into the operating system specific locations.
				</div></li><li><div class="para">
					Shut down your guest operating system.
				</div></li><li><div class="para">
					Reconfigure the guest operating system's configuration file on the host to use the installed para-virtualized drivers.
				</div></li><li><div class="para">
					Remove the â€œtype=ioemuâ€ entry for the network device.
				</div></li><li><div class="para">
					Add any additional storage entities you want to use for the para-virtualized block device driver.
				</div></li><li><div class="para">
					Restart your guest:
				</div><pre class="screen"># virsh start <em class="replaceable"><code>YourGuestName</code></em>
</pre><div class="para">
					Where <em class="replaceable"><code>YourGuestName</code></em> is the name of the guest operating system.
				</div></li><li><div class="para">
					Reconfigure the guest network
				</div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html"><strong>Prev</strong>ChapterÂ 10.Â Xen Para-virtualized Drivers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_3.html"><strong>Next</strong>10.2.2.Â Installation and Configuration of Para-vi...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>1.4.Â Installing KVM packages on an existing Fedora system</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html" title="ChapterÂ 1.Â Installing the virtualization packages"/><link rel="prev" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation.html" title="1.3.Â Installing KVM with a new Fedora installation"/><link rel="next" href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html" title="ChapterÂ 2.Â Virtualized guest installation overview"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><i
 mg src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></div></div><div class="para">
			The section describes the steps for installing the KVM hypervisor on a working Fedora 12 or newer.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installing_KVM_packages_on_an_existing_Fedora_system-Installing_the_KVM_hypervisor_with_yum">Installing the KVM hypervisor with <code class="command">yum</code></h5>
				To use virtualization on Fedora you require the <code class="filename">kvm</code> package. The <code class="filename">kvm</code> package contains the KVM kernel module providing the KVM hypervisor on the default Linux kernel.
			</div><div class="para">
			To install the <code class="filename">kvm</code> package, run: 
<pre class="screen"># yum install kvm
</pre>
		</div><div class="para">
			Now, install additional virtualization management packages.
		</div><div class="variablelist" id="vari-Virtualization_Guide-Installing_KVM_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><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation.html"><strong>Prev</strong>1.3.Â Installing KVM with a new Fedora installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html"><strong>Next</strong>ChapterÂ 2.Â Virtualized guest installation overview</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>1.3.Â Installing KVM with a new Fedora installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html" title="ChapterÂ 1.Â Installing the virtualization packages"/><link rel="prev" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system.html" title="1.2.Â Installing Xen packages on an existing Fedora system"/><link rel="next" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system.html" title="1.4.Â Installing KVM packages on an existing Fedora system"/></head><body class="draft "><p 
 id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system.html"><strong>Next</strong></a></li></ul><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.
				</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>KVM</strong></span> package group. Deselect the <span class="guilabel"><strong>Virtualization</strong></span> package group. This selects the KVM 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/RHELkvmSelect.png"/></div></li><li id="step-Virtualization_Guide-Installing_KVM_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/RHELKVMpackages.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_KVM_with_a_new_Fedora_installation-Installing_KVM_packages_with_Kickstart_files">Installing KVM packages with Kickstart files</h5>
				This section describes how to use a Kickstart file to install Fedora with the KVM 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
@kvm
</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><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system.html"><strong>Prev</strong>1.2.Â Installing Xen packages on an existing Fedor...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system.html"><strong>Next</strong>1.4.Â Installing KVM packages on an existing Fedor...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_Xen_packages_on_an_existing_Fedora_system.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>1.2.Â Installing Xen packages on an existing Fedora system</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html" title="ChapterÂ 1.Â Installing the virtualization packages"/><link rel="prev" href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html" title="ChapterÂ 1.Â Installing the virtualization packages"/><link rel="next" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation.html" title="1.3.Â Installing KVM with a new Fedora installation"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img
  src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation.html"><strong>Next</strong></a></li></ul><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="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_packages_on_an_existing_Fedora_system.html#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><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Installing_the_virtualization_packages.html"><strong>Prev</strong>ChapterÂ 1.Â Installing the virtualization packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Installing_the_virtualization_packages-Installing_KVM_with_a_new_Fedora_installation.html"><strong>Next</strong>1.3.Â Installing KVM with a new Fedora installation</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-KVM_live_migration-Live_KVM_migration_with_virsh.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>15.3.Â Live KVM migration with virsh</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-KVM_live_migration.html" title="ChapterÂ 15.Â KVM live migration"/><link rel="prev" href="sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration.html" title="15.2.Â Share storage example: NFS for a simple migration"/><link rel="next" href="sect-Virtualization_Guide-KVM_live_migration-Migrating_with_virt_manager.html" title="15.4.Â Migrating with virt-manager"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="righ
 t" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-KVM_live_migration-Live_KVM_migration_with_virsh">15.3.Â Live KVM migration with virsh</h2></div></div></div><div class="para">
			A guest can be migrated to another host with the <code class="command">virsh</code> command. The <code class="command">migrate</code> command accepts parameters in the following format:
		</div><pre class="screen"># virsh migrate --live <em class="parameter"><code>GuestName DestinationURL</code></em>
</pre><div class="para">
			The <em class="parameter"><code>GuestName</code></em> parameter represents the name of the guest which you want to migrate.
		</div><div class="para">
			The <em class="parameter"><code>DestinationURL</code></em> parameter is the URL or hostname of the destination system. The destination system must run the same version of Fedora, be using the same hypervisor and have <code class="command">libvirt</code> running.
		</div><div class="para">
			Once the command is entered you will be prompted for the root password of the destination system.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Live_KVM_migration_with_virsh-Example_live_migration_with_virsh">Example: live migration with virsh</h5>
				This example migrates from <code class="systemitem">test1.bne.redhat.com</code> to <code class="systemitem">test2.bne.redhat.com</code>. Change the host names for your environment. This example migrates a virtual machine named <code class="filename">CentOS4test</code>.
			</div><div class="para">
			This example assumes you have fully configured shared storage and meet all the prerequisites (listed here: <a class="xref" href="chap-Virtualization_Guide-KVM_live_migration.html#item-Virtualization_Guide-Live_migration_requirements-Migration_requirements" title="Migration requirements">Migration requirements</a>).
		</div><div class="procedure"><ol class="1"><li id="step-Virtualization_Guide-Live_KVM_migration_with_virsh-Verify_the_guest_is_running"><p class="title"><b>Verify the guest is running</b></p><div class="para">
					From the source system, <code class="systemitem">test1.bne.redhat.com</code>, verify <code class="systemitem">CentOS4test</code> is running:
				</div><pre class="screen">[root at test1 ~]# virsh list
Id Name                 State
----------------------------------
 10 CentOS4                running
</pre></li><li id="step-Virtualization_Guide-Live_KVM_migration_with_virsh-Migrate_the_guest"><p class="title"><b>Migrate the guest</b></p><div class="para">
					Execute the following command to live migrate the guest to the destination, <code class="systemitem">test2.bne.redhat.com</code>. Append <code class="filename">/system</code> to the end of the destination URL to tell libvirt that you need full access.
				</div><pre class="screen"># virsh migrate --live <em class="parameter"><code>CentOS4test qemu+ssh://test2.bne.redhat.com/system</code></em>
</pre><div class="para">
					Once the command is entered you will be prompted for the root password of the destination system.
				</div></li><li id="step-Virtualization_Guide-Live_KVM_migration_with_virsh-Wait"><p class="title"><b>Wait</b></p><div class="para">
					The migration may take some time depending on load and the size of the guest. <code class="command">virsh</code> only reports errors. The guest continues to run on the source host until fully migrated.
				</div></li><li id="step-Virtualization_Guide-Live_KVM_migration_with_virsh-Verify_the_guest_has_arrived_at_the_destination_host"><p class="title"><b>Verify the guest has arrived at the destination host</b></p><div class="para">
					From the destination system, <code class="systemitem">test2.bne.redhat.com</code>, verify <code class="systemitem">CentOS4test</code> is running:
				</div><pre class="screen">[root at test2 ~]# virsh list
Id Name                 State
----------------------------------
 10 CentOS4                running
</pre></li></ol></div><div class="para">
			The live migration is now complete.
		</div><div class="note"><h2>Other networking methods</h2><div class="para">
				libvirt supports a variety of networking methods including TLS/SSL, unix sockets, SSH, and unecrypted TCP. Refer to <a class="xref" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html" title="ChapterÂ 16.Â Remote management of virtualized guests">ChapterÂ 16, <i>Remote management of virtualized guests</i></a> for more information on using other methods.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration.html"><strong>Prev</strong>15.2.Â Share storage example: NFS for a simple mig...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Next</strong>15.4.Â Migrating with virt-manager</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-KVM_live_migration-Migrating_with_virt_manager.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>15.4.Â Migrating with virt-manager</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-KVM_live_migration.html" title="ChapterÂ 15.Â KVM live migration"/><link rel="prev" href="sect-Virtualization_Guide-KVM_live_migration-Live_KVM_migration_with_virsh.html" title="15.3.Â Live KVM migration with virsh"/><link rel="next" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html" title="ChapterÂ 16.Â Remote management of virtualized guests"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedorapr
 oject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-KVM_live_migration-Migrating_with_virt_manager">15.4.Â Migrating with virt-manager</h2></div></div></div><div class="para">
			This section covers migrating KVM based guests with <code class="command">virt-manager</code>.
		</div><div class="procedure"><ol class="1"><li><div class="para">
					Connect to the source and target hosts. On the <span class="guimenu"><strong>File</strong></span> menu, click <span class="guimenuitem"><strong>Add Connection</strong></span>, the <span class="guilabel"><strong>Add Connection</strong></span> window appears.
				</div><div class="para">
					Enter the following details:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<span class="guilabel"><strong>Hypervisor</strong></span>: Select <span class="guimenuitem"><strong>QEMU</strong></span>.
						</div></li><li><div class="para">
							<span class="guilabel"><strong>Connection</strong></span>: Select the connection type.
						</div></li><li><div class="para">
							<span class="guilabel"><strong>Hostname</strong></span>: Enter the hostname.
						</div></li></ul></div><div class="para">
					Click <span class="guibutton"><strong>Connect</strong></span>.
				</div><div class="mediaobject"><img src="images/step1-1.png"/></div><div class="para">
					The Virtual Machine Manager displays a list of connected hosts.
				</div><div class="mediaobject"><img src="images/step1-2.png"/></div></li><li><div class="para">
					Add a storage pool with the same NFS to the source and target hosts.
				</div><div class="para">
					On the <span class="guimenu"><strong>Edit</strong></span> menu, click <span class="guimenuitem"><strong>Host Details</strong></span>, the Host Details window appears.
				</div><div class="para">
					Click the <span class="guibutton"><strong>Storage</strong></span> tab.
				</div><div class="mediaobject"><img src="images/step2-1.png"/></div></li><li><div class="para">
					Add a new storage pool. In the lower left corner of the window, click the <span class="guibutton"><strong>+</strong></span> button. The Add a New Storage Pool window appears.
				</div><div class="para">
					Enter the following details:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<span class="guilabel"><strong>Name</strong></span>: Enter the name of the storage pool.
						</div></li><li><div class="para">
							<span class="guilabel"><strong>Type</strong></span>: Select <span class="guimenuitem"><strong>netfs: Network Exported Directory</strong></span>.
						</div></li></ul></div><div class="mediaobject"><img src="images/step2-2.png"/></div><div class="para">
					Click <span class="guibutton"><strong>Forward</strong></span>.
				</div></li><li><div class="para">
					Enter the following details:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<span class="guilabel"><strong>Format</strong></span>: Select the storage type. This must be NFS or iSCSI for live migrations.
						</div></li><li><div class="para">
							<span class="guilabel"><strong>Host Name</strong></span>: Enter the IP address or fully-qualified domain name of the storage server.
						</div></li></ul></div><div class="mediaobject"><img src="images/step2-3.png"/></div><div class="para">
					Click <span class="guibutton"><strong>Finish</strong></span>.
				</div></li><li><div class="para">
					Create a new volume in the shared storage pool, click <span class="guibutton"><strong>New Volume</strong></span>.
				</div><div class="mediaobject"><img src="images/step2-4.png"/></div></li><li><div class="para">
					Enter the details, then click <span class="guibutton"><strong>Create Volume</strong></span>.
				</div><div class="mediaobject"><img src="images/step3-1.png"/></div></li><li><div class="para">
					Create a virtual machine with the new volume, then run the virtual machine.
				</div><div class="mediaobject"><img src="images/step4-1.png"/></div><div class="para">
					The Virtual Machine window appears.
				</div><div class="mediaobject"><img src="images/step4-2.png"/></div></li><li><div class="para">
					In the Virtual Machine Manager window, right-click on the virtual machine, select <span class="guimenuitem"><strong>Migrate</strong></span>, then click the migration location.
				</div><div class="mediaobject"><img src="images/step5-2.png"/></div></li><li><div class="para">
					Click <span class="guibutton"><strong>Yes</strong></span> to confirm migration.
				</div><div class="mediaobject"><img src="images/step5-3.png"/></div><div class="para">
					The Virtual Machine Manger displays the virtual machine in its new location.
				</div><div class="mediaobject"><img src="images/step6-1.png"/></div><div class="para">
					The Virtual Machine window displays the new virtual machine location.
				</div><div class="mediaobject"><img src="images/step6-2.png"/></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Prev</strong>15.3.Â Live KVM migration with virsh</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html"><strong>Next</strong>ChapterÂ 16.Â Remote management of virtualized gues...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>15.2.Â Share storage example: NFS for a simple migration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-KVM_live_migration.html" title="ChapterÂ 15.Â KVM live migration"/><link rel="prev" href="chap-Virtualization_Guide-KVM_live_migration.html" title="ChapterÂ 15.Â KVM live migration"/><link rel="next" href="sect-Virtualization_Guide-KVM_live_migration-Live_KVM_migration_with_virsh.html" title="15.3.Â Live KVM migration with virsh"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src=
 "Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-KVM_live_migration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-KVM_live_migration-Share_storage_example_NFS_for_a_simple_migration">15.2.Â Share storage example: NFS for a simple migration</h2></div></div></div><div class="para">
			This example uses NFS to share guest images with other KVM hosts. This example is not practical for large installations, this example is only for demonstrating migration techniques and small deployments. Do not use this example for migrating or running more than a few virtualized guests.
		</div><div class="para">
			For advanced and more robust shared storage instructions, refer to <a class="xref" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html" title="ChapterÂ 5.Â Shared storage and virtualization">ChapterÂ 5, <i>Shared storage and virtualization</i></a>
		</div><div class="procedure"><ol class="1"><li id="step-Virtualization_Guide-Share_storage_example_NFS_for_a_simple_migration-Export_your_libvirt_image_directory"><p class="title"><b>Export your libvirt image directory</b></p><div class="para">
					Add the default image directory to the <code class="filename">/etc/exports</code> file:
				</div><pre class="screen">/var/lib/libvirt/images <em class="parameter"><code>*.bne.redhat.com</code></em>(rw,no_root_squash,async)
</pre><div class="para">
					Change the hosts parameter as required for your environment.
				</div></li><li id="step-Virtualization_Guide-Share_storage_example_NFS_for_a_simple_migration-Start_NFS"><p class="title"><b>Start NFS</b></p><ol class="a"><li><div class="para">
							Install the NFS packages if they are not yet installed:
						</div><pre class="screen"># yum install nfs
</pre></li><li><div class="para">
							Open the ports for NFS in <code class="command">iptables</code> and add NFS to the <code class="filename">/etc/hosts.allow</code> file.
						</div></li><li><div class="para">
							Start the NFS service:
						</div><pre class="screen"># service nfs start
</pre></li></ol></li><li id="step-Virtualization_Guide-Share_storage_example_NFS_for_a_simple_migration-Mount_the_shared_storage_on_the_destination"><p class="title"><b>Mount the shared storage on the destination</b></p><div class="para">
					On the destination system, mount the <code class="filename">/var/lib/libvirt/images</code> directory:
				</div><pre class="screen"># mount <em class="parameter"><code>sourceURL</code></em>:/var/lib/libvirt/images /var/lib/libvirt/images
</pre><div class="warning"><h2>Locations must be the same on source and destination</h2><div class="para">
						Whichever directory is chosen for the guests must exactly the same on host and guest. This applies to all types of shared storage. The directory must be the same or the migration will fail.
					</div></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-KVM_live_migration.html"><strong>Prev</strong>ChapterÂ 15.Â KVM live migration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Next</strong>15.3.Â Live KVM migration with virsh</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Creating_a_virtual_network.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.15.Â Creating a virtual network</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network.html" title="19.14.Â Managing a virtual network"/><link rel="next" href="chap-Virtualization_Guide-The_xm_command_quick_reference.html" title="ChapterÂ 20.Â The xm command quick reference"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img sr
 c="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-The_xm_command_quick_reference.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Creating_a_virtual_network">19.15.Â Creating a virtual network</h2></div></div></div><div class="para">
			To create a virtual network on your system:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					Open the <span class="guilabel"><strong>Host Details</strong></span> menu (refer to <a class="xref" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network.html" title="19.14.Â Managing a virtual network">SectionÂ 19.14, â€œManaging a virtual networkâ€</a>) and click the <span class="guibutton"><strong>Add</strong></span> button.
				</div><div class="figure" id="figu-Virtualization_Guide-Creating_a_virtual_network-Virtual_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_maintab.png" alt="Virtual network configuration"/></div></div><h6>FigureÂ 19.30.Â Virtual network configuration</h6></div><br class="figure-break"/><div class="para">
					This will open the <span class="guimenu"><strong>Create a new virtual network</strong></span> menu. Click <span class="guibutton"><strong>Forward</strong></span> to continue.
				</div><div class="figure" id="figu-Virtualization_Guide-Creating_a_virtual_network-Creating_a_new_virtual_network"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_create1.png" alt="Creating a new virtual network"/></div></div><h6>FigureÂ 19.31.Â Creating a new virtual network</h6></div><br class="figure-break"/></li><li><div class="para">
					Enter an appropriate name for your virtual network and click <span class="guibutton"><strong>Forward</strong></span>.
				</div><div class="figure" id="figu-Virtualization_Guide-Creating_a_virtual_network-Naming_your_virtual_network"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_create2.png" alt="Naming your virtual network"/></div></div><h6>FigureÂ 19.32.Â Naming your virtual network</h6></div><br class="figure-break"/></li><li><div class="para">
					Enter an IPv4 address space for your virtual network and click <span class="guibutton"><strong>Forward</strong></span>.
				</div><div class="figure" id="figu-Virtualization_Guide-Creating_a_virtual_network-Choosing_an_IPv4_address_space"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_create3_ipv4addspace.png" alt="Choosing an IPv4 address space"/></div></div><h6>FigureÂ 19.33.Â Choosing an IPv4 address space</h6></div><br class="figure-break"/></li><li><div class="para">
					Define the DHCP range for your virtual network by specifying a <span class="guilabel"><strong>Start</strong></span> and <span class="guilabel"><strong>End</strong></span> range of IP addresses. Click <span class="guibutton"><strong>Forward</strong></span> to continue.
				</div><div class="figure" id="figu-Virtualization_Guide-Creating_a_virtual_network-Selecting_the_DHCP_range"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_create4_dhcprange.png" alt="Selecting the DHCP range"/></div></div><h6>FigureÂ 19.34.Â Selecting the <code class="systemitem">DHCP</code> range</h6></div><br class="figure-break"/></li><li><div class="para">
					Select how the virtual network should connect to the physical network.
				</div><div class="figure" id="figu-Virtualization_Guide-Creating_a_virtual_network-Connecting_to_physical_network"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_create5_connectphysnet.png" alt="Connecting to physical network"/></div></div><h6>FigureÂ 19.35.Â Connecting to physical network</h6></div><br class="figure-break"/><div class="para">
					If you select <span class="guilabel"><strong>Forwarding to physical network</strong></span>, choose whether the <span class="guilabel"><strong>Destination</strong></span> should be <span class="guilabel"><strong>NAT to any physical device</strong></span> or <span class="guilabel"><strong>NAT to physical device eth0</strong></span>.
				</div><div class="para">
					Click <span class="guibutton"><strong>Forward</strong></span> to continue.
				</div></li><li><div class="para">
					You are now ready to create the network. Check the configuration of your network and click <span class="guibutton"><strong>Finish</strong></span>.
				</div><div class="figure" id="figu-Virtualization_Guide-Creating_a_virtual_network-Ready_to_create_network"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_create6_finish.png" alt="Ready to create network"/></div></div><h6>FigureÂ 19.36.Â Ready to create network</h6></div><br class="figure-break"/></li><li><div class="para">
					The new virtual network is now available in the <span class="guimenu"><strong>Virtual Network</strong></span> tab of the <span class="guimenu"><strong>Host Details</strong></span> menu.
				</div><div class="figure" id="figu-Virtualization_Guide-Creating_a_virtual_network-New_virtual_network_is_now_available"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_create7_maintab.png" alt="New virtual network is now available"/></div></div><h6>FigureÂ 19.37.Â New virtual network is now available</h6></div><br class="figure-break"/></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network.html"><strong>Prev</strong>19.14.Â Managing a virtual network</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-The_xm_command_quick_reference.html"><strong>Next</strong>ChapterÂ 20.Â The xm command quick reference</a></li></ul></body></htm
 l>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.12.Â Displaying CPU usage</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_.html" title="19.11.Â Displaying virtual CPUs"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_memory_usage_.html" title="19.13.Â Displaying memory usage"/></head><body class="draft "><p id="title"><a class="left" href="http:
 //www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_memory_usage_.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage">19.12.Â Displaying CPU usage</h2></div></div></div><div class="para">
			To view the CPU usage for all virtual machines on your system:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					From the <span class="guilabel"><strong>View</strong></span> menu, select the <span class="guilabel"><strong>CPU Usage</strong></span> check box.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_CPU_usage-Selecting_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_viewcpu_menu.png" alt="Selecting CPU usage"/></div></div><h6>FigureÂ 19.24.Â Selecting CPU usage</h6></div><br class="figure-break"/></li><li><div class="para">
					The Virtual Machine Manager lists the percentage of CPU in use for all virtual machines on your system.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_CPU_usage-Displaying_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_viewcpu.png" alt="Displaying CPU usage"/></div></div><h6>FigureÂ 19.25.Â Displaying CPU usage</h6></div><br class="figure-break"/></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_.html"><strong>Prev</strong>19.11.Â Displaying virtual CPUs </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_memory_usage_.html"><strong>Next</strong>19.13.Â Displaying memory usage </a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_a_guests_status_.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.10.Â Displaying a guest's status</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers.html" title="19.9.Â Displaying guest identifiers"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_.html" title="19.11.Â Displaying virtual CPUs"/></head><body class="draft "><p id="title"><a class="le
 ft" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_a_guests_status_">19.10.Â Displaying a guest's status </h2></div></div></div><div class="procedure"><div class="para">
				To view the status of all virtual machines on your system:
			</div><ol class="1"><li><div class="para">
					From the <span class="guilabel"><strong>View</strong></span> menu, select the <span class="guilabel"><strong>Status</strong></span> check box.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_a_guests_status_-Selecting_a_virtual_machines_status"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_viewdomstatus_menu.png" alt="Selecting a virtual machine's status"/></div></div><h6>FigureÂ 19.20.Â Selecting a virtual machine's status</h6></div><br class="figure-break"/></li><li><div class="para">
					The Virtual Machine Manager lists the status of all virtual machines on your system.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_a_guests_status_-Displaying_a_virtual_machines_status"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_viewdomstatus.png" alt="Displaying a virtual machine's status"/></div></div><h6>FigureÂ 19.21.Â Displaying a virtual machine's status</h6></div><br class="figure-break"/></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers.html"><strong>Prev</strong>19.9.Â Displaying guest identifiers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_.html"><strong>Next</strong>19.11.Â Display
 ing virtual CPUs </a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.7.Â Displaying guest details</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Restoring_a_saved_machine_.html" title="19.6.Â Restoring a saved machine"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html" title="19.8.Â Status monitoring"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fe
 doraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Restoring_a_saved_machine_.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details">19.7.Â Displaying guest details</h2></div></div></div><div class="para">
			You can use the Virtual Machine Monitor to view activity data information for any virtual machines on your system.
		</div><div class="para">
			To view a virtual system's details:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					In the Virtual Machine Manager main window, highlight the virtual machine that you want to view.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_guest_details-Selecting_a_virtual_machine_to_display_"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_main.png" alt="Selecting a virtual machine to display"/></div></div><h6>FigureÂ 19.8.Â Selecting a virtual machine to display </h6></div><br class="figure-break"/></li><li><div class="para">
					From the Virtual Machine Manager <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Machine Details </strong></span>(or click the <span class="guilabel"><strong>Details</strong></span> button on the bottom of the Virtual Machine Manager main window).
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_guest_details-Displaying_virtual_machine_details_menu"><div class="figure-contents"><div class="mediaobject"><img src="images/display_vmm_menu.png" alt="Displaying virtual machine details menu"/></div></div><h6>FigureÂ 19.9.Â Displaying virtual machine details menu</h6></div><br class="figure-break"/><div class="para">
					The Virtual Machine Details Overview window appears. This window summarizes CPU and memory usage for the domains you specified.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_guest_details-Displaying_guest_details_overview"><div class="figure-contents"><div class="mediaobject"><img src="images/virtual_machine_details.png" alt="Displaying guest details overview"/></div></div><h6>FigureÂ 19.10.Â Displaying guest details overview</h6></div><br class="figure-break"/></li><li><div class="para">
					On the <span class="guilabel"><strong>Virtual Machine Details</strong></span> window, click the <span class="guilabel"><strong>Hardware</strong></span>tab.
				</div><div class="para">
					The <span class="guilabel"><strong>Virtual Machine Details Hardware</strong></span> window appears.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_guest_details-Displaying_guest_hardware_details_"><div class="figure-contents"><div class="mediaobject"><img src="images/hardware_vmm_tab.png" alt="Displaying guest hardware details"/></div></div><h6>FigureÂ 19.11.Â Displaying guest hardware details </h6></div><br class="figure-break"/></li><li><div class="para">
					On the <span class="guilabel"><strong>Hardware</strong></span> tab, click on <span class="guilabel"><strong>Processor</strong></span> to view or change the current processor allocation.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_guest_details-Processor_allocation_panel"><div class="figure-contents"><div class="mediaobject"><img src="images/processor_hw_panel.png" alt="Processor allocation panel"/></div></div><h6>FigureÂ 19.12.Â Processor allocation panel</h6></div><br class="figure-break"/></li><li><div class="para">
					On the <span class="guilabel"><strong>Hardware</strong></span> tab, click on <span class="guilabel"><strong>Memory</strong></span> to view or change the current RAM memory allocation.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_guest_details-Displaying_memory_allocation"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_memory.png" alt="Displaying memory allocation"/></div></div><h6>FigureÂ 19.13.Â Displaying memory allocation</h6></div><br class="figure-break"/></li><li><div class="para">
					On the<span class="guilabel"><strong> Hardware</strong></span> tab, click on <span class="guilabel"><strong>Disk </strong></span>to view or change the current hard disk configuration.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_guest_details-Displaying_disk_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_disk.png" alt="Displaying disk configuration"/></div></div><h6>FigureÂ 19.14.Â Displaying disk configuration</h6></div><br class="figure-break"/></li><li><div class="para">
					On the <span class="guilabel"><strong>Hardware</strong></span> tab, click on <span class="guilabel"><strong>Network</strong></span> to view or change the current network configuration.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_guest_details-Displaying_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_network.png" alt="Displaying network configuration"/></div></div><h6>FigureÂ 19.15.Â Displaying network configuration</h6></div><br class="figure-break"/></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Restoring_a_saved_machine_.html"><strong>Prev</strong>19.6.Â Restoring a saved machine </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html"><strong>Next</strong>19.8.Â Status monitoring</a></li></ul></body></ht
 ml>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.9.Â Displaying guest identifiers</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html" title="19.8.Â Status monitoring"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_a_guests_status_.html" title="19.10.Â Displaying a guest's status"/></head><body class="draft "><p id="title"><a class="left" href="http:
 //www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_a_guests_status_.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers">19.9.Â Displaying guest identifiers</h2></div></div></div><div class="para">
			To view the guest IDs for all virtual machines on your system:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					From the <span class="guilabel"><strong>View</strong></span> menu, select the <span class="guilabel"><strong>Domain ID</strong></span> check box.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_guest_identifiers-Viewing_guest_IDs"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_viewdomid_menu.png" alt="Viewing guest IDs"/></div></div><h6>FigureÂ 19.18.Â Viewing guest IDs</h6></div><br class="figure-break"/></li><li><div class="para">
					The Virtual Machine Manager lists the Domain IDs for all domains on your system.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_guest_identifiers-Displaying_domain_IDs"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_viewdomid.png" alt="Displaying domain IDs"/></div></div><h6>FigureÂ 19.19.Â Displaying domain IDs</h6></div><br class="figure-break"/></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html"><strong>Prev</strong>19.8.Â Status monitoring</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_a_guests_status_.html"><strong>Next</strong>19.10.Â Displaying a guest's status </a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_memory_usage_.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.13.Â Displaying memory usage</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html" title="19.12.Â Displaying CPU usage"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network.html" title="19.14.Â Managing a virtual network"/></head><body class="draft "><p id="title"><a class="left" href="http
 ://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_memory_usage_">19.13.Â Displaying memory usage </h2></div></div></div><div class="para">
			To view the memory usage for all virtual machines on your system:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					From the <span class="guilabel"><strong>View</strong></span> menu, select the <span class="guilabel"><strong>Memory Usage</strong></span> check box.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_memory_usage_-Selecting_Memory_Usage"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_viewmem_menu.png" alt="Selecting Memory Usage"/></div></div><h6>FigureÂ 19.26.Â Selecting Memory Usage</h6></div><br class="figure-break"/></li><li><div class="para">
					The Virtual Machine Manager lists the percentage of memory in use (in megabytes) for all virtual machines on your system.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_memory_usage_-Displaying_memory_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_viewmem.png" alt="Displaying memory usage"/></div></div><h6>FigureÂ 19.27.Â Displaying memory usage</h6></div><br class="figure-break"/></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html"><strong>Prev</strong>19.12.Â Displaying CPU usage</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network.html"><strong>Next</strong>19.14.Â Managing a virtual network</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.11.Â Displaying virtual CPUs</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_a_guests_status_.html" title="19.10.Â Displaying a guest's status"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html" title="19.12.Â Displaying CPU usage"/></head><body class="draft "><p id="title"><a class="left" href="ht
 tp://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_a_guests_status_.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_">19.11.Â Displaying virtual CPUs </h2></div></div></div><div class="para">
			To view the amount of virtual CPUs for all virtual machines on your system:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					From the <span class="guilabel"><strong>View</strong></span> menu, select the <span class="guilabel"><strong>Virtual CPUs</strong></span> check box.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_virtual_CPUs_-Selecting_the_virtual_CPUs_option"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_viewvcpus_menu.png" alt="Selecting the virtual CPUs option"/></div></div><h6>FigureÂ 19.22.Â Selecting the virtual CPUs option</h6></div><br class="figure-break"/></li><li><div class="para">
					The Virtual Machine Manager lists the Virtual CPUs for all virtual machines on your system.
				</div><div class="figure" id="figu-Virtualization_Guide-Displaying_virtual_CPUs_-Displaying_Virtual_CPUs"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_viewvcpus.png" alt="Displaying Virtual CPUs"/></div></div><h6>FigureÂ 19.23.Â Displaying Virtual CPUs</h6></div><br class="figure-break"/></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_a_guests_status_.html"><strong>Prev</strong>19.10.Â Displaying a guest's status </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html"><strong>Next</strong>19.12.Â Displaying CPU usage</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.14.Â Managing a virtual network</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_memory_usage_.html" title="19.13.Â Displaying memory usage"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Creating_a_virtual_network.html" title="19.15.Â Creating a virtual network"/></head><body class="draft "><p id="title"><a class="left" 
 href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_memory_usage_.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Creating_a_virtual_network.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Managing_a_virtual_network">19.14.Â Managing a virtual network</h2></div></div></div><div class="para">
			To configure a virtual network on your system:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					From the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Host Details</strong></span>.
				</div><div class="figure" id="figu-Virtualization_Guide-Managing_a_virtual_network-Selecting_a_hosts_details"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_menuselect.png" alt="Selecting a host's details"/></div></div><h6>FigureÂ 19.28.Â Selecting a host's details</h6></div><br class="figure-break"/></li><li><div class="para">
					This will open the <span class="guimenu"><strong>Host Details</strong></span> menu. Click the <span class="guilabel"><strong>Virtual Networks</strong></span> tab.
				</div><div class="figure" id="figu-Virtualization_Guide-Managing_a_virtual_network-Virtual_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_maintab.png" alt="Virtual network configuration"/></div></div><h6>FigureÂ 19.29.Â Virtual network configuration</h6></div><br class="figure-break"/></li><li><div class="para">
					All available virtual networks are listed on the left-hand box of the menu. You can edit the configuration of a virtual network by selecting it from this box and editing as you see fit.
				</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_memory_usage_.html"><strong>Prev</strong>19.13.Â Displaying memory usage </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Creating_a_virtual_network.html"><strong>Next</strong>19.15.Â Creating a virtual network</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Restoring_a_saved_machine_.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.6.Â Restoring a saved machine</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager.html" title="19.5.Â Starting virt-manager"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html" title="19.7.Â Displaying guest details"/></head><body class="draft "><p id="title"><a class="left" href="http://
 www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Restoring_a_saved_machine_">19.6.Â Restoring a saved machine </h2></div></div></div><div class="para">
			After you start the Virtual Machine Manager, all virtual machines on your system are displayed in the main window. Domain0 is your host system. If there are no machines present, this means that currently there are no machines running on the system.
		</div><div class="para">
			To restore a previously saved session:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					From the <span class="guilabel"><strong>File</strong></span> menu, select <span class="guilabel"><strong> Restore a saved machine</strong></span>.
				</div><div class="figure" id="figu-Virtualization_Guide-Restoring_a_saved_machine_-Restoring_a_virtual_machine"><div class="figure-contents"><div class="mediaobject"><img src="images/restore_vmm_menu.png" alt="Restoring a virtual machine"/></div></div><h6>FigureÂ 19.6.Â Restoring a virtual machine</h6></div><br class="figure-break"/></li><li><div class="para">
					The <span class="guilabel"><strong>Restore Virtual Machine</strong></span> main window appears.
				</div></li><li><div class="para">
					Navigate to correct directory and select the saved session file.
				</div></li><li><div class="para">
					Click <span class="guilabel"><strong>Open</strong></span>.
				</div></li></ol></div><div class="para">
			The saved virtual system appears in the Virtual Machine Manager main window.
		</div><div class="figure" id="figu-Virtualization_Guide-Restoring_a_saved_machine_-A_restored_virtual_machine_manager_session"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_main.png" alt="A restored virtual machine manager session"/></div></div><h6>FigureÂ 19.7.Â A restored virtual machine manager session</h6></div><br class="figure-break"/></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager.html"><strong>Prev</strong>19.5.Â Starting virt-manager</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html"><strong>Next</strong>19.7.Â Displaying guest details</a></li></
 ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.5.Â Starting virt-manager</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html" title="19.4.Â Virtual Machine graphical console"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Restoring_a_saved_machine_.html" title="19.6.Â Restoring a saved machine"/></head><body class="draft "><p id="title"><a cl
 ass="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Restoring_a_saved_machine_.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager">19.5.Â Starting virt-manager</h2></div></div></div><div class="para">
			To start <code class="command">virt-manager</code> session open the <span class="guimenuitem"><strong>Applications</strong></span> menu, then the <span class="guimenuitem"><strong>System Tools</strong></span> menu and select <span class="guimenuitem"><strong>Virtual Machine Manager</strong></span> (<code class="command">virt-manager</code>).
		</div><div class="para">
			The <code class="command">virt-manager</code> main window appears.
		</div><div class="figure" id="figu-Virtualization_Guide-Starting_virt_manager-Starting_virt_manager"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_main.png" alt="Starting virt-manager"/></div></div><h6>FigureÂ 19.5.Â Starting <code class="command">virt-manager</code></h6></div><br class="figure-break"/><div class="para">
			Alternatively, <code class="command">virt-manager</code> can be started remotely using ssh as demonstrated in the following command: 
<pre class="screen">ssh -X <em class="replaceable"><code>host's address</code></em>[remotehost]# virt-manager
</pre>
			 Using <code class="command">ssh</code> to manage virtual machines and hosts is discussed further in <a class="xref" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_with_SSH" title="16.1.Â Remote management with SSH">SectionÂ 16.1, â€œRemote management with SSHâ€</a>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html"><strong>Prev</strong>19.4.Â Virtual Machine graphical console </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Restoring_a_saved_machine_.html"><strong>Next</strong>19.6.Â Restoring a saved machine </a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.8.Â Status monitoring</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html" title="19.7.Â Displaying guest details"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers.html" title="19.9.Â Displaying guest identifiers"/></head><body class="draft "><p id="title"><a class="left" href="h
 ttp://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring">19.8.Â Status monitoring</h2></div></div></div><div class="para">
			You can use the Virtual Machine Manager to modify the virtual system Status monitoring.
		</div><div class="para">
			To configure Status monitoring, and enable Consoles:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					From the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Preferences</strong></span>.
				</div><div class="figure" id="figu-Virtualization_Guide-Status_monitoring-Modifying_guest_preferences"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_preferences_menu.png" alt="Modifying guest preferences"/></div></div><h6>FigureÂ 19.16.Â Modifying guest preferences</h6></div><br class="figure-break"/><div class="para">
					The Virtual Machine Manager Preferences window appears.
				</div></li><li><div class="para">
					From the Status monitoring area selection box, specify the time (in seconds) that you want the system to update.
				</div><div class="figure" id="figu-Virtualization_Guide-Status_monitoring-Configuring_status_monitoring"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_preferences2.png" alt="Configuring status monitoring"/></div></div><h6>FigureÂ 19.17.Â Configuring status monitoring</h6></div><br class="figure-break"/></li><li><div class="para">
					From the Consoles area, specify how to open a console and specify an input device.
				</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html"><strong>Prev</strong>19.7.Â Displaying guest details</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_identifiers.html"><strong>Next</strong>19.9.Â Displaying guest identifiers</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.3.Â The Virtual Machine Manager details window</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html" title="19.2.Â The Virtual Machine Manager main window"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html" title="19.4.Â Virtual Machine graphical console"/
 ></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_">19.3.Â The Virtual Machine Manag
 er details window </h2></div></div></div><div class="para">
			This window displays graphs and statistics of a guest's live resource utilization data available from <code class="command">virt-manager</code>. The UUID field displays the globally unique identifier for the virtual machines.
		</div><div class="figure" id="figu-Virtualization_Guide-The_Virtual_Machine_Manager_details_window_-virt_manager_details_window"><div class="figure-contents"><div class="mediaobject"><img src="images/virtual_machine_details.png" alt="virt-manager details window"/></div></div><h6>FigureÂ 19.3.Â <code class="command">virt-manager</code> details window</h6></div><br class="figure-break"/></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html"><strong>Prev</strong>19.2.Â The Virtual Machine Manager main window</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html"><
 strong>Next</strong>19.4.Â Virtual Machine graphical console </a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.2.Â The Virtual Machine Manager main window</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html" title="19.3.Â The Virtual Machine Manager details wi
 ndow"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></di
 v></div><div class="para">
			This main window displays all the running virtual machines and resources currently allocated to them (including domain0). You can decide which fields to display. Double-clicking on the desired virtual machine brings up the respective console for that particular machine. Selecting a virtual machine and double-click the <span class="guilabel"><strong> Details </strong></span> button to display the Details window for that machine. You can also access the <span class="guilabel"><strong> File </strong></span> menu to create a new virtual machine.
		</div><div class="figure" id="figu-Virtualization_Guide-The_Virtual_Machine_Manager_main_window-Virtual_Machine_Manager_main_window"><div class="figure-contents"><div class="mediaobject"><img src="images/step5-1.png" alt="Virtual Machine Manager main window"/></div></div><h6>FigureÂ 19.2.Â Virtual Machine Manager main window</h6></div><br class="figure-break"/></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html"><strong>Prev</strong>ChapterÂ 19.Â Managing guests with the Virtual Mach...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html"><strong>Next</strong>19.3.Â The Virtual Machine M
 anager details window </a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>19.4.Â Virtual Machine graphical console</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="ChapterÂ 19.Â Managing guests with the Virtual Machine Manager (virt-manager)"/><link rel="prev" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html" title="19.3.Â The Virtual Machine Manager details window"/><link rel="next" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager.html" title="19.5.Â Starting virt-manager"/></head><body class="draft 
 "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_">19.4.Â Virtual Machine graphical console </h2></div></div></div><div class="p
 ara">
			This window displays a virtual machine's graphical console. Para-virtualized and fully virtualized guests use different techniques to export their local virtual framebuffers, but both technologies use <span class="application"><strong>VNC</strong></span> to make them available to the Virtual Machine Manager's console window. If your virtual machine is set to require authentication, the Virtual Machine Graphical console prompts you for a password before the display appears.
		</div><div class="figure" id="figu-Virtualization_Guide-Virtual_Machine_graphical_console_-Graphical_console_window"><div class="figure-contents"><div class="mediaobject"><img src="images/guest-console-small.png" alt="Graphical console window"/></div></div><h6>FigureÂ 19.4.Â Graphical console window</h6></div><br class="figure-break"/><div class="note"><h2>A note on security and VNC</h2><div class="para">
				VNC is considered insecure by many security experts, however, several changes have been made to enable the secure usage of VNC for virtualization on Fedora. The guest machines only listen to the local host (<code class="systemitem">dom0</code>)'s loopback address (<code class="systemitem">127.0.0.1</code>). This ensures only those with shell privileges on the host can access virt-manager and the virtual machine through VNC.
			</div><div class="para">
				Remote administration can be performed following the instructions in <a class="xref" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html" title="ChapterÂ 16.Â Remote management of virtualized guests">ChapterÂ 16, <i>Remote management of virtualized guests</i></a>. TLS can provide enterprise level security for managing guest and host systems.
			</div></div><div class="para">
			Your local desktop can intercept key combinations (for example, Ctrl+Alt+F11) to prevent them from being sent to the guest machine. You can use <code class="command">virt-manager</code>sticky key' capability to send these sequences. You must press any modifier key (Ctrl or Alt) 3 times and the key you specify gets treated as active until the next non-modifier key is pressed. Then you can send Ctrl-Alt-F11 to the guest by entering the key sequence 'Ctrl Ctrl Ctrl Alt+F1'.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html"><strong>Prev</strong>19.3.Â The Virtual Machine Manager details window </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager.html"><strong>Next</strong>19.5.Â Starting virt-manager</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Network_Configuration-Bridged_networking_with_libvirt.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>8.2.Â Bridged networking with libvirt</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Network_Configuration.html" title="ChapterÂ 8.Â Network Configuration"/><link rel="prev" href="chap-Virtualization_Guide-Network_Configuration.html" title="ChapterÂ 8.Â Network Configuration"/><link rel="next" href="chap-Virtualization_Guide-Xen_networking.html" title="ChapterÂ 9.Â Xen networking"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documen
 tation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Network_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Xen_networking.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Network_Configuration-Bridged_networking_with_libvirt">8.2.Â Bridged networking with libvirt</h2></div></div></div><div class="para">
			Bridged networking (also known as physical device sharing) is used for dedicating a physical device to a virtual machine. Bridging is often used for more advanced setups and on servers with multiple network interfaces.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Bridged_networking_with_libvirt-Disable_Xen_network_scripts">Disable Xen network scripts</h5>
				If your system was using a Xen bridge, it is recommended to disable the default Xen network bridge by editing <code class="filename">/etc/xen/xend-config.sxp</code> and changing the line:
			</div><pre class="screen"> (network-script network-bridge)
</pre><div class="para">
			To:
		</div><pre class="screen"> (network-script /bin/true)
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Bridged_networking_with_libvirt-Disable_NetworkManager">Disable NetworkManager</h5>
				NetworkManager does not support bridging. NetworkManager must be disabled to use the older network scripts networking.
			</div><pre class="screen"># chkconfig NetworkManager off
# chkconfig network on
# service NetworkManager stop
# service network start
</pre><div class="note"><h2>Note</h2><div class="para">
				Instead of turning off NetworkManager, you can add "<em class="parameter"><code>NM_CONTROLLED=no</code></em>" to the <code class="filename">ifcfg-*</code> scripts used in the examples.
			</div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Bridged_networking_with_libvirt-Creating_network_initscripts">Creating network initscripts</h5>
				Create or edit the following two network configuration files. This step can be repeated (with different names) for additional network bridges.
			</div><div class="para">
			Change to the <code class="filename">/etc/sysconfig/network-scripts</code> directory:
		</div><pre class="screen"># cd /etc/sysconfig/network-scripts
</pre><div class="para">
			Open the network script for the device you are adding to the bridge. In this example, <code class="filename">ifcfg-eth0</code> defines the physical network interface which is set as part of a bridge:
		</div><pre class="screen">DEVICE=eth0
# change the hardware address to match the hardware address your NIC uses
HWADDR=00:16:76:D6:C9:45
ONBOOT=yes
BRIDGE=br0
</pre><div class="note"><h2>Tip</h2><div class="para">
				You can configure the device's Maximum Transfer Unit (MTU) by appending an <em class="parameter"><code>MTU</code></em> variable to the end of the configuration file.
			</div><pre class="screen">MTU=9000
</pre></div><div class="para">
			Create a new network script in the <code class="filename">/etc/sysconfig/network-scripts</code> directory called <code class="filename">ifcfg-br0</code> or similar. The <em class="parameter"><code>br0</code></em> is the name of the bridge, this can be anything as long as the name of the file is the same as the DEVICE parameter.
		</div><pre class="screen">DEVICE=br0
TYPE=Bridge
BOOTPROTO=dhcp
ONBOOT=yes
DELAY=0
</pre><div class="warning"><h2>Warning</h2><div class="para">
				The line, <em class="parameter"><code>TYPE=Bridge</code></em>, is case-sensitive. It must have uppercase 'B' and lower case 'ridge'.
			</div></div><div class="para">
			After configuring, restart networking or reboot.
		</div><pre class="screen"># service network restart
</pre><div class="para">
			Configure <code class="command">iptables</code> to allow all traffic to be forwarded across the bridge.
		</div><pre class="screen"># iptables -I FORWARD -m physdev --physdev-is-bridged -j ACCEPT
# service iptables save
# service iptables restart
</pre><div class="note"><h2>Disable iptables on bridges</h2><div class="para">
				Alternatively, prevent bridged traffic from being processed by <code class="command">iptables</code> rules. In <code class="filename">/etc/sysctl.conf</code> append the following lines:
			</div><pre class="screen">net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
</pre><div class="para">
				Reload the kernel parameters configured with <code class="command">sysctl</code>
			</div></div><pre class="screen"># sysctl -p /etc/sysctl.conf
</pre><div class="para">
			Restart the <code class="command">libvirt</code> daemon.
		</div><pre class="screen"># service libvirtd reload
</pre><div class="para">
			You should now have a "shared physical device", which guests can be attached and have full LAN access. Verify your new bridge:
		</div><pre class="screen"># brctl show
bridge name     bridge id               STP enabled     interfaces
virbr0          8000.000000000000       yes
br0             8000.000e0cb30550       no              eth0
</pre><div class="para">
			Note, the bridge is completely independent of the <code class="command">virbr0</code> bridge. Do <span class="emphasis"><em>not</em></span> attempt to attach a physical device to <code class="command">virbr0</code>. The <code class="command">virbr0</code> bridge is only for Network Address Translation (NAT) connectivity.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Network_Configuration.html"><strong>Prev</strong>ChapterÂ 8.Â Network Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Xen_networking.html"><strong>Next</strong>ChapterÂ 9.Â Xen networking</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Para_virtualized_Network_Driver_Configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>10.3.Â Para-virtualized Network Driver Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html" title="ChapterÂ 10.Â Xen Para-virtualized Drivers"/><link rel="prev" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_5.html" title="10.2.4.Â Installation and Configuration of Para-virtualized Drivers on Red Hat Enterprise Linux 5"/><link rel="next" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html" title="10.4.Â Additional Para-virtualized Hardware Configuration"/></head><body class="draft "><p id="title"><a class="lef
 t" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_5.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Para_virtualized_Network_Driver_Configuration">10.3.Â Para-virtualized Network Driver Configuration</h2></div></div></div><div class="para">
		Once the para-virtualized network driver is loaded you may need to reconfigure the guest's network interface to reflect the driver and virtual Ethernet card change.
	</div><div class="para">
		Perform the following steps to reconfigure the network interface inside the guest.
	</div><div class="orderedlist"><ol class="arabic"><li><div class="para">
				In <code class="command">virt-manager</code> open the console window for the guest and log in as <code class="systemitem">root</code>.
			</div></li><li><div class="para">
				To display the present settings for <code class="command">eth0</code> execute â€œ<code class="command"># ifconfig eth0</code>â€. If you receive an error about the device not existing you should load the modules manually as outlined in <a class="xref" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers.html" title="27.3.Â Manually loading the para-virtualized drivers">SectionÂ 27.3, â€œManually loading the para-virtualized driversâ€</a>. 
<pre class="screen">ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:00:00:6A:27:3A  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:630150 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:109336431 (104.2 MiB)  TX bytes:846 (846.0 b)
</pre>
			</div></li><li><div class="para">
				Start the network configuration utility(NetworkManager) with the command â€œ<code class="command"># system-config-network</code>â€. Click on the â€œ<span class="guibutton"><strong>Forward</strong></span>â€ button to start the network card configuration. 
				<div class="mediaobject"><img src="images/netconfig3.png"/></div>
			</div></li><li><div class="para">
				Select the '<span class="guimenuitem"><strong>Xen Virtual Ethernet Card (eth0)</strong></span>' entry and click '<span class="guibutton"><strong>Forward</strong></span>'. 
				<div class="mediaobject"><img src="images/netconfig4.png"/></div>
			</div><div class="para">
				Configure the network settings as required. 
				<div class="mediaobject"><img src="images/netconfig5.png"/></div>
			</div></li><li><div class="para">
				Complete the configuration by pressing the '<span class="guibutton"><strong>Apply</strong></span>' button. 
				<div class="mediaobject"><img src="images/netconfig6.png"/></div>
			</div></li><li><div class="para">
				Press the '<span class="guibutton"><strong>Activate</strong></span>' button to apply the new settings and restart the network. 
				<div class="mediaobject"><img src="images/netconfig7.png"/></div>
			</div></li><li><div class="para">
				You should now see the new network interface with an IP address assigned. 
<pre class="screen">ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:16:3E:49:E4:E0
          inet addr:192.168.78.180  Bcast:192.168.79.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:630150 errors:0 dropped:0 overruns:0 frame:0
          TX packets:501209 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:109336431 (104.2 MiB)  TX bytes:46265452 (44.1 MiB)
</pre>
			</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Installation_and_Configuration_of_Para_virtualized_Drivers_on_Red_Hat_Enterprise_Linux_5.html"><strong>Prev</strong>10.2.4.Â Installation and Configuration of Para-vi...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Additional_Para_virtualized_Hardware_Configuration.html"><strong>Next</strong>10.4.Â Additional Para-virtualized Hardware Config...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>16.2.Â Remote management over TLS and SSL</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html" title="ChapterÂ 16.Â Remote management of virtualized guests"/><link rel="prev" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html" title="ChapterÂ 16.Â Remote management of virtualized guests"/><link rel="next" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes.html" title="16.3.Â Transport modes"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><
 a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL">16.2.Â Remote management over TLS and SSL</h2></div></div></div><div class="para">
			You can manage virtual machines using TLS and SSL. TLS and SSL provides greater scalability but is more complicated than ssh (refer to <a class="xref" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_with_SSH" title="16.1.Â Remote management with SSH">SectionÂ 16.1, â€œRemote management with SSHâ€</a>). TLS and SSL is the same technology used by web browsers for secure connections. The <code class="command">libvirt</code> management connection opens a TCP port for incoming connections, which is securely encrypted and authenticated based on x509 certificates. In addition the VNC console for each guest virtual machine will be setup to use TLS with x509 certificate authentication.
		</div><div class="para">
			This method does not require shell accounts on the remote machines being managed. However, extra firewall rules are needed to access the management service or VNC console. Certificate revocation lists can revoke users' access.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Remote_management_over_TLS_and_SSL-Steps_to_setup_TLSSSL_access_for_virt_manager">Steps to setup TLS/SSL access for virt-manager</h5>
				The following short guide assuming you are starting from scratch and you do not have any TLS/SSL certificate knowledge. If you are lucky enough to have a certificate management server you can probably skip the first steps.
			</div><div class="variablelist"><dl><dt><span class="term"><code class="command">libvirt</code> server setup</span></dt><dd><div class="para">
						For more information on creating certificates, refer to the <span class="application"><strong>libvirt</strong></span> website, <a href="http://libvirt.org/remote.html">http://libvirt.org/remote.html</a>.
					</div></dd><dt><span class="term">Xen VNC Server</span></dt><dd><div class="para">
						The Xen VNC server can have TLS enabled by editing the configuration file, <code class="filename">/etc/xen/xend-config.sxp</code>. Remove the commenting on the <code class="command">(vnc-tls 1)</code> configuration parameter in the configuration file.
					</div><div class="para">
						The <code class="filename">/etc/xen/vnc</code> directory needs the following 3 files: 
						<div class="itemizedlist"><ul><li><div class="para">
									<code class="command">ca-cert.pem</code> - The CA certificate
								</div></li><li><div class="para">
									<code class="command">server-cert.pem</code> - The Server certificate signed by the CA
								</div></li><li><div class="para">
									<code class="command">server-key.pem </code>- The server private key
								</div></li></ul></div>
						 This provides encryption of the data channel. It might be appropriate to require that clients present their own x509 certificate as a form of authentication. To enable this remove the commenting on the <code class="command">(vnc-x509-verify 1)</code> parameter.
					</div></dd><dt><span class="term"><code class="command">virt-manager</code> and <code class="command">virsh</code> client setup</span></dt><dd><div class="para">
						The setup for clients is slightly inconsistent at this time. To enable the <code class="command">libvirt</code> management API over TLS, the CA and client certificates must be placed in <code class="command">/etc/pki</code>. For details on this consult <a href="http://libvirt.org/remote.html">http://libvirt.org/remote.html</a>
					</div><div class="para">
						In the <code class="command">virt-manager</code> user interface, use the '<span class="guibutton"><strong>SSL/TLS</strong></span>' transport mechanism option when connecting to a host.
					</div><div class="para">
						For <code class="command">virsh</code>, the URI has the following format:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="filename">qemu://hostname.guestname/system</code> for KVM.
							</div></li><li><div class="para">
								<code class="filename">xen://hostname.guestname/</code> for Xen.
							</div></li></ul></div></dd></dl></div><div class="para">
			To enable SSL and TLS for VNC, it is necessary to put the certificate authority and client certificates into <code class="filename">$HOME/.pki</code>, that is the following three files:
		</div><div class="itemizedlist"><ul><li><div class="para">
					CA or <code class="command">ca-cert.pem</code> - The CA certificate.
				</div></li><li><div class="para">
					<code class="command">libvirt-vnc</code> or <code class="command">clientcert.pem</code> - The client certificate signed by the CA.
				</div></li><li><div class="para">
					<code class="command">libvirt-vnc</code> or <code class="command">clientkey.pem</code> - The client private key.
				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html"><strong>Prev</strong>ChapterÂ 16.Â Remote management of virtualized gues...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes.html"><strong>Next</strong>16.3.Â Transport modes</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>16.3.Â Transport modes</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Remote_management_of_virtualized_guests.html" title="ChapterÂ 16.Â Remote management of virtualized guests"/><link rel="prev" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html" title="16.2.Â Remote management over TLS and SSL"/><link rel="next" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html" title="PartÂ IV.Â Virtualization Reference Guide"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a 
 class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes">16.3.Â Transport modes</h2></div></div></div><div class="para">
			For remote management, <code class="command">libvirt</code> supports the following transport modes:
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Transport_modes-Transport_Layer_Security_TLS">Transport Layer Security (TLS)</h5>
				Transport Layer Security TLS 1.0 (SSL 3.1) authenticated and encrypted TCP/IP socket, usually listening on a public port number. To use this you will need to generate client and server certificates. The standard port is 16514.
			</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Transport_modes-UNIX_sockets">UNIX sockets</h5>
				Unix domain sockets are only accessible on the local machine. Sockets are not encrypted, and use UNIX permissions or SELinux for authentication. The standard socket names are <code class="filename">/var/run/libvirt/libvirt-sock</code> and <code class="filename">/var/run/libvirt/libvirt-sock-ro</code> (for read-only connections).
			</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Transport_modes-SSH">SSH</h5>
				Transported over an Secure Shell protocol (SSH) connection. Requires Netcat (the <span class="package">nc</span> package) installed. The libvirt daemon (<code class="command">libvirtd</code>) must be running on the remote machine. Port 22 must be open for SSH access. You should use some sort of ssh key management (for example, the <code class="command">ssh-agent</code> utility) or you will be prompted for a password.
			</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Transport_modes-ext">ext</h5>
				The ext parameter is used for any external program which can make a connection to the remote machine by means outside the scope of libvirt. This usually covers third-party, unsupported security applications.
			</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Transport_modes-tcp">tcp</h5>
				Unencrypted TCP/IP socket. Not recommended for production use, this is normally disabled, but an administrator can enable it for testing or use over a trusted network. The default port is 16509.
			</div><div class="para">
			The default transport, if no other is specified, is tls.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Transport_modes-Remote_URIs">Remote URIs</h5>
				<code class="command">A Uniform Resource Identifier (URI) is used by <code class="command">virsh</code> and <code class="command">libvirt</code> to connect to a remote host. URIs can also be used with the <code class="command">--connect</code> parameter for the <code class="command">virsh</code> command to execute single commands or migrations on remote hosts.</code>
			</div><div class="para">
			libvirt URIs take the general form (content in square brackets, "[]", represents optional functions):
		</div><pre class="screen">driver[+transport]://[username@][hostname][:port]/[path][?extraparameters]
</pre><div class="para">
			Either the transport method or the hostname must be provided in order to distinguish this from a local URI.
		</div><div class="itemizedlist" id="item-Virtualization_Guide-Transport_modes-Examples_of_remote_management_parameters"><h6>Examples of remote management parameters</h6><ul><li><div class="para">
					Connect to a remote Xen hypervisor on the host named <code class="systemitem">towada</code>, using SSH transport and the SSH username <code class="systemitem">ccurran</code>.
				</div><pre class="screen">xen+ssh://ccurran@towada/
</pre></li><li><div class="para">
					Connect to a remote Xen hypervisor on the host named <code class="systemitem">towada</code> using TLS.
				</div><pre class="screen">xen://towada/
</pre></li><li><div class="para">
					Connect to a remote Xen hypervisor on host <code class="systemitem">towada</code> using TLS. The <em class="parameter"><code>no_verify=1</code></em> tells libvirt not to verify the server's certificate.
				</div><pre class="screen">xen://towada/?no_verify=1
</pre></li><li><div class="para">
					Connect to a remote KVM hypervisor on host <code class="systemitem">towada</code> using SSH.
				</div><pre class="screen">qemu+ssh://towada/system
</pre></li></ul></div><div class="itemizedlist" id="item-Virtualization_Guide-Transport_modes-Testing_examples"><h6>Testing examples</h6><ul><li><div class="para">
					Connect to the local KVM hypervisor with a non-standard UNIX socket. The full path to the Unix socket is supplied explicitly in this case.
				</div><pre class="screen">qemu+unix:///system?socket=/opt/libvirt/run/libvirt/libvirt-sock
</pre></li><li><div class="para">
					Connect to the libvirt daemon with an unencrypted TCP/IP connection to the server with the IP address 10.1.1.10 on port 5000. This uses the test driver with default settings.
				</div><pre class="screen">test+tcp://10.1.1.10:5000/default
</pre></li></ul></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Transport_modes-Extra_URI_parameters">Extra URI parameters</h5>
				Extra parameters can be appended to remote URIs. The table below <a class="xref" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Transport_modes.html#tabl-Virtualization_Guide-Transport_modes-Extra_URI_parameters" title="TableÂ 16.1.Â Extra URI parameters">TableÂ 16.1, â€œExtra URI parametersâ€</a> covers the recognized parameters. All other parameters are ignored. Note that parameter values must be URI-escaped (that is, a question mark (?) is appended before the parameter and special characters are converted into the URI format).
			</div><div class="table" id="tabl-Virtualization_Guide-Transport_modes-Extra_URI_parameters"><div class="table-contents"><table summary="Extra URI parameters" border="1"><colgroup><col/><col/><col/><col/></colgroup><thead><tr><th>
							Name
						</th><th>
							Transport mode
						</th><th>
							Description
						</th><th>
							Example usage
						</th></tr></thead><tbody><tr><td>
							name
						</td><td>
							all modes
						</td><td>
							The name passed to the remote virConnectOpen function. The name is normally formed by removing transport, hostname, port number, username and extra parameters from the remote URI, but in certain very complex cases it may be better to supply the name explicitly.
						</td><td>
							name=qemu:///system
						</td></tr><tr><td>
							command
						</td><td>
							ssh and ext
						</td><td>
							The external command. For ext transport this is required. For ssh the default is ssh. The PATH is searched for the command.
						</td><td>
							command=/opt/openssh/bin/ssh
						</td></tr><tr><td>
							socket
						</td><td>
							unix and ssh
						</td><td>
							The path to the UNIX domain socket, which overrides the default. For ssh transport, this is passed to the remote netcat command (see netcat).
						</td><td>
							socket=/opt/libvirt/run/libvirt/libvirt-sock
						</td></tr><tr><td>
							netcat
						</td><td>
							ssh
						</td><td>
							The name of the netcat command on the remote machine. The default is nc. For ssh transport, libvirt constructs an ssh command which looks like: command -p port [-l username] hostname netcat -U socket where port, username, hostname can be specified as part of the remote URI, and command, netcat and socket come from extra parameters (or sensible defaults).
						</td><td>
							netcat=/opt/netcat/bin/nc
						</td></tr><tr><td>
							no_verify
						</td><td>
							tls
						</td><td>
							If set to a non-zero value, this disables client checks of the server's certificate. Note that to disable server checks of the client's certificate or IP address you must change the libvirtd configuration.
						</td><td>
							no_verify=1
						</td></tr><tr><td>
							no_tty
						</td><td>
							ssh
						</td><td>
							If set to a non-zero value, this stops ssh from asking for a password if it cannot log in to the remote machine automatically (for using ssh-agent or similar). Use this when you do not have access to a terminal - for example in graphical programs which use libvirt.
						</td><td>
							no_tty=1
						</td></tr></tbody></table></div><h6>TableÂ 16.1.Â Extra URI parameters</h6></div><br class="table-break"/></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Prev</strong>16.2.Â Remote management over TLS and SSL</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="part-Virtualization_Guide-Virtualization_Reference_Guide.html"><strong>Next</strong>PartÂ IV.Â Virtualization Reference Guide</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>7.2.Â SELinux considerations</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Security_for_virtualization.html" title="ChapterÂ 7.Â Security for virtualization"/><link rel="prev" href="chap-Virtualization_Guide-Security_for_virtualization.html" title="ChapterÂ 7.Â Security for virtualization"/><link rel="next" href="chap-Virtualization_Guide-Network_Configuration.html" title="ChapterÂ 8.Â Network Configuration"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/
 image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Security_for_virtualization.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Network_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Security_for_virtualization-SELinux_considerations">7.2.Â SELinux considerations</h2></div></div></div><div class="para">
			This sections contains things to you must consider when you implement SELinux into your virtualization deployment. When you deploy system changes or add devices, you must update your SELinux policy accordingly. To configure an LVM volume for a guest, you must modify the SELinux context for the respective underlying block device and volume group.
		</div><pre class="screen"># semanage fcontext -a -t xen_image _t -f -b /dev/sda2
# restorecon /dev/sda2
</pre><div class="para">
			The Boolean parameter <code class="command">xend_disable_t</code> can set the <code class="command">xend</code> to unconfined mode after restarting the daemon. It is better to disable protection for a single daemon than the whole system. It is advisable that you should not re-label directories as <code class="command">xen_image_t</code> that you will use elsewhere.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Security_for_virtualization.html"><strong>Prev</strong>ChapterÂ 7.Â Security for virtualization</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Network_Configuration.html"><strong>Next</strong>ChapterÂ 8.Â Network Configuration</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>5.3.Â Using GFS2 for storing guests</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html" title="ChapterÂ 5.Â Shared storage and virtualization"/><link rel="prev" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests.html" title="5.2.Â Using NFS for storing guests"/><link rel="next" href="chap-Virtualization_Guide-Server_best_practices.html" title="ChapterÂ 6.Â Server best practices"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fed
 oraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Server_best_practices.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests">5.3.Â Using GFS2 for storing guests</h2></div></div></div><div class="para">
			This section covers using the fedora Global File System 2 (GFS2) to store virtualized guests.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests.html"><strong>Prev</strong>5.2.Â Using NFS for storing guests</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Server_best_practices.html"><strong>Next</strong>ChapterÂ 6.Â Server best practices</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>5.2.Â Using NFS for storing guests</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html" title="ChapterÂ 5.Â Shared storage and virtualization"/><link rel="prev" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html" title="ChapterÂ 5.Â Shared storage and virtualization"/><link rel="next" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests.html" title="5.3.Â Using GFS2 for storing guests"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="rig
 ht" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_NFS_for_storing_guests">5.2.Â Using NFS for storing guests</h2></div></div></div><div class="para">
			This section covers using NFS to store virtualized guests.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html"><strong>Prev</strong>ChapterÂ 5.Â Shared storage and virtualization</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Shared_storage_and_virtualization-Using_GFS2_for_storing_guests.html"><strong>Next</strong>5.3.Â Using GFS2 for storing guests</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.2.Â Changing between the KVM and Xen hypervisors</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="next" href="sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-KVM_to_Xen.html" title="23.2.2.Â KVM to Xen"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/imag
 e_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Tips_and_tricks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-KVM_to_Xen.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Changing_between_the_KVM_and_Xen_hypervisors">23.2.Â Changing between the KVM and Xen hypervisors</h2></div></div></div><div class="para">
			This section covers changing between the KVM and Xen hypervisors.
		</div><div class="para">
			Fedora only supports one active hypervisor at a time.
		</div><div class="important"><h2>Migrating virtualized guests between hypervisors</h2><div class="para">
				Presently, there is no application for switching Xen-based guests to KVM or KVM-based guests to Xen. Guests can only be used on the hypervisor type that they were created on.
			</div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-Xen_to_KVM">23.2.1.Â Xen to KVM</h3></div></div></div><div class="para">
				The following procedure covers changing from the Xen hypervisor to the KVM hypervisor. This procedure assumes the <span class="package">kernel-xen</span> package is installed and enabled.
			</div><div class="procedure"><ol class="1"><li id="step-Virtualization_Guide-Xen_to_KVM-Install_the_KVM_package"><p class="title"><b>Install the KVM package</b></p><div class="para">
						Install the <span class="package">kvm</span> package if you have not already done so.
					</div><pre class="screen"># yum install kvm
</pre></li><li id="step-Virtualization_Guide-Xen_to_KVM-Verify_which_kernel_is_in_use"><p class="title"><b>Verify which kernel is in use</b></p><div class="para">
						The <span class="package">kernel-xen</span> package may be installed. Use the <code class="command">uname</code> command to determine which kernel is running:
					</div><pre class="screen">$ uname -r
2.6.23.14-107.fc8xen
</pre><div class="para">
						The "<code class="command">2.6.23.14-107.fc8xen</code>" kernel is running on the system. If the default kernel, "<code class="command">2.6.23.14-107.fc8</code>", is running you can skip the substep.
					</div><ol class="a"><li id="step-Virtualization_Guide-Verify_which_kernel_is_in_use-Changing_the_Xen_kernel_to_the_default_kernel"><p class="title"><b>Changing the Xen kernel to the default kernel</b></p><div class="para">
								The <code class="filename">grub.conf</code> file determines which kernel is booted. To change the default kernel edit the <code class="filename">/boot/grub/grub.conf</code> file as shown below.
							</div><pre class="screen"><span class="bold bold"><strong>default=1</strong></span>
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.23.14-107.fc8)
        root (hd0,0)
        kernel /vmlinuz-2.6.23.14-107.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.23.14-107.fc8.img
title Fedora (2.6.23.14-107.fc8xen)
        root (hd0,0)
        kernel /xen.gz-2.6.23.14-107.fc8
        module /vmlinuz-2.6.23.14-107.fc8xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        module /initrd-2.6.23.14-107.fc8xen.img
</pre><div class="para">
								Notice the <span class="bold bold"><strong>default=1</strong></span> parameter. This is instructing the GRUB boot loader to boot the second entry, the Xen kernel. Change the default to <em class="parameter"><code>0</code></em> (or the number for the default kernel):
							</div><pre class="screen"><span class="bold bold"><strong>default=0</strong></span>
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.23.14-107.fc8)
        root (hd0,0)
        kernel /vmlinuz-2.6.23.14-107.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.23.14-107.fc8.img
title Fedora (2.6.23.14-107.fc8xen)
        root (hd0,0)
        kernel /xen.gz-2.6.23.14-107.fc8
        module /vmlinuz-2.6.23.14-107.fc8xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        module /initrd-2.6.23.14-107.fc8xen.img
</pre></li></ol></li><li id="step-Virtualization_Guide-Xen_to_KVM-Reboot_to_load_the_new_kernel"><p class="title"><b>Reboot to load the new kernel</b></p><div class="para">
						Reboot the system. The computer will restart with the default kernel. The KVM module should be automatically loaded with the kernel. Verify KVM is running:
					</div><pre class="screen">$ lsmod | grep kvm
kvm_intel              85992  1 
kvm                   222368  2 ksm,kvm_intel
</pre><div class="para">
						The <code class="command">kvm</code> module and either the <code class="command">kvm_intel</code> module or the <code class="command">kvm_amd</code> module are present if everything worked.
					</div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Tips_and_tricks.html"><strong>Prev</strong>ChapterÂ 23.Â Tips and tricks</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-KVM_to_Xen.html"><strong>Next</strong>23.2.2.Â KVM to Xen</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.15.Â Cleaning up old Xen configuration files</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html" title="23.14.Â Disable SMART disk monitoring for guests"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_a_VNC_Server.html" title="23.16.Â Configuring a VNC Server"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.f
 edoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files">23.15.Â Cleaning up old Xen configuration files</h2></div></div></div><div class="para">
			Over time you will see a number of files accumulate in <code class="filename">/var/lib/xen</code>, the usually named <code class="filename">vmlinuz.******</code> and <code class="filename">initrd.******</code>. These files are the initrd and vmlinuz files from virtual machines which either failed to boot or failed for some other reason. These files are temporary files extracted from virtual machine's boot disk during the start up sequence. These files should be automatically removed after the virtual machine is shut down cleanly. Then you can safely delete old and stale copies from this directory.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Prev</strong>23.14.Â Disable SMART disk monitoring for guests</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Next</strong>23.16.Â Configuring a VNC Server</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Cloning_guest_configuration_files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.17.Â Cloning guest configuration files</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_a_VNC_Server.html" title="23.16.Â Configuring a VNC Server"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Duplicating_an_existing_guest_and_its_configuration_file.html" title="23.18.Â Duplicating an existing guest and its configuration file"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="
 right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Duplicating_an_existing_guest_and_its_configuration_file.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Cloning_guest_configuration_files">23.17.Â Cloning guest configuration files</h2></div></div></div><div class="para">
			You can copy an existing configuration file to create an all new guest. You must modify the name parameter of the guests' configuration file. The new, unique name then appears in the hypervisor and is viewable by the management utilities. You must generate an all new UUID as well by using the <code class="command">uuidgen</code> command. Then for the <code class="command">vif</code> entries you must define a unique MAC address for each guest (if you are copying a guest configuration from an existing guest, you can create a script to handle it). For the xen bridge information, if you move an existing guest configuration file to a new host, you must update the <code class="command">xenbr</code> entry to match your local networking configuration. For the Device entries, you must modify the entries in the <code class="command">'disk='</code> section to point to the correct guest image.
		</div><div class="para">
			You must also modify these system configuration settings on your guest. You must modify the HOSTNAME entry of the <code class="command">/etc/sysconfig/network</code> file to match the new guest's hostname.
		</div><div class="para">
			You must modify the <code class="command">HWADDR</code> address of the <code class="filename"> /etc/sysconfig/network-scripts/ifcfg-eth0</code> file to match the output from <code class="command">ifconfig eth0</code> file and if you use static IP addresses, you must modify the <code class="command">IPADDR</code> entry.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Prev</strong>23.16.Â Configuring a VNC Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Duplicating_an_existing_guest_and_its_configuration_file.html"><strong>Next</strong>23.18.Â Duplicating an existing guest and its conf...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.13.Â Configuring LUN Persistence</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd.html" title="23.12.Â Very Secure ftpd"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html" title="23.14.Â Disable SMART disk monitoring for guests"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="
 Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence">23.13.Â Configuring LUN Persistence</h2></div></div></div><div class="para">
			This section covers how to implement <a class="firstterm" href="go01.html#glos-Virtualization_Guide-LUN"><em class="firstterm">LUN</em></a> persistence in guests and on the host machine with and without multipath.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Configuring_LUN_Persistence-Implementing_LUN_persistence_without_multipath">Implementing LUN persistence without multipath</h5>
				If your system is not using multipath, you can use <code class="command">udev</code> to implement LUN persistence. Before implementing LUN persistence in your system, ensure that you acquire the proper UUIDs. Once you acquire these, you can configure LUN persistence by editing the <code class="command">scsi_id</code> file that resides in the <code class="command">/etc </code> directory. Once you have this file open in a text editor, you must comment out this line:
			</div><pre class="screen"># options=-b
</pre><div class="para">
			Then replace it with this parameter:
		</div><pre class="screen"># options=-g
</pre><div class="para">
			This tells udev to monitor all system SCSI devices for returning UUIDs. To determine the system UUIDs, use the <code class="command">scsi_id</code> command:
		</div><pre class="screen"># scsi_id -g -s /block/sdc
*3600a0b80001327510000015427b625e*
</pre><div class="para">
			The long string of characters in the output is the UUID. The UUID does not change when you add a new device to your system. Acquire the UUID for each the device in order to create rules for the devices. To create new device rules, edit the <code class="command">20-names.rules</code> file in the <code class="command">/etc/udev/rules.d </code> directory. The device naming rules follow this format:
		</div><pre class="screen"># KERNEL="sd*",  BUS="scsi",  PROGRAM="sbin/scsi_id", RESULT="<em class="parameter"><code>UUID</code></em>", NAME="<em class="parameter"><code>devicename</code></em>"
</pre><div class="para">
			Replace your existing <em class="parameter"><code>UUID</code></em> and <em class="parameter"><code>devicename</code></em> with the above UUID retrieved entry. The rule should resemble the following:
		</div><pre class="screen">KERNEL="<em class="parameter"><code>sd*</code></em>",  BUS="scsi",  PROGRAM="sbin/scsi_id", RESULT="<em class="parameter"><code>3600a0b80001327510000015427b625e</code></em>", NAME="<em class="parameter"><code>mydevicename</code></em>"
</pre><div class="para">
			This enables all devices that match the <code class="command">/dev/sd*</code> pattern to inspect the given UUID. When it finds a matching device, it creates a device node called <em class="parameter"><code> /dev/devicename</code></em>. For this example, the device node is <em class="parameter"><code>/dev/mydevice </code></em>. Finally, append the <code class="command">/etc/rc.local</code> file with this line:
		</div><pre class="screen">/sbin/start_udev
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Configuring_LUN_Persistence-Implementing_LUN_persistence_with_multipath">Implementing LUN persistence with multipath</h5>
				To implement LUN persistence in a multipath environment, you must define the alias names for the multipath devices. For this example, you must define four device aliases by editing the <code class="command">multipath.conf</code> file that resides in the <code class="command">/etc/</code> directory:
			</div><pre class="screen">multipath  {  
             wwid       3600a0b80001327510000015427b625e
             alias      oramp1
}
multipath  {  
             wwid       3600a0b80001327510000015427b6
             alias      oramp2
}
multipath  {  
             wwid       3600a0b80001327510000015427b625e
             alias      oramp3
}
multipath  {  
             wwid       3600a0b80001327510000015427b625e
             alias      oramp4
}
</pre><div class="para">
			This defines 4 LUNs: <code class="command"> /dev/mpath/oramp1</code>, <code class="command">/dev/mpath/oramp2</code>, <code class="command">/dev/mpath/oramp3</code>, and <code class="command">dev/mpath/oramp4</code>. The devices will reside in the <code class="command">/dev/mpath </code> directory. These LUN names are persistent over reboots as it creates the alias names on the wwid of the LUNs.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd.html"><strong>Prev</strong>23.12.Â Very Secure ftpd</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Next</strong>23.14.Â Disable SMART disk monitoring for guests</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Configuring_Xen_processor_affinities.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.10.Â Configuring Xen processor affinities</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest.html" title="23.9.Â Limit network bandwidth for a Xen guest"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_the_Xen_hypervisor.html" title="23.11.Â Modifying the Xen hypervisor"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs
 .fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_the_Xen_hypervisor.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Configuring_Xen_processor_affinities">23.10.Â Configuring Xen processor affinities</h2></div></div></div><div class="para">
			Xen can allocate virtual CPUs to associate with one or more host CPUs. This allocates real processing resources to virtualized guests. This approach allows Fedora to optimize processor resources when employing dual-core, hyper-threading, or other CPU concurrency technologies. The Xen credit scheduler automatically balances virtual CPUs between physical ones, to maximize system use. Linux allows the credit scheduler to move CPUs around as necessary, as long as the virtual CPU is pinned to a physical CPU.
		</div><div class="para">
			If you are running I/O intensive tasks, it is recommended to dedicate either a hyperthread or an entire processor core to run domain0.
		</div><div class="para">
			Note that this is unnecessary for KVM as KVM uses the default Linux kernel scheduler.
		</div><div class="para">
			CPU affinities can be set with <code class="command">virsh</code> or <code class="command">virt-manager</code>:
		</div><div class="para">
			To set CPU affinities using <code class="command">virsh</code> refer to <a class="xref" href="chap-Virtualization_Guide-Managing_guests_with_virsh.html#form-Virtualization_Guide-Managing_guests_with_virsh-Configuring_virtual_CPU_affinity" title="Configuring virtual CPU affinity">Configuring virtual CPU affinity</a> for more information.
		</div><div class="para">
			To configure and view CPU information with <code class="command">virt-manager</code> refer to <a class="xref" href="sect-Virtualization_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_virtual_CPUs_.html" title="19.11.Â Displaying virtual CPUs">SectionÂ 19.11, â€œDisplaying virtual CPUs â€</a> for more information.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest.html"><strong>Prev</strong>23.9.Â Limit network bandwidth for a Xen guest</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_the_Xen_hypervisor.html"><strong>Next</strong>23.11.Â Modifying the Xen hypervisor</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Configuring_a_VNC_Server.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.16.Â Configuring a VNC Server</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files.html" title="23.15.Â Cleaning up old Xen configuration files"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Cloning_guest_configuration_files.html" title="23.17.Â Cloning guest configuration files"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.
 fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Cloning_guest_configuration_files.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Configuring_a_VNC_Server">23.16.Â Configuring a VNC Server</h2></div></div></div><div class="para">
			To configure a VNC server use the <span class="guimenuitem"><strong>Remote Desktop</strong></span> application in <span class="guimenu"><strong>System</strong></span> > <span class="guimenu"><strong>Preferences</strong></span>. Alternatively, you can run the <code class="command">vino-preferences</code> command.
		</div><div class="para">
			The following steps set up a dedicated VNC server session:
		</div><div class="orderedlist"><ol><li><div class="para">
					Edit the <code class="filename">~/.vnc/xstartup</code> file to start a GNOME session whenever <span class="application"><strong>vncserver</strong></span> is started. The first time you run the <span class="application"><strong>vncserver</strong></span> script it will ask you for a password you want to use for your VNC session.
				</div></li><li><div class="para">
					A sample <code class="command">xstartup</code> file:
				</div><pre class="screen">#!/bin/sh
# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc
[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
#xsetroot -solid grey
#vncconfig -iconic &
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#twm &
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
	eval `dbus-launch --sh-syntax â€“exit-with-session`
	echo "D-BUS per-session daemon address is: \
	$DBUS_SESSION_BUS_ADDRESS"
fi
exec  gnome-session
</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files.html"><strong>Prev</strong>23.15.Â Cleaning up old Xen configuration files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Cloning_guest_configuration_files.html"><strong>Next</strong>23.17.Â Cloning guest configuration files</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.14.Â Disable SMART disk monitoring for guests</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html" title="23.13.Â Configuring LUN Persistence"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files.html" title="23.15.Â Cleaning up old Xen configuration files"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://d
 ocs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests">23.14.Â Disable SMART disk monitoring for guests</h2></div></div></div><div class="para">
			SMART disk monitoring can be disabled as we are running on virtual disks and the physical storage is managed by the host. 
<pre class="screen">/sbin/service smartd stop
/sbin/chkconfig --del smartd
</pre>
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html"><strong>Prev</strong>23.13.Â Configuring LUN Persistence</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Cleaning_up_old_Xen_configuration_files.html"><strong>Next</strong>23.15.Â Cleaning up old Xen configuration files</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Duplicating_an_existing_guest_and_its_configuration_file.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.18.Â Duplicating an existing guest and its configuration file</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Cloning_guest_configuration_files.html" title="23.17.Â Cloning guest configuration files"/><link rel="next" href="chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html" title="ChapterÂ 24.Â Creating custom libvirt scripts"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http:/
 /docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Cloning_guest_configuration_files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Duplicating_an_existing_guest_and_its_configuration_file">23.18.Â Duplicating an existing guest and its configuration file</h2></div></div></div><div class="para">
			This section outlines copying an existing configuration file to create a new guest. There are key parameters in your guest's configuration file you must be aware of, and modify, to successfully duplicate a guest.
		</div><div class="variablelist"><dl><dt><span class="term"><code class="computeroutput">name</code></span></dt><dd><div class="para">
						The name of your guest as it is known to the hypervisor and displayed in the management utilities. This entry should be unique on your system.
					</div></dd><dt><span class="term"><code class="computeroutput">uuid</code></span></dt><dd><div class="para">
						A unique handle for the guest, a new UUID can be regenerated using the <code class="command">uuidgen</code> command. A sample UUID output:
					</div><pre class="screen">$ uuidgen 
a984a14f-4191-4d14-868e-329906b211e5
</pre></dd><dt><span class="term"><code class="computeroutput">vif</code></span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
								The <a class="firstterm" href="go01.html#glos-Virtualization_Guide-MAC_Addresses"><em class="firstterm">MAC address</em></a> must define a unique MAC address for each guest. This is automatically done if the standard tools are used. If you are copying a guest configuration from an existing guest you can use the script <a class="xref" href="sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address.html" title="23.8.Â Generating a new unique MAC address">SectionÂ 23.8, â€œGenerating a new unique MAC addressâ€</a>.
							</div></li><li><div class="para">
								If you are moving or duplicating an existing guest configuration file to a new host you have to make sure you adjust the <code class="computeroutput">xenbr</code> entry to correspond with your local networking configuration (you can obtain the bridge information using the command <code class="command">brctl show</code> command).
							</div></li><li><div class="para">
								Device entries, make sure you adjust the entries in the <code class="filename">disk=</code> section to point to the correct guest image.
							</div></li></ul></div></dd></dl></div><div class="para">
			Now, adjust the system configuration settings on your guest:
		</div><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/sysconfig/network</code></span></dt><dd><div class="para">
						Modify the <code class="computeroutput">HOSTNAME</code> entry to the guest's new <code class="command">hostname</code>.
					</div></dd><dt><span class="term"><code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code></span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
								Modify the <code class="computeroutput">HWADDR</code> address to the output from <code class="command">ifconfig eth0</code>
							</div></li><li><div class="para">
								Modify the <code class="computeroutput">IPADDR</code> entry if a static IP address is used.
							</div></li></ul></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Cloning_guest_configuration_files.html"><strong>Prev</strong>23.17.Â Cloning guest configuration files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Creating_custom_libvirt_scripts.html"><strong>Next</strong>ChapterÂ 24.Â Creating custom libvirt scripts</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.8.Â Generating a new unique MAC address</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation.html" title="23.7.Â Identifying guest type and implementation"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest.html" title="23.9.Â Limit network bandwidth for a Xen guest"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="r
 ight" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address">23.8.Â Generating a new unique MAC address</h2></div></div></div><div class="para">
			In some case you will need to generate a new and unique <a class="firstterm" href="go01.html#glos-Virtualization_Guide-MAC_Addresses"><em class="firstterm">MAC address</em></a> for a guest. There is no command line tool available to generate a new MAC address at the time of writing. The script provided below can generate a new MAC address for your guests. Save the script to your guest as <code class="filename">macgen.py</code>. Now from that directory you can run the script using <code class="command">./macgen.py</code> . and it will generate a new MAC address. A sample output would look like the following:
		</div><pre class="screen">$ ./macgen.py 
00:16:3e:20:b0:11

#!/usr/bin/python
# macgen.py script to generate a MAC address for virtualized guests on Xen
#
import random
#
def randomMAC():
	mac = [ 0x00, 0x16, 0x3e,
		random.randint(0x00, 0x7f),
		random.randint(0x00, 0xff),
		random.randint(0x00, 0xff) ]
	return ':'.join(map(lambda x: "%02x" % x, mac))
#
print randomMAC()
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Generating_a_new_unique_MAC_address-Another_method_to_generate_a_new_MAC_for_your_guest">Another method to generate a new MAC for your guest</h5>
				You can also use the built-in modules of <code class="command">python-virtinst</code> to generate a new MAC address and <code class="command">UUID</code> for use in a guest configuration file:
			</div><pre class="screen"># echo  'import virtinst.util ; print\
 virtinst.util.uuidToString(virtinst.util.randomUUID())' | python
# echo  'import virtinst.util ; print virtinst.util.randomMAC()' | python
</pre><div class="para">
			The script above can also be implemented as a script file as seen below.
		</div><pre class="screen">#!/usr/bin/env python
#  -*- mode: python; -*-
print ""
print "New UUID:"
import virtinst.util ; print virtinst.util.uuidToString(virtinst.util.randomUUID())
print "New MAC:"
import virtinst.util ; print virtinst.util.randomMAC()
print ""
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation.html"><strong>Prev</strong>23.7.Â Identifying guest type and implementation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest.html"><strong>Next</strong>23.9.Â Limit network bandwidth for a Xen guest</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.7.Â Identifying guest type and implementation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html" title="23.6.Â Verifying virtualization extensions"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address.html" title="23.8.Â Generating a new unique MAC address"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="ht
 tp://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation">23.7.Â Identifying guest type and implementation</h2></div></div></div><div class="para">
			The script below can identify if the environment an application or script is running in is a para-virtualized, a fully virtualized guest or on the hypervisor.
		</div><pre class="screen">#!/bin/bash
declare -i IS_HVM=0
declare -i IS_PARA=0
check_hvm()
{
	IS_X86HVM="$(strings /proc/acpi/dsdt | grep int-xen)"
	  if [ x"${IS_X86HVM}" != x ]; then
	   echo "Guest type is full-virt x86hvm"
	   IS_HVM=1
	fi
}
check_para()
{
	if $(grep -q control_d /proc/xen/capabilities); then
	  echo "Host is dom0"
	  IS_PARA=1
	else
	  echo "Guest is para-virt domU"
	  IS_PARA=1
	fi
}
if [ -f /proc/acpi/dsdt ]; then 
	check_hvm
fi

if [ ${IS_HVM} -eq 0 ]; then
	if [ -f /proc/xen/capabilities ] ; then
		check_para
	fi
     fi
if [ ${IS_HVM} -eq 0 -a ${IS_PARA} -eq 0 ]; then
	echo "Baremetal platform"
fi
</pre><div class="note"><h2>Examining hosts</h2><div class="para">
				For examining hosts, use the <code class="command">virsh capabilites</code> command.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Prev</strong>23.6.Â Verifying virtualization extensions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Next</strong>23.8.Â Generating a new unique MAC address</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.9.Â Limit network bandwidth for a Xen guest</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address.html" title="23.8.Â Generating a new unique MAC address"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_Xen_processor_affinities.html" title="23.10.Â Configuring Xen processor affinities"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="h
 ttp://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_Xen_processor_affinities.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest">23.9.Â Limit network bandwidth for a Xen guest</h2></div></div></div><div class="para">
			In some environments it may be required to limit the network bandwidth available to certain guests. This can be used to implement basic Quality of Service on a host running multiple virtual machines. By default, the guest can use any bandwidth setting available which your physical network card supports. The physical network card must be mapped to one of virtual machine's virtual network interfaces. In Xen the â€œ<code class="command">rate</code>â€ parameter part of the <code class="filename">VIF</code> entries can throttle virtualized guests.
		</div><div class="para">
			This list covers the variables
		</div><div class="variablelist"><dl><dt><span class="term"><code class="command">rate</code></span></dt><dd><div class="para">
						The <code class="computeroutput">rate=</code> option can be added to the <code class="computeroutput">VIF=</code> entry in a virtual machine configuration file to limit a virtual machine's network bandwidth or specify a specific time interval for a time window.
					</div></dd><dt><span class="term">time window</span></dt><dd><div class="para">
						The time window is optional to the <code class="computeroutput">rate=</code> option:
					</div><div class="para">
						The default time window is 50ms.
					</div><div class="para">
						A smaller time window will provide less burst transmission, however, the replenishment rate and latency will increase.
					</div><div class="para">
						The default 50ms time window is a good balance between latency and throughput and in most cases will not require changing.
					</div></dd></dl></div><div class="para">
			Examples of <code class="command">rate</code> parameter values and uses.
		</div><div class="variablelist"><dl><dt><span class="term"><code class="computeroutput">rate=10Mb/s</code></span></dt><dd><div class="para">
						Limit the outgoing network traffic from the guest to 10MB/s.
					</div></dd><dt><span class="term"><code class="computeroutput">rate=250KB/s</code></span></dt><dd><div class="para">
						Limit the outgoing network traffic from the guest to 250KB/s.
					</div></dd><dt><span class="term"><code class="computeroutput">rate=10MB/s at 50ms</code></span></dt><dd><div class="para">
						Limit bandwidth to 10MB/s and provide the guest with a 50KB chunk every 50ms.
					</div></dd></dl></div><div class="para">
			In the virtual machine configuration a sample <code class="filename">VIF</code> entry would look like the following:
		</div><pre class="screen">vif = [ 'rate=10MB/s , mac=00:16:3e:7a:55:1c, bridge=xenbr1']
</pre><div class="para">
			This <code class="computeroutput">rate</code> entry would limit the virtual machine's interface to 10MB/s for outgoing traffic
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Prev</strong>23.8.Â Generating a new unique MAC address</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_Xen_processor_affinities.html"><strong>Next</strong>23.10.Â Configuring Xen processor affinities</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.5.Â Modifying /etc/grub.conf</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html" title="23.4.Â Overcommitting with KVM"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html" title="23.6.Â Verifying virtualization extensions"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Co
 mmon_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf">23.5.Â Modifying /etc/grub.conf</h2></div></div></div><div class="para">
			This section describes how to safely and correctly change your <code class="filename">/etc/grub.conf</code> file to use the virtualization kernel. You must use the <code class="systemitem">xen</code> kernel to use the Xen hypervisor. Copy your existing <code class="systemitem">xen</code> kernel entry make sure you copy all of the important lines or your system will panic upon boot (<code class="command">initrd</code> will have a length of '<code class="command">0</code>'). If you require <code class="systemitem">xen</code> hypervisor specific values you must append them to the <code class="computeroutput">xen</code> line of your grub entry.
		</div><div class="para">
			The output below is an example of a <code class="filename">grub.conf</code> entry from a system running the <span class="package">kernel-xen</span> package. The <code class="filename">grub.conf</code> on your system may vary. The important part in the example below is the section from the <code class="command">title</code> line to the next new line.
		</div><pre class="screen">#boot=/dev/sda
default=0
timeout=15
#splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
terminal --timeout=10 serial console

title Fedora (2.6.23.14-107.fc8xen)
	root (hd0,0)
	kernel /xen.gz-2.6.23.14-107.fc8 com1=115200,8n1
	module /vmlinuz-2.6.23.14-107.fc8xen ro root=/dev/VolGroup00/LogVol00
	module /initrd-2.6.23.14-107.fc8xen.img
</pre><div class="note"><h2>An important point regarding editing grub.conf...</h2><div class="para">
				Your <code class="filename">grub.conf</code> could look very different if it has been manually edited before or copied from an example. Read <a class="xref" href="chap-Virtualization_Guide-Configuring_the_Xen_kernel_boot_parameters.html" title="ChapterÂ 21.Â Configuring the Xen kernel boot parameters">ChapterÂ 21, <i>Configuring the Xen kernel boot parameters</i></a> for more information on using virtualization and grub.
			</div></div><div class="para">
			To set the amount of memory assigned to your host system at boot time to 256MB you need to append <code class="computeroutput">dom0_mem=256M</code> to the <code class="computeroutput">xen</code> line in your <code class="filename">grub.conf</code>. A modified version of the grub configuration file in the previous example:
		</div><pre class="screen">#boot=/dev/sda
default=0
timeout=15
#splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
terminal --timeout=10 serial console

title Fedora (2.6.23.14-107.fc8xen)
	root (hd0,0)
	kernel /xen.gz-2.6.23.14-107.fc8 com1=115200,8n1 dom0_mem=256MB
	module /vmlinuz-2.6.23.14-107.fc8xen ro
	root=/dev/VolGroup00/LogVol00
	module /initrd-2.6.23.14-107.fc8xen.img
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Prev</strong>23.4.Â Overcommitting with KVM</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Next</strong>23.6.Â Verifying virtualization extensions</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Modifying_the_Xen_hypervisor.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.11.Â Modifying the Xen hypervisor</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_Xen_processor_affinities.html" title="23.10.Â Configuring Xen processor affinities"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd.html" title="23.12.Â Very Secure ftpd"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_
 Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_Xen_processor_affinities.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Modifying_the_Xen_hypervisor">23.11.Â Modifying the Xen hypervisor</h2></div></div></div><div class="para">
			Managing host systems often involves changing the boot configuration file <code class="filename">/boot/grub/grub.conf</code>. Managing several or more hosts configuration files quickly becomes difficult. System administrators often prefer to use the 'cut and paste' method for editing multiple <code class="command">grub.conf</code> files. If you do this, ensure you include all five lines in the Virtualization entry (or this will create system errors). Hypervisor specific values are all found on the '<code class="systemitem">xen</code>' line. This example represents a correct <code class="command">grub.conf</code> virtualization entry:
		</div><pre class="screen"># boot=/dev/sda/
default=0
timeout=15
#splashimage=(hd0, 0)/grub/splash.xpm.gz

hiddenmenu
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
terminal --timeout=10 serial console
title Fedora (2.6.23.14-107.fc8xen)
root (hd0, 0)
kernel /xen.gz-2.6.23.14-107.fc8 com1=115200,8n1
module /vmlinuz-2.6.23.14-107.fc8xen ro root=/dev/VolGroup00/LogVol00
module /initrd-2.6.23.14-107.fc8xen.img
</pre><div class="para">
			For example, to change the memory entry on your hypervisor (dom0) to 256MB at boot time, edit the 'xen' line and append it with this entry: <code class="command">'dom0_mem=256M'</code>. This example a modified <code class="command">grub.conf</code> with the hypervisor's memory entry modified.
		</div><pre class="screen"># boot=/dev/sda
default=0
timeout=15
#splashimage=(hd0,0)/grubs/splash.xpm.gz
hiddenmenu
serial --unit=0 --speed =115200 --word=8 --parity=no --stop=1
terminal --timeout=10 serial console
title Fedora (2.6.23.14-107.fc8xen)
root (hd0,0)
kernel /xen.gz-2.6.23.14-107.fc8 com1=115200,8n1 dom0_mem=256MB
module /vmlinuz-2.6.23.14-107.fc8xen ro
root=/dev/VolGroup00/LogVol00
module /initrd-2.6.23.14-107.fc8xen.img
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_Xen_processor_affinities.html"><strong>Prev</strong>23.10.Â Configuring Xen processor affinities</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd.html"><strong>Next</strong>23.12.Â Very Secure ftpd</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.4.Â Overcommitting with KVM</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img.html" title="23.3.Â Using qemu-img"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html" title="23.5.Â Modifying /etc/grub.conf"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="D
 ocumentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM">23.4.Â Overcommitting with KVM</h2></div></div></div><div class="para">
			The KVM hypervisor supports overcommitting CPUs and overcommitting memory. Overcommitting is allocating more virtualized CPUs or memory than there are physical resources on the system. With CPU overcommit, under-utilized virtualized servers or desktops can run on fewer servers which saves power and money.
		</div><div class="important"><h2>Xen support</h2><div class="para">
				CPU overcommitting is not supported for the Xen hypervisor. Overcommitting CPUs with the Xen hypervisor may cause system instability and crashes of the host and virtualized guests.
			</div></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Overcommitting_with_KVM-Overcommitting_memory">Overcommitting memory</h5>
				Most operating systems and applications do not use 100% of the available RAM all the time. This behavior can be exploited with KVM to use more memory for virtualized guests than what is physically available.
			</div><div class="para">
			With KVM, virtual machines are Linux processes. Guests on the KVM hypervisor do not have blocks of physical RAM assigned to them instead they function as processes. Each process is allocated memory when it requests more memory. KVM uses this to allocate memory for guests when the guest operating system requests more or less memory. The guest only uses slightly more physical memory than the virtualized operating system appears to use.
		</div><div class="para">
			When physical memory is nearly completely used or a process is inactive for some time, Linux moves the process's memory to swap. Swap is usually a partition on a hard disk drive or solid state drive which Linux uses to extend virtual memory. Swap is significantly slower than RAM.
		</div><div class="para">
			As KVM virtual machines are Linux processes, memory used by virtualized guests can be put into swap if the guest is idle or not in heavy use. Memory can be committed over the total size of the swap and physical RAM. This can cause issues if virtualized guests use their total RAM. Without sufficient swap space for the virtual machine processes to be swapped to the <code class="command">pdflush</code> process starts. <code class="command">pdflush</code> kills processes to free memory so the system does not crash. <code class="command">pdflush</code> may destroy virtualized guests or other system processes which may cause file system errors and may leave virtualized guests unbootable.
		</div><div class="warning"><h2>Warning</h2><div class="para">
				If sufficient swap is not available guest operating systems will be forcibly shut down. This may leave guests inoperable. Avoid this by never overcommitting more memory than there is swap available.
			</div></div><div class="para">
			The swap partition is used for swapping underused memory to the hard drive to speed up memory performance. The default size of the swap partition is calculated from amount of RAM and overcommit ratio. It is recommended to make your swap partition larger if you intend to overcommit memory with KVM. A recommended overcommit ratio is 50% (0.5). The formula used is:
		</div><pre class="screen">(0.5 * RAM) + (overcommit ratio * RAM) = Recommended swap size
</pre><div class="para">
			The Red Hat Knowledgebase has an article on safely and efficiently determining the size of the swap partition â€” refer to <a href="http://kbase.redhat.com/faq/docs/DOC-15252">Knowledgebase</a>.
		</div><div class="para">
			It is possible to run with an overcommit ratio of ten times the number of virtualized guests over the amount of physical RAM in the system. This only works with certain application loads (for example desktop virtualization with under 100% usage). Setting overcommit ratios is not a hard formula, you must test and customize the ratio for your environment.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Overcommitting_with_KVM-Overcommitting_virtualized_CPUs">Overcommitting virtualized CPUs</h5>
				The KVM hypervisor supports overcommitting virtualized CPUs. Virtualized CPUs can be overcommitted as far as load limits of virtualized guests allow. Use caution when overcommitting VCPUs as loads near 100% may cause dropped requests or unusable response times.
			</div><div class="para">
			Virtualized CPUs are overcommitted best when each virtualized guest only has a single VCPU. The Linux scheduler is very efficient with this type of load. KVM should safely support guests with loads under 100% at a ratio of 5 VCPUs Overcommitting single VCPU virtualized guests is not an issue.
		</div><div class="para">
			You cannot overcommit symmetric multiprocessing guests on more than the physical number of processing cores. For example a guest with four VCPUs should not be run on a host with a dual core processor. Overcommitting symmetric multiprocessing guests in over the physical number of processing cores will cause significant performance degradation.
		</div><div class="para">
			Assigning guests VCPUs up to the number of physical cores is appropriate and works as expected. For example, running virtualized guests with four VCPUs on a quad core host. Guests with less than 100% loads should function effectively in this setup.
		</div><div class="important"><h2>Always test first</h2><div class="para">
				Do not overcommit memory or CPUs in a production environment without extensive testing. Applications which use 100% of memory or processing resources may become unstable in overcommitted environments. Test before deploying.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img.html"><strong>Prev</strong>23.3.Â Using qemu-img</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html"><strong>Next</strong>23.5.Â Modifying /etc/grub.conf</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.3.Â Using qemu-img</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-KVM_to_Xen.html" title="23.2.2.Â KVM to Xen"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html" title="23.4.Â Overcommitting with KVM"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_rig
 ht.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-KVM_to_Xen.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Using_qemu_img">23.3.Â Using qemu-img</h2></div></div></div><div class="para">
			The <code class="command">qemu-img</code> command line tool is used for formatting various file systems used by Xen and KVM. <code class="command">qemu-img</code> should be used for formatting virtualized guest images, additional storage devices and network storage. <code class="command">qemu-img</code> options and usages are listed below.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Using_qemu_img-Formatting_and_creating_new_images_or_devices">Formatting and creating new images or devices</h5>
				Create the new disk image filename of size size and format format.
			</div><pre class="screen"># qemu-img create [-6] [-e] [-b base_image] [-f format] filename [size]
</pre><div class="para">
			If base_image is specified, then the image will record only the differences from base_image. No size needs to be specified in this case. base_image will never be modified unless you use the "commit" monitor command.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Using_qemu_img-Convert_an_existing_image_to_another_format">Convert an existing image to another format</h5>
				The convert option is used for converting a recognized format to another image format.
			</div><div class="para">
			Command format:
		</div><pre class="screen"># qemu-img convert [-c] [-e] [-f format] filename [-O output_format] output_filename
</pre><div class="para">
			convert the disk image filename to disk image output_filename using format output_format. it can be optionally encrypted ("-e" option) or compressed ("-c" option).
		</div><div class="para">
			only the format "qcow" supports encryption or compression. the compression is read-only. it means that if a compressed sector is rewritten, then it is rewritten as uncompressed data.
		</div><div class="para">
			The encryption uses the AES format with very secure 128 bit keys. use a long password (16 characters) to get maximum protection.
		</div><div class="para">
			image conversion is also useful to get smaller image when using a format which can grow, such as <code class="command">qcow</code> or <code class="command">cow</code>. The empty sectors are detected and suppressed from the destination image.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Using_qemu_img-getting_image_information">getting image information</h5>
				the <code class="command">info</code> parameter displays information about a disk image. the format for the <code class="command">info</code> option is as follows:
			</div><pre class="screen"># qemu-img info [-f format] filename
</pre><div class="para">
			give information about the disk image filename. use it in particular to know the size reserved on disk which can be different from the displayed size. if vm snapshots are stored in the disk image, they are displayed too.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Using_qemu_img-Supported_formats">Supported formats</h5>
				The format of an image is usually guessed automatically. The following formats are supported:
			</div><div class="variablelist"><dl><dt><span class="term"><code class="command">raw</code></span></dt><dd><div class="para">
						Raw disk image format (default). This format has the advantage of being simple and easily exportable to all other emulators. If your file system supports holes (for example in ext2 or ext3 on Linux or NTFS on Windows), then only the written sectors will reserve space. Use <code class="command">qemu-img info</code> to know the real size used by the image or <code class="command">ls -ls</code> on Unix/Linux.
					</div></dd><dt><span class="term"><code class="command">qcow2</code></span></dt><dd><div class="para">
						QEMU image format, the most versatile format. Use it to have smaller images (useful if your file system does not supports holes, for example: on Windows), optional AES encryption, zlib based compression and support of multiple VM snapshots.
					</div></dd><dt><span class="term"><code class="command">qcow</code></span></dt><dd><div class="para">
						Old QEMU image format. Only included for compatibility with older versions.
					</div></dd><dt><span class="term"><code class="command">cow</code></span></dt><dd><div class="para">
						User Mode Linux Copy On Write image format. The <code class="command">cow</code> format is included only for compatibility with previous versions. It does not work with Windows.
					</div></dd><dt><span class="term"><code class="command">vmdk</code></span></dt><dd><div class="para">
						VMware 3 and 4 compatible image format.
					</div></dd><dt><span class="term"><code class="command">cloop</code></span></dt><dd><div class="para">
						Linux Compressed Loop image, useful only to reuse directly compressed CD-ROM images present for example in the Knoppix CD-ROMs.
					</div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Changing_between_the_KVM_and_Xen_hypervisors-KVM_to_Xen.html"><strong>Prev</strong>23.2.2.Â KVM to Xen</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Next</strong>23.4.Â Overcommitting with KVM</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.6.Â Verifying virtualization extensions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html" title="23.5.Â Modifying /etc/grub.conf"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation.html" title="23.7.Â Identifying guest type and implementation"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedorapr
 oject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Verifying_virtualization_extensions">23.6.Â Verifying virtualization extensions</h2></div></div></div><div class="para">
			Use this section to determine whether your system has the hardware virtualization extensions. Virtualization extensions (Intel VT or AMD-V) are required for full virtualization.
		</div><div class="note"><h2>Can I use virtualization without the virtualization extensions?</h2><div class="para">
				If hardware virtualization extensions are not present you can use Xen para-virtualization with the fedora <span class="package">kernel-xen</span> package.
			</div></div><div class="para">
			Run the following command to verify the CPU virtualization extensions are available:
		</div><pre class="screen">$ grep -E 'svm|vmx' /proc/cpuinfo
</pre><div class="para">
			The following output contains a <code class="computeroutput">vmx</code> entry indicating an Intel processor with the Intel VT extensions:
		</div><pre class="screen">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
</pre><div class="para">
			The following output contains an <code class="computeroutput">svm</code> entry indicating an AMD processor with the AMD-V extensions:
		</div><pre class="screen">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
</pre><div class="para">
			The "<code class="computeroutput">flags:</code>" content may appear multiple times for each hyperthread, core or CPU on in the system.
		</div><div class="para">
			The virtualization extensions may be disabled in the BIOS. If the extensions do not appear or full virtualization does not work refer to <a class="xref" href="sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html#proc-Virtualization_Guide-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS-Enabling_virtualization_extensions_in_BIOS" title="ProcedureÂ 26.1.Â Enabling virtualization extensions in BIOS">ProcedureÂ 26.1, â€œEnabling virtualization extensions in BIOSâ€</a>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_etcgrub.conf.html"><strong>Prev</strong>23.5.Â Modifying /etc/grub.conf</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Identifying_guest_type_and_implementation.html"><strong>Next</strong>23.7.Â Identifying guest type and implementation</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>23.12.Â Very Secure ftpd</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Tips_and_tricks.html" title="ChapterÂ 23.Â Tips and tricks"/><link rel="prev" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_the_Xen_hypervisor.html" title="23.11.Â Modifying the Xen hypervisor"/><link rel="next" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html" title="23.13.Â Configuring LUN Persistence"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Conten
 t/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_the_Xen_hypervisor.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Tips_and_tricks-Very_Secure_ftpd">23.12.Â Very Secure <code class="systemitem">ftpd</code></h2></div></div></div><div class="para">
			<code class="systemitem">vsftpd</code> can provide access to installation trees for para-virtualized guests  or other data. If you have not installed <code class="systemitem">vsftpd</code> during the server installation you can grab the RPM package from your <code class="filename">Server</code> directory of your installation media and install it using the <code class="command">rpm -ivh vsftpd*.rpm</code> (note that the RPM package must be in your current directory).
		</div><div class="orderedlist"><ol><li><div class="para">
					To configure <code class="systemitem">vsftpd</code>, edit <code class="filename">/etc/passwd</code> using <code class="command">vipw</code> and change the ftp user's home directory to the directory where you are going to keep the installation trees for your para-virtualized guests. An example entry for the FTP user would look like the following:
				</div><pre class="screen">ftp:x:14:50:FTP User:/xen/pub:/sbin/nologin
</pre></li><li><div class="para">
					to have <code class="systemitem">vsftpd</code> start automatically during system boot use the chkconfig utility to enable the automatic start up of <code class="systemitem">vsftpd</code>.
				</div></li><li><div class="para">
					verify that <code class="systemitem">vsftpd</code> is not enabled using the <code class="command">chkconfig --list vsftpd</code>:
				</div><pre class="screen">$ chkconfig --list vsftpd
vsftpd          0:off   1:off   2:off   3:off   4:off   5:off   6:off
</pre></li><li><div class="para">
					run the <code class="command">chkconfig --levels 345 vsftpd on</code> to start vsftpd automatically for run levels 3, 4 and 5.
				</div></li><li><div class="para">
					use the <code class="command">chkconfig --list vsftpd</code> command to verify vsftdp has been enabled to start during system boot:
				</div><pre class="screen">$ chkconfig --list vsftpd
vsftpd          0:off   1:off   2:off   3:on    4:on    5:on    6:off
</pre></li><li><div class="para">
					use the <code class="command">service vsftpd start vsftpd</code> to start the vsftpd service:
				</div><pre class="screen">$service vsftpd start vsftpd
Starting vsftpd for vsftpd:                  [  OK  ]
</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Tips_and_tricks-Modifying_the_Xen_hypervisor.html"><strong>Prev</strong>23.11.Â Modifying the Xen hypervisor</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Tips_and_tricks-Configuring_LUN_Persistence.html"><strong>Next</strong>23.13.Â Configuring LUN Persistence</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-A_missing_localhost_entry_causes_virt_manager_to_fail.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.9.Â A missing localhost entry causes virt-manager to fail</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-Fully_virtualized_64_bit_guest_fails_to_boot.html" title="26.8.Â Fully-virtualized 64 bit guest fails to boot"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-Microcode_error_during_guest_boot.html" title="26.10.Â Microcode error during guest boot"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></
 a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Fully_virtualized_64_bit_guest_fails_to_boot.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Microcode_error_during_guest_boot.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting-A_missing_localhost_entry_causes_virt_manager_to_fail">26.9.Â A missing localhost entry causes virt-manager to fail</h2></div></div></div><div class="para">
			The <code class="command">virt-manager</code> application may fail to launch and display an error such as â€œ<code class="computeroutput">Unable to open a connection to the Xen hypervisor/daemon</code>â€. This is usually caused by a missing <code class="systemitem">localhost</code> entry in the <code class="filename">/etc/hosts</code> file. Verify that you indeed have a <code class="systemitem">localhost</code> entry and if it is missing from <code class="filename">/etc/hosts</code> and insert a new entry for <code class="systemitem">localhost</code> if it is not present. An incorrect <code class="filename">/etc/hosts</code> may resemble the following:
		</div><pre class="screen"># Do not remove the following line, or various programs
# that require network functionality will fail.
localhost.localdomain localhost
</pre><div class="para">
			The correct entry should look similar to the following:
		</div><pre class="screen"># Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
localhost.localdomain localhost
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Fully_virtualized_64_bit_guest_fails_to_boot.html"><strong>Prev</strong>26.8.Â Fully-virtualized 64 bit guest fails to boot</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Microcode_error_during_guest_boot.html"><strong>Next</strong>26.10.Â Microcode error during guest boot</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.2.Â After rebooting Xen-based guests the console freezes</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-Virtualized_Ethernet_devices_are_not_found_by_networking_tools.html" title="26.3.Â Virtualized Ethernet devices are not found by networking tools"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class=
 "right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Troubleshooting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Virtualized_Ethernet_devices_are_not_found_by_networking_tools.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes">26.2.Â After rebooting Xen-based guests the console freezes</h2></div></div></div><div class="para">
			Occasionally, a Xen guest's console freezes when the guest boots. The console still displays messages but the user cannot log in.
		</div><div class="para">
			To fix this issue add the following line to the <code class="filename">/etc/inittab</code> file:
		</div><pre class="screen">1:12345:respawn:/sbin/mingetty xvc0
</pre><div class="para">
			After saving the file, reboot. The console session should now be interactive as expected.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Troubleshooting.html"><strong>Prev</strong>ChapterÂ 26.Â Troubleshooting</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Virtualized_Ethernet_devices_are_not_found_by_networking_tools.html"><strong>Next</strong>26.3.Â Virtualized Ethernet devices are not found ...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.13.Â Enabling Intel VT and AMD-V virtualization hardware extensions in BIOS</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine.html" title="26.12.Â Python depreciation warning messages when starting a virtual machine"/><link rel="next" href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html" title="ChapterÂ 27.Â Troubleshooting the Xen para-virtualized drivers"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fe
 doraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></div></div><div class="para">
			This section describes how to identify hardware virtualization extensions and enable them in your BIOS if they are disabled.
		</div><div class="para">
			The Intel VT extensions can be disabled in the BIOS. Certain laptop vendors have disabled the Intel VT extensions by default in their CPUs.
		</div><div class="para">
			The virtualization extensions can not be disabled in the BIOS for AMD-V ( capable processors installed in a Rev 2 socket.
		</div><div class="para">
			The virtualization extensions are sometimes disabled in BIOS, usually by laptop manufacturers. Refer to <a class="xref" href="sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html" title="26.13.Â Enabling Intel VT and AMD-V virtualization hardware extensions in BIOS">SectionÂ 26.13, â€œEnabling Intel VT and AMD-V virtualization hardware extensions in BIOSâ€</a> for instructions on enabling disabled virtualization extensions.
		</div><div class="para">
			Verify the virtualization extensions are enabled in BIOS. The BIOS settings for <span class="trademark">Intel</span>Â® VT or AMD-V are usually in the <span class="guimenuitem"><strong>Chipset</strong></span> or <span class="guimenuitem"><strong>Processor</strong></span> menus. The menu names may vary from this guide, the virtualization extension settings may be found in <span class="guilabel"><strong>Security Settings</strong></span> or other non standard menu names.
		</div><div class="procedure" id="proc-Virtualization_Guide-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS-Enabling_virtualization_extensions_in_BIOS"><h6>ProcedureÂ 26.1.Â Enabling virtualization extensions in BIOS</h6><ol class="1"><li><div class="para">
					Reboot the computer and open the system's BIOS menu. This can usually be done by pressing <span class="guibutton"><strong>delete</strong></span> or <span class="keycap"><strong>Alt</strong></span> + <span class="keycap"><strong>F4</strong></span>.
				</div></li><li><div class="para">
					Select <span class="guilabel"><strong>Restore Defaults</strong></span>, and then select <span class="guilabel"><strong>Save & Exit</strong></span>.
				</div></li><li><div class="para">
					Power off the machine and disconnect the power supply.
				</div></li><li><div class="para">
					Power on the machine and open the <span class="guilabel"><strong>BIOS Setup Utility</strong></span>. Open the <span class="guilabel"><strong>Processor</strong></span> section and enable <span class="trademark"><span class="guilabel"><strong>Intel</strong></span></span>Â®<span class="guilabel"><strong>Virtualization Technology</strong></span> or <span class="guilabel"><strong>AMD-V</strong></span>. The values may also be called <span class="guilabel"><strong>Virtualization Extensions</strong></span> on some machines. Select <span class="guilabel"><strong>Save & Exit</strong></span>.
				</div></li><li><div class="para">
					Power off the machine and disconnect the power supply.
				</div></li><li><div class="para">
					Run <code class="command">cat /proc/cpuinfo | grep vmx svm</code>. If the command outputs, the virtualization extensions are now enabled. If there is no output your system may not have the virtualization extensions or the correct BIOS setting enabled.
				</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine.html"><strong>Prev</strong>26.12.Â Python depreciation warning messages when ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html"><strong>Next</strong>ChapterÂ 27.Â Troubleshooting the Xen para-virtuali...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-Failed_domain_creation_caused_by_a_memory_shortage.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.5.Â Failed domain creation caused by a memory shortage</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-Loop_device_errors.html" title="26.4.Â Loop device errors"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error.html" title="26.6.Â Wrong kernel image error"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_C
 ontent/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Loop_device_errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting-Failed_domain_creation_caused_by_a_memory_shortage">26.5.Â Failed domain creation caused by a memory shortage</h2></div></div></div><div class="para">
			This may cause a domain to fail to start. The reason for this is there is not enough memory available or <code class="command">dom0</code> has not ballooned down enough to provide space for a recently created or started guest. In your <code class="filename">/var/log/xen/xend.log</code>, an example error message indicating this has occurred: 
<pre class="screen">[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
</pre>
			 You can verify the amount of memory currently used by <code class="command">dom0</code> with the command â€œ<code class="command">xm list Domain-0</code>â€. If <code class="command">dom0</code> is not ballooned down you can use the command â€œ<code class="command">xm mem-set Domain-0 NewMemSize</code>â€ where <code class="computeroutput">NewMemSize</code> should be a smaller value.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Loop_device_errors.html"><strong>Prev</strong>26.4.Â Loop device errors</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error.html"><strong>Next</strong>26.6.Â Wrong kernel image error</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-Fully_virtualized_64_bit_guest_fails_to_boot.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.8.Â Fully-virtualized 64 bit guest fails to boot</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error_non_PAE_kernel_on_a_PAE_platform.html" title="26.7.Â Wrong kernel image error - non-PAE kernel on a PAE platform"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-A_missing_localhost_entry_causes_virt_manager_to_fail.html" title="26.9.Â A missing localhost entry causes virt-manager to fail"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Co
 mmon_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error_non_PAE_kernel_on_a_PAE_platform.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-A_missing_localhost_entry_causes_virt_manager_to_fail.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting-Fully_virtualized_64_bit_guest_fails_to_boot">26.8.Â Fully-virtualized 64 bit guest fails to boot</h2></div></div></div><div class="para">
			If you have moved the configuration file to Fedor causing your fully-virtualized guest fails to boot and present the error, â€œ<code class="computeroutput">Your CPU does not support long mode. Use a 32 bit distribution</code>â€. The problem is a missing or incorrect <code class="command">pae</code> setting. Make sure you have an entry â€œ<code class="command">pae=1</code>â€ in your guest's configuration file.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error_non_PAE_kernel_on_a_PAE_platform.html"><strong>Prev</strong>26.7.Â Wrong kernel image error - non-PAE kernel o...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-A_missing_localhost_entry_causes_virt_manager_to_fail.html"><strong>Next</strong>26.9.Â A missing localhost entry causes virt-manag...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-Loop_device_errors.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.4.Â Loop device errors</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-Virtualized_Ethernet_devices_are_not_found_by_networking_tools.html" title="26.3.Â Virtualized Ethernet devices are not found by networking tools"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-Failed_domain_creation_caused_by_a_memory_shortage.html" title="26.5.Â Failed domain creation caused by a memory shortage"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/imag
 e_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Virtualized_Ethernet_devices_are_not_found_by_networking_tools.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Failed_domain_creation_caused_by_a_memory_shortage.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting-Loop_device_errors">26.4.Â Loop device errors</h2></div></div></div><div class="para">
			If file based guest images are used you may have to increase the number of configured loop devices. The default configuration allows up to 8 active loop devices. If more than 8 file based guests or loop devices are needed the number of loop devices configured can be adjusted in <code class="filename">/etc/modprobe.conf</code>. Edit <code class="filename">/etc/modprobe.conf</code> and add the following line to it:
		</div><pre class="screen">                options loop max_loop=64
</pre><div class="para">
			This example uses 64 but you can specify another number to set the maximum loop value. You may also have to implement loop device backed guests on your system. To employ loop device backed guests for a para-virtualized guest, use the <code class="command">phy: block device</code> or <code class="command">tap:aio</code> commands. To employ loop device backed guests for a full virtualized system, use the <code class="command">phy: device</code> or <code class="command">file: file</code> commands.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Virtualized_Ethernet_devices_are_not_found_by_networking_tools.html"><strong>Prev</strong>26.3.Â Virtualized Ethernet devices are not found ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Failed_domain_creation_caused_by_a_memory_shortage.html"><strong>Next</strong>26.5.Â Failed domain creation caused by a memory s...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-Microcode_error_during_guest_boot.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.10.Â Microcode error during guest boot</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-A_missing_localhost_entry_causes_virt_manager_to_fail.html" title="26.9.Â A missing localhost entry causes virt-manager to fail"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-Wrong_bridge_configured_on_the_guest_causing_hot_plug_script_timeouts.html" title="26.11.Â Wrong bridge configured on the guest causing hot plug script timeouts"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"
 ><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-A_missing_localhost_entry_causes_virt_manager_to_fail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Wrong_bridge_configured_on_the_guest_causing_hot_plug_script_timeouts.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting-Microcode_error_during_guest_boot">26.10.Â Microcode error during guest boot</h2></div></div></div><div class="para">
			During the boot phase of your virtual machine you may see an error message similar to: 
<pre class="screen">Applying Intel CPU microcode update: FATAL: Module microcode not found.
ERROR: Module microcode does not exist in /proc/modules
</pre>
			 As the virtual machine is running on virtual CPUs there is no point updating the microcode. Disabling the microcode update for your virtual machines will stop this error: 
<pre class="screen">/sbin/service microcode_ctl stop
/sbin/chkconfig --del microcode_ctl
</pre>
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-A_missing_localhost_entry_causes_virt_manager_to_fail.html"><strong>Prev</strong>26.9.Â A missing localhost entry causes virt-manag...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Wrong_bridge_configured_on_the_guest_causing_hot_plug_script_timeouts.html"><strong>Next</strong>26.11.Â Wrong bridge configured on the guest causi...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.12.Â Python depreciation warning messages when starting a virtual machine</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-Wrong_bridge_configured_on_the_guest_causing_hot_plug_script_timeouts.html" title="26.11.Â Wrong bridge configured on the guest causing hot plug script timeouts"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html" title="26.13.Â Enabling Intel VT and AMD-V virtualization hardware extensions in BIOS"/></head><body class="dra
 ft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Wrong_bridge_configured_on_the_guest_causing_hot_plug_script_timeouts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine">26.12.Â Python depreciation warning messages when starting a virtual machine</h2></div></div></div><div
  class="para">
			Sometimes Python will generate a message like the one below, these are often caused by either an invalid or incorrect configuration file. A configuration file containing non-ascii characters will cause these errors.The solution is to correct the configuration file or generate a new one.
		</div><div class="para">
			Another cause is an incorrect configuration file in your current working directory. â€œ<code class="command">xm create</code>â€ will look in the current directory for a configuration file and then in <code class="filename">/etc/xen</code>
<pre class="screen"># xm shutdown win2k3xen12
# xm create win2k3xen12
Using config file "win2k3xen12".
/usr/lib64/python2.4/site-packages/xen/xm/opts.py:520: DeprecationWarning:
Non-ASCII character '\xc0' in file win2k3xen12 on line 1, but no encoding
declared; see http://www.python.org/peps/pep-0263.html for details
execfile(defconfig, globs, locs)
Error: invalid syntax (win2k3xen12, line 1)
</pre>
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Wrong_bridge_configured_on_the_guest_causing_hot_plug_script_timeouts.html"><strong>Prev</strong>26.11.Â Wrong bridge configured on the guest causi...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html"><strong>Next</strong>26.13.Â Enabling Intel VT and AMD-V virtualization...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-Virtualized_Ethernet_devices_are_not_found_by_networking_tools.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.3.Â Virtualized Ethernet devices are not found by networking tools</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes.html" title="26.2.Â After rebooting Xen-based guests the console freezes"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-Loop_device_errors.html" title="26.4.Â Loop device errors"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a c
 lass="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Loop_device_errors.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting-Virtualized_Ethernet_devices_are_not_found_by_networking_tools">26.3.Â Virtualized Ethernet devices are not found by networking tools</h2></div></div></div><div class="para">
			The networking tools cannot identify the <code class="computeroutput">Xen Virtual Ethernet</code> networking card inside the guest operation system you should execute <code class="command">cat /etc/modprobe.conf</code> (in Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5) or <code class="command">cat /etc/modules.conf</code> (in Red Hat Enterprise Linux 3). The output should contain the line â€œ<code class="command">alias eth0 xen-vnif</code>â€ and a similar line for each additional interface. To fix this problem you will need to add the aliasing lines (for example, <code class="command">alias eth0 xen-vnif</code>) for every para-virtualized interface for the guest.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-After_rebooting_Xen_based_guests_the_console_freezes.html"><strong>Prev</strong>26.2.Â After rebooting Xen-based guests the consol...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Loop_device_errors.html"><strong>Next</strong>26.4.Â Loop device errors</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-Wrong_bridge_configured_on_the_guest_causing_hot_plug_script_timeouts.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.11.Â Wrong bridge configured on the guest causing hot plug script timeouts</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-Microcode_error_during_guest_boot.html" title="26.10.Â Microcode error during guest boot"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine.html" title="26.12.Â Python depreciation warning messages when starting a virtual machine"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img
  src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Microcode_error_during_guest_boot.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></div></div><div class="para">
			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 your network topology, such as Xen bridge numbering.
		</div><div class="para">
			If you try to start a guest which has an incorrect or non-existent virtual network bridge configured you will see the following error after starting the guest 
<pre class="screen"># xm create r5b2-mySQL01
Using config file "r5b2-mySQL01".
Going to boot Fedora (2.6.23.14-107.fc8xen)
kernel: /vmlinuz-2.6.23.14-107.fc8xen
initrd: /initrd-2.6.23.14-107.fc8xen.img
Error: Device 0 (vif) could not be connected. Hotplug scripts not working
</pre>
			 In <code class="filename">/var/log/xen/xen-hotplug.log</code> you will see the following error being logged 
<pre class="screen">bridge xenbr1 does not exist!
</pre>
			 and in <code class="filename">/var/log/xen/xend.log</code> you will see the following messages (or similar messages) being logged 
<pre class="screen">[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:07:08 xend 3874] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2006-12-14 15:08:48 xend.XendDomainInfo 3874] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=2
[2006-12-14 15:08:48 xend.XendDomainInfo 3874] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(2)
[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) 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)
hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
</pre>
			 To resolve this issue edit your guest's configuration file and modify the <code class="command">vif</code> entry to reflect your local configuration. For example if your local configuration is using <code class="command">xenbr0</code> as its default bridge you should modify your <code class="command">vif</code> entry in your configuration file from 
<pre class="screen">vif = [ 'mac=00:16:3e:49:1d:11, bridge=xenbr1', ]
</pre>
			 to 
<pre class="screen">vif = [ 'mac=00:16:3e:49:1d:11, bridge=xenbr0', ]
</pre>
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Microcode_error_during_guest_boot.html"><strong>Prev</strong>26.10.Â Microcode error during guest boot</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Python_depreciation_warning_messages_when_starting_a_virtual_machine.html"><strong>Next</strong>26.12.Â Python depreciation warning messages when ...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.6.Â Wrong kernel image error</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-Failed_domain_creation_caused_by_a_memory_shortage.html" title="26.5.Â Failed domain creation caused by a memory shortage"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error_non_PAE_kernel_on_a_PAE_platform.html" title="26.7.Â Wrong kernel image error - non-PAE kernel on a PAE platform"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_
 left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Failed_domain_creation_caused_by_a_memory_shortage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error_non_PAE_kernel_on_a_PAE_platform.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error">26.6.Â Wrong kernel image error</h2></div></div></div><div class="para">
			Para-virtualized guests cannot use the kernel-xen kernel. Use only the standard kernel for para-virtualized guests.
		</div><div class="para">
			If you try to boot a non kernel-xen kernel as a para-virtualized guest the following error message appears: 
<pre class="screen"># xm create testVM
Using config file "./testVM".
Going to boot Fedora (2.6.23.14-107.fc8)
kernel: /vmlinuz-2.6.23.14-107.fc8
initrd: /initrd-2.6.23.14-107.fc8.img
Error: (22, 'Invalid argument')
</pre>
			 In the above error you can see that the kernel line shows that it's trying to boot a non-xen kernel. The correct entry in the example is â€<code class="command">kernel: /vmlinuz-2.6.23.14-107.fc8xen</code>â€.
		</div><div class="para">
			The solution is to verify you have indeed installed a kernel-xen in your guest and it is the default kernel to boot in your <code class="filename">/etc/grub.conf</code> configuration file.
		</div><div class="para">
			If you have <code class="command">kernel-xen</code> installed in your guest you can start your guest:
		</div><pre class="screen">xm create -c GuestName
</pre><div class="para">
			Where <code class="command">GuestName</code> is the name of the guest. The previous command will present you with the <span class="application"><strong>GRUB</strong></span> boot loader screen and allow you to select the kernel to boot. You will have to choose the kernel-xen kernel to boot. Once the guest has completed the boot process you can log into the guest and edit <code class="command">/etc/grub.conf</code> to change the default boot kernel to your kernel-xen. Simply change the line â€œ<code class="command">default=X</code>â€ (where X is a number starting at '<code class="command">0</code>') to correspond to the entry with your kernel-xen line. The numbering starts at '<code class="command">0</code>' so if your kernel-xen entry is the second entry you would enter '<code class="command">1</code>' as the default,for example â€œ<code class="command">default=1</code>â€.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Failed_domain_creation_caused_by_a_memory_shortage.html"><strong>Prev</strong>26.5.Â Failed domain creation caused by a memory s...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error_non_PAE_kernel_on_a_PAE_platform.html"><strong>Next</strong>26.7.Â Wrong kernel image error - non-PAE kernel o...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error_non_PAE_kernel_on_a_PAE_platform.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>26.7.Â Wrong kernel image error - non-PAE kernel on a PAE platform</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error.html" title="26.6.Â Wrong kernel image error"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting-Fully_virtualized_64_bit_guest_fails_to_boot.html" title="26.8.Â Fully-virtualized 64 bit guest fails to boot"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="r
 ight" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Fully_virtualized_64_bit_guest_fails_to_boot.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></div></div><div class="para">
			If you to boot a non-PAE para-virtualized guest you will see the error message below. It basically indicates you are trying to run a guest kernel on your Hypervisor which at this time is not supported. The Xen hypervisor presently only supports PAE and 64 bit para-virtualized guest kernels. 
<pre class="screen"># xm create -c va-base 
Using config file "va-base".
Error: (22, 'Invalid argument')
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] ERROR (XendDomainInfo:202) Domain construction failed
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", 
	line 195, in  create vm.initDomain()
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", 
	line 1363, in initDomain raise VmError(str(exn))
VmError: (22, 'Invalid argument')
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=1
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(1)
</pre>
			 If you need to run a 32 bit or non-PAE kernel you will need to run your guest as a fully-virtualized virtual machine. The rules for hypervisor compatibility are: 
			<div class="itemizedlist"><ul><li><div class="para">
						para-virtualized guests must match the architecture type of your hypervisor. To run a 32 bit PAE guest you must have a 32 bit PAE hypervisor.
					</div></li><li><div class="para">
						to run a 64 bit para-virtualized guest your Hypervisor must be a 64 bit version too.
					</div></li><li><div class="para">
						fully virtualized guests your hypervisor must be 32 bit or 64 bit for 32 bit guests. You can run a 32 bit (PAE and non-PAE) guest on a 32 bit or 64 bit hypervisor.
					</div></li><li><div class="para">
						to run a 64 bit fully virtualized guest your hypervisor must be 64 bit too.
					</div></li></ul></div>
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting-Wrong_kernel_image_error.html"><strong>Prev</strong>26.6.Â Wrong kernel image error</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting-Fully_virtualized_64_bit_guest_fails_to_boot.html"><strong>Next</strong>26.8.Â Fully-virtualized 64 bit guest fails to boot</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.9.Â Accessing data on guest disk image</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html" title="25.8.Â Fully virtualized guest console access"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Common_Xen_problems.html" title="25.10.Â Common Xen problems"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedora
 project.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Common_Xen_problems.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image">25.9.Â Accessing data on guest disk image</h2></div></div></div><div class="para">
			You can use two separate applications that assist you in accessing data from within a guest disk image. Before using these tools, you must shut down the guests. Accessing the file system from the guest and dom0 could potentially harm your system.
		</div><div class="para">
			You can use the kpartx application to handle partitioned disks or LVM volume groups:
		</div><pre class="screen">yum install kpartx
</pre><pre class="screen">kpartx -av /dev/xen/guest1
add map guest1p1 : 0 208782 linear /dev/xen/guest1 63
add map guest1p2: 0 16563015 linear /dev/xen/guest1 208845
</pre><div class="para">
			To access LVM volumes on a second partition, you must rescan LVM with vgscan and activate the volume group on the partition (called <code class="filename">VolGroup00</code> by default) by using the <code class="command">vgchange -ay</code> command:
		</div><pre class="screen"># kpartx -a /dev/xen/guest1
#vgscan
Reading all physical volumes . This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
# vgchange -ay VolGroup00
2 logical volumes in volume group VolGroup00 now active.
# lvs
LV VG Attr Lsize Origin Snap% Move Log Copy%
LogVol00 VolGroup00 -wi-a- 5.06G
LogVol01 VolGroup00 -wi-a- 800.00M
# mount /dev/VolGroup00/LogVol00 /mnt/
....
#umount /mnt/
#vgchange -an VolGroup00
#kpartx -d /dev/xen/guest1
</pre><div class="para">
			You must remember to deactivate the logical volumes with <code class="command"> vgchange -an</code>, remove the partitions with<code class="command"> kpartx-d </code>, and delete the loop device with <code class="command">losetup -d </code> when you finish.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html"><strong>Prev</strong>25.8.Â Fully virtualized guest console access</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Common_Xen_problems.html"><strong>Next</strong>25.10.Â Common Xen problems</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Common_Xen_problems.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.10.Â Common Xen problems</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image.html" title="25.9.Â Accessing data on guest disk image"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html" title="25.11.Â Guest creation errors"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img 
 src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Common_Xen_problems">25.10.Â Common Xen problems</h2></div></div></div><div class="para">
			When attempting to start the <code class="command">xend</code> service, nothing happens. Type <code class="command">virsh list</code> and receive the following:
		</div><pre class="screen">Error: Error connecting to xend: Connection refused. Is xend running?
</pre><div class="para">
			Try to run <code class="command">xend start</code> manually and receive more errors:
		</div><pre class="screen">Error: Could not obtain handle on privileged command interfaces (2 = No such file or directory)
Traceback (most recent call last:)

File "/usr/sbin/xend/", line 33 in ?

from xen.xend.server. import SrvDaemon

File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py" , line 26 in ?

from xen.xend import XendDomain

File "/usr//lib/python2.4/site-packages/xen/xend/XendDomain.py" , line 33, in ?

from xen.xend import XendDomainInfo

File "/usr/lib/python2.4/site-packages/xen/xend/image.py" , line37, in ?

import images

File "/usr/lib/python2.4/site-packages/xen/xend/image.py" , line30, in ?

xc = xen.lowlevel.xc.xc ()

RuntimeError: (2, 'No such file or directory' )
</pre><div class="para">
			What has most likely happened here is that you rebooted your host into a kernel that is not a <code class="command">kernel-xen</code> kernel. To correct this, you must select the <code class="command">kernel-xen</code> kernel at boot time (or set the <code class="command">kernel-xen</code> kernel to the default in the <code class="command">grub.conf</code> file.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image.html"><strong>Prev</strong>25.9.Â Accessing data on guest disk image</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html"><strong>Next</strong>25.11.Â Guest creation errors</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.8.Â Fully virtualized guest console access</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Para_virtualized_guest_console_access.html" title="25.7.Â Para-virtualized guest console access"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image.html" title="25.9.Â Accessing data on guest disk image"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="
 right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Para_virtualized_guest_console_access.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access">25.8.Â Fully virtualized guest console access</h2></div></div></div><div class="para">
			Fully virtualized guest operating systems automatically has a text console configured for use, but the difference is the kernel guest is not configured. To enable the guest virtual serial console to work with the Full Virtualized guest, you must modify the guest's <code class="command">grub.conf</code> file, and include the <code class="command">'console =ttyS0 console=tty0'</code> parameter. This ensures that the kernel messages are sent to the virtual serial console (and the normal graphical console). If you plan to use the virtual serial console in a full virtualized guest, you must edit the configuration file in the <code class="command">/etc/xen/</code> directory. On the host domain, access the serial console with the following command:
		</div><pre class="screen"># virsh console
</pre><div class="para">
			You can also use <code class="command">virt-manager</code> to display the virtual text console. In the Virtual Machine Details window, select <span class="guilabel"><strong>Serial Console</strong></span> from the <span class="guilabel"><strong>View</strong></span> menu.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Para_virtualized_guest_console_access.html"><strong>Prev</strong>25.7.Â Para-virtualized guest console access</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Accessing_data_on_guest_disk_image.html"><strong>Next</strong>25.9.Â Accessing data on guest disk image</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Guest_configuration_files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.13.Â Guest configuration files</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_from_fully_virtualized_guests.html" title="25.12.3.Â Serial console output from fully virtualized guests"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html" title="25.14.Â Interpreting Xen error messages"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt
 ="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_from_fully_virtualized_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_configuration_files">25.13.Â Guest configuration files</h2></div></div></div><div class="para">
			When you create guests with the virt-manager or virt-install tools on Linux 5, the guests configuration files are created automatically in the <code class="filename">/etc/xen</code> directory. The example below is a typical a para-virtualized guest configuration file:
		</div><pre class="screen">name = "rhel5vm01"
memory = "2048"
disk = ['tap:aio:/var/lib/libvirt/images/rhel5vm01.dsk,xvda,w',]
vif = ["type=ieomu, mac=00:16:3e:09:f0:12 bridge=xenbr0', 
"type=ieomu, mac=00:16:3e:09:f0:13 ]
vnc = 1
vncunused = 1
uuid = "302bd9ce-4f60-fc67-9e40-7a77d9b4e1ed"
bootloader = "/usr/bin/pygrub"
vcpus=2
on_reboot = "restart"
on_crash = "restart"
</pre><div class="para">
			Note that the <code class="command">serial="pty" </code> is the default for the configuration file. This configuration file example is for a fully-virtualized guest:
		</div><pre class="screen">name = "rhel5u5-86_64"
builder = "hvm"
memory = 500
disk = ['/var/lib/libvirt/images/rhel5u5-x86_64.dsk.hda,w']
vif = [ 'type=ioemu, mac=00:16:3e:09:f0:12, bridge=xenbr0', 'type=ieomu, mac=00:16:3e:09:f0:13, bridge=xenbr1']
uuid = "b10372f9-91d7-ao5f-12ff-372100c99af5'
device_model = "/usr/lib64/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader/"
vnc = 1
vncunused = 1
apic = 1
acpi = 1
pae = 1
vcpus =1
serial ="pty" # enable serial console
on_boot = 'restart'
</pre><div class="note"><h2>Xen configuration files</h2><div class="para">
				Editing Xen configuration files is unsupported. Use <code class="command">virsh dumpxml</code> and <code class="command">virsh create</code> (or <code class="command">virsh edit</code>) to edit the <code class="command">libvirt</code> configuration files (xml based) which have error checking and safety checks.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_from_fully_virtualized_guests.html"><strong>Prev</strong>25.12.3.Â Serial console output from fully virtual...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html"><strong>Next</strong>25.14.Â Interpreting Xen error messages</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.11.Â Guest creation errors</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Common_Xen_problems.html" title="25.10.Â Common Xen problems"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html" title="25.12.Â Troubleshooting with serial consoles"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><i
 mg src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Common_Xen_problems.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors">25.11.Â Guest creation errors</h2></div></div></div><div class="para">
			When you attempt to create a guest, you receive an <code class="command">"Invalid argument"</code> error message. This usually means that the kernel image you are trying to boot is incompatible with the hypervisor. An example of this would be if you were attempting to run a non-PAE FC5 kernel on a PAE only FC6 hypervisor.
		</div><div class="para">
			You do a yum update and receive a new kernel, the <code class="command">grub.conf</code> default kernel switches right back to a bare-metal kernel instead of the Virtualization kernel.
		</div><div class="para">
			To correct this problem you must modify the default kernel RPM that resides in the <code class="command">/etc/sysconfig/kernel/</code> directory. You must ensure that <code class="command">kernel-xen</code> parameter is set as the default option in your <code class="command">gb.conf</code> file.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Common_Xen_problems.html"><strong>Prev</strong>25.10.Â Common Xen problems</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html"><strong>Next</strong>25.12.Â Troubleshooting with serial consoles</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.4.Â Important directory locations</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html" title="25.3.Â Log file descriptions"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs.html" title="25.5.Â Troubleshooting with the logs"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img sr
 c="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations">25.4.Â Important directory locations</h2></div></div></div><div class="para">
			There are other utilities and log files you should be aware of for tracking errors and troubleshooting problems with Xen:
		</div><div class="itemizedlist"><ul><li><div class="para">
					Virtualized guest images reside in the <code class="command">/var/lib/libvirt/images</code> directory.
				</div></li></ul></div><div class="itemizedlist"><ul><li><div class="para">
					When you restart the <code class="command">xend</code> daemon, it updates the <code class="command">xend-database</code> that resides in the <code class="command">/var/lib/xen/xend-db</code> directory.
				</div></li></ul></div><div class="itemizedlist"><ul><li><div class="para">
					Virtual machine dumps (that you perform with the <code class="command">xm dump-core</code> command) resides in the <code class="command">/var/lib/xen/dumps</code> directory.
				</div></li></ul></div><div class="itemizedlist"><ul><li><div class="para">
					The <code class="command">/etc/xen</code> directory contains the configuration files that you use to manage system resources. The <code class="command">xend</code> daemon configuration file is <code class="command">/etc/xen/xend-config.sxp</code>. This file can be edited to implement system-wide changes and configure the networking. However, manually editing files in the <code class="filename">/etc/xen/</code> folder is not advised.
				</div></li></ul></div><div class="itemizedlist"><ul><li><div class="para">
					The <code class="command">proc</code> folders are another resource that allows you to gather system information. These proc entries reside in the <code class="filename">/proc/xen</code> directory:
				</div></li></ul></div><div class="para">
			<code class="command">/proc/xen/capabilities</code>
		</div><div class="para">
			<code class="command">/proc/xen/balloon </code>
		</div><div class="para">
			<code class="command"> /proc/xen/xenbus/ </code>
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html"><strong>Prev</strong>25.3.Â Log file descriptions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs.html"><strong>Next</strong>25.5.Â Troubleshooting with the logs</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.14.Â Interpreting Xen error messages</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_configuration_files.html" title="25.13.Â Guest configuration files"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-The_layout_of_the_log_directories.html" title="25.15.Â The layout of the log directories"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedor
 aproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_configuration_files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-The_layout_of_the_log_directories.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages">25.14.Â Interpreting Xen error messages</h2></div></div></div><div class="para">
			You receive the following error:
		</div><pre class="screen">failed domain creation due to memory shortage, unable to balloon domain0
</pre><div class="para">
			A domain can fail if there is not enough RAM available. Domain0 does not balloon down enough to provide space for the newly created guest. You can check the <code class="filename">xend.log</code> file for this error:
		</div><pre class="screen">[2006-12-21] 20:33:31 xend 3198] DEBUG (balloon:133) Balloon: 558432 Kib free; 0 to scrub; need 1048576; retries: 20
[2006-12-21] 20:33:31 xend. XendDomainInfo 3198] ERROR (XendDomainInfo: 202
Domain construction failed
</pre><div class="para">
			You can check the amount of memory in use by domain0 by using the <code class="command">xm list domain0</code> command. If dom0 is not ballooned down, you can use the command <code class="command">virsh setmem dom0 NewMemSize</code> to check memory.
		</div><div class="para">
			You receive the following error:
		</div><pre class="screen">wrong kernel image: non-PAE kernel on a PAE
</pre><div class="para">
			This message indicates that you are trying to run an unsupported guest kernel image on your hypervisor. This happens when you try to boot a non-PAE, para-virtualized guest kernel on a Fedora host. The Fedora <span class="package">kernel-xen</span> package only supports guest kernels with PAE and 64 bit architectures.
		</div><div class="para">
			Type this command:
		</div><pre class="screen"># xm create -c va-base

Using config file "va-base"
Error: (22, 'invalid argument')
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] ERRORs
(XendDomainInfo:202) Domain construction failed

Traceback (most recent call last)
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195 in create vm.initDomain()
File " /usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1363 in initDomain raise VmError(str(exn))
VmError: (22, 'Invalid argument')
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] DEBUG (XenDomainInfo: 1449]
XendDlomainInfo.destroy: domain=1
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] DEBUG (XenDomainInfo: 1457]
XendDlomainInfo.destroy:Domain(1)
</pre><div class="para">
			If you need to run a 32 bit non-PAE kernel you will need to run your guest as a fully virtualized virtual machine. For para-virtualized guests, if you need to run a 32 bit PAE guest, then you must have a 32 bit PAE hypervisor. For para-virtualized guests, to run a 64 bit PAE guest, then you must have a 64 bit PAE hypervisor. For full virtualization guests you must run a 64 bit guest with a 64 bit hypervisor. The 32 bit PAE hypervisor that comes with Fedora i686 only supports running 32 bit PAE para virtualized and 32 bit fully virtualized guest OSes. The 64 bit hypervisor only supports 64 bit para-virtualized guests.
		</div><div class="para">
			This happens when you move the full virtualized HVM guest onto a Fedora system. Your guest may fail to boot and you will see an error in the console screen. Check the PAE entry in your configuration file and ensure that pae=1.You should use a 32 bit distribution.
		</div><div class="para">
			You receive the following error:
		</div><pre class="screen">Unable to open a connection to the Xen hypervisor or daemon
</pre><div class="para">
			This happens when the virt-manager application fails to launch. This error occurs when there is no localhost entry in the <code class="command">/etc/hosts </code> configuration file. Check the file and verify if the localhost entry is enabled. Here is an example of an incorrect localhost entry:
		</div><pre class="screen"># Do not remove the following line, or various programs
# that require network functionality will fail.
localhost.localdomain localhost
</pre><div class="para">
			Here is an example of a correct localhost entry:
		</div><pre class="screen"># Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
localhost.localdomain. localhost
</pre><div class="para">
			You receive the following error (in the <code class="command">xen-xend.logfile </code>):
		</div><pre class="screen">Bridge xenbr1 does not exist!
</pre><div class="para">
			This happens when the guest's bridge is incorrectly configured and this forces the Xen hotplug scripts to timeout. If you move configuration files between hosts, you must ensure that you update the guest configuration files to reflect network topology and configuration modifications. When you attempt to start a guest that has an incorrect or non-existent Xen bridge configuration, you will receive the following errors:
		</div><pre class="screen"># xm create mySQL01

Using config file " mySQL01"
Going to boot Fedora (2.6.23.14-107.fc8xen)
kernel: /vmlinuz-2.6.23.14-107.fc8xen
initrd: /initrd-2.6.23.14-107.fc8xen.img
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
</pre><div class="para">
			In addition, the <code class="command">xend.log</code> displays the following errors:
		</div><pre class="screen">[2006-11-14 15:07:08 xend 3875] DEBUG (DevController:143) Waiting for devices vif
[2006-11-14 15:07:08 xend 3875] DEBUG (DevController:149) Waiting for 0
[2006-11-14 15:07:08 xend 3875] DEBUG (DevController:464) hotplugStatusCallback

/local/domain/0/backend/vif/2/0/hotplug-status

[2006-11-14 15:08:09 xend.XendDomainInfo 3875] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=2
[2006-11-14 15:08:09 xend.XendDomainInfo 3875] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(2)
[2006-11-14 15:07:08 xend 3875] DEBUG (DevController:464) hotplugStatusCallback

/local/domain/0/backend/vif/2/0/hotplug-status
</pre><div class="para">
			To resolve this problem, open the guest's configuration file found in the <code class="filename">/etc/xen</code> directory. For example, editing the guest <em class="parameter"><code>mySQL01</code></em>
<pre class="screen"># vim /etc/xen/<em class="parameter"><code>mySQL01</code></em>
</pre>
			 Locate the <code class="command">vif</code> entry. Assuming you are using <code class="command">xenbr0</code> as the default bridge, the proper entry should resemble the following:
		</div><pre class="screen"># vif = ['mac=00:16:3e:49:1d:11, bridge=xenbr0',]
</pre><div class="para">
			You receive these python deprecation errors:
		</div><pre class="screen"># xm shutdown win2k3xen12
# xm create win2k3xen12

Using config file "win2k3xen12".

/usr/lib64/python2.4/site-packages/xenxm/opts.py:520: Deprecation Warning:
Non ASCII character '\xc0' in file win2k3xen12 on line 1, but no encoding
declared; see http://www.python.org/peps/pep-0263.html for details

execfile (defconfig, globs, locs,)
Error: invalid syntax 9win2k3xen12, line1)
</pre><div class="para">
			Python generates these messages when an invalid (or incorrect) configuration file. To resolve this problem, you must modify the incorrect configuration file, or you can generate a new one.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_configuration_files.html"><strong>Prev</strong>25.13.Â Guest configuration files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-The_layout_of_the_log_directories.html"><strong>Next</strong>25.15.Â The layout of the log directories</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.3.Â Log file descriptions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html" title="25.2.Â Log files overview"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html" title="25.4.Â Important directory locations"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Cont
 ent/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions">25.3.Â Log file descriptions</h2></div></div></div><div class="para">
			Xen features the <code class="command">xend</code> daemon and <code class="command">qemu-dm </code> process, two utilities that write the multiple log files to the <code class="command">/var/log/xen/</code> directory:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="filename">xend.log</code> is the log file that contains all the data collected by the <code class="command">xend</code> daemon, whether it is a normal system event, or an operator initiated action. All virtual machine operations (such as create, shutdown, destroy and so on) appear in this log. The <code class="command"> xend.log</code> is usually the first place to look when you track down event or performance problems. It contains detailed entries and conditions of the error messages.
				</div></li><li><div class="para">
					<code class="filename">xend-debug.log</code> is the log file that contains records of event errors from <code class="command">xend</code> and the Virtualization subsystems (such as framebuffer, Python scripts, and so on).
				</div></li></ul></div><div class="itemizedlist"><ul><li><div class="para">
					<code class="filename">xen-hotplug-log</code> is the log file that contains data from hotplug events. If a device or a network script does not come online, the event appears here.
				</div></li><li><div class="para">
					<code class="filename">qemu-dm.[PID].log</code> is the log file created by the <code class="command">qemu-dm</code> process for each fully virtualized guest. When using this log file, you must retrieve the given <code class="command">qemu-dm </code> process PID, by using the <code class="command">ps</code> command to examine process arguments to isolate the <code class="command">qemu-dm</code> process on the virtual machine. Note that you must replace the [PID] symbol with the actual PID <code class="command">qemu-dm</code> process.
				</div></li></ul></div><div class="para">
			If you encounter any errors with the Virtual Machine Manager, you can review the generated data in the <code class="command">virt-manager.log</code> file that resides in the <code class="command">/.virt-manager </code> directory. Note that every time you start the Virtual Machine Manager, it overwrites the existing log file contents. Make sure to backup the <code class="command"> virt-manager.log </code> file, before you restart the Virtual Machine manager after a system error.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html"><strong>Prev</strong>25.2.Â Log files overview</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html"><strong>Next</strong>25.4.Â Important directory locations</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.2.Â Log files overview</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html" title="25.3.Â Log file descriptions"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" al
 t="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Troubleshooting_Xen.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Log_files_overview">25.2.Â Log files overview</h2></div></div></div><div class="para">
			When deploying Fedora 12 with Virtualization into your network infrastructure, the host's Virtualization software uses many specific directories for important configuration, log files, and other utilities. All the Xen logs files are standard ASCII files, and accessible with a text editor:
		</div><div class="itemizedlist"><ul><li><div class="para">
					The Xen configuration directory is <code class="filename">/etc/xen/</code>. This directory contains the <code class="command">xend</code> daemon and other virtual machine configuration files. The networking script files are found in the <code class="filename">script</code>s directory).
				</div></li><li><div class="para">
					All of actual log files themselves that you will consult for troubleshooting purposes reside in the <code class="command">/var/log/xen</code> directory.
				</div></li></ul></div><div class="itemizedlist"><ul><li><div class="para">
					You should also know that the default directory for all virtual machine file based disk images resides in the <code class="command">/var/lib/xen</code> directory.
				</div></li><li><div class="para">
					Xen kernel information is stored in the <code class="command">/proc/xen/</code> directory.
				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Troubleshooting_Xen.html"><strong>Prev</strong>ChapterÂ 25.Â Troubleshooting Xen</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Log_file_descriptions.html"><strong>Next</strong>25.3.Â Log file descriptions</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Para_virtualized_guest_console_access.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.7.Â Para-virtualized guest console access</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_serial_console.html" title="25.6.Â Troubleshooting with the serial console"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html" title="25.8.Â Fully virtualized guest console access"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a
 ><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_serial_console.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Para_virtualized_guest_console_access">25.7.Â Para-virtualized guest console access</h2></div></div></div><div class="para">
			Para-virtualized guest operating systems automatically has a virtual text console configured to transmit data to the host operating system. Connect to a guest's virtual console with the following command:
		</div><pre class="screen"># virsh console [guest name, ID or UUID]
</pre><div class="para">
			You can also use <code class="command">virt-manager</code> to display the virtual text console. In the Virtual Machine Details window, select <span class="guilabel"><strong>Serial Console</strong></span> from the <span class="guilabel"><strong>View</strong></span> menu.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_serial_console.html"><strong>Prev</strong>25.6.Â Troubleshooting with the serial console</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Fully_virtualized_guest_console_access.html"><strong>Next</strong>25.8.Â Fully virtualized guest console access</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-The_layout_of_the_log_directories.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.15.Â The layout of the log directories</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html" title="25.14.Â Interpreting Xen error messages"/><link rel="next" href="chap-Virtualization_Guide-Troubleshooting.html" title="ChapterÂ 26.Â Troubleshooting"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Conte
 nt/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Troubleshooting.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-The_layout_of_the_log_directories">25.15.Â The layout of the log directories</h2></div></div></div><div class="para">
			The basic directory structure in a Fedora virtualization environment is as follows:
		</div><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/xen/</code> directory contains</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
								configuration files used by the <code class="systemitem">xend</code> daemon.
							</div></li><li><div class="para">
								the <code class="filename">scripts</code> directory which contains the scripts for Virtualization networking.
							</div></li></ul></div><div class="note"><h2>Tip</h2><div class="para">
							Before moving virtual machine configuration files to a different location, ensure you are not working off old or stale configuration files.
						</div></div></dd><dt><span class="term"><code class="filename">/var/log/xen/</code></span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
								directory holding all Xen related log files.
							</div></li></ul></div></dd><dt><span class="term"><code class="filename">/var/lib/libvirt/images/</code></span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
								The default directory for virtual machine image files.
							</div></li><li><div class="para">
								If you are using a different directory for your virtual machine images make sure you add the directory to your SELinux policy and relabel it before starting the installation.
							</div></li></ul></div></dd><dt><span class="term"><code class="filename">/proc/xen/</code></span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
								The xen related information in the /proc file system.
							</div></li></ul></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Interpreting_Xen_error_messages.html"><strong>Prev</strong>25.14.Â Interpreting Xen error messages</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Troubleshooting.html"><strong>Next</strong>ChapterÂ 26.Â Troubleshooting</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.12.Â Troubleshooting with serial consoles</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html" title="25.11.Â Guest creation errors"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_para_virtualized_guests.html" title="25.12.2.Â Xen serial console output from para-virtualized guests"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="P
 roduct Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_para_virtualized_guests.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles">25.12.Â Troubleshooting with serial consoles</h2></div></div></div><div class="para">
			Linux kernels can output information to serial ports. This is useful for debugging kernel panics and hardware issues with video devices or headless servers. The subsections in this section cover setting up serial console output for machines running Linux virtualization kernels and their virtualized guests.
		</div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_for_Xen">25.12.1.Â Serial console output for Xen</h3></div></div></div><div class="para">
				By default, Xen's serial console is disabled and no data is output from serial ports.
			</div><div class="para">
				To receive kernel information on a serial port modify the <code class="filename">/boot/grub/grub.conf</code> file by setting the appropriate serial device parameters.
			</div><div class="para">
				If your serial console is on <code class="systemitem">com1</code>, modify <code class="filename">/boot/grub/grub.conf</code> by inserting the lines <em class="parameter"><code>com1=115200,8n1</code></em>, <em class="parameter"><code>console=tty0</code></em> and <em class="parameter"><code>console=ttyS0,115200</code></em> where shown.
			</div><pre class="programlisting">title Fedora i386 Xen (2.6.23.14-107.fc8xen)
	root (hd0, 8)
	kernel /boot/xen.gz-2.6.23.14-107.fc8 <em class="parameter"><code>com1=115200,8n1</code></em>
	module /boot/vmlinuz-2.6.23.14-107.fc8xen ro root=LABEL=CentOS5_i386 <em class="parameter"><code>console=tty0</code></em>
	<em class="parameter"><code>console=ttyS0,115200</code></em>
	module /boot/initrd-2.6.23.14-107.fc8xen.img
</pre><div class="para">
				If your serial console is on <code class="systemitem">com2</code>, modify <code class="filename">/boot/grub/grub.conf</code> by inserting the lines <em class="parameter"><code>com2=115200,8n1 console=com2L</code></em>, <em class="parameter"><code>console=tty0</code></em> and <em class="parameter"><code>console=ttyS0,115200</code></em> where shown.
			</div><pre class="programlisting">title Fedora i386 Xen (2.6.23.14-107.fc8xen)
	root (hd0, 8)
	kernel /boot/xen.gz-2.6.23.14-107.fc8 com2=115200,8n1 console=com2L
	module /boot/vmlinuz-2.6.23.14-107.fc8xen ro root=LABEL=CentOS5_i386 console=tty0
	console=ttyS0,115200
	module /boot/initrd-2.6.23.14-107.fc8xen.img
</pre><div class="para">
				Save the changes and reboot the host. The hypervisor outputs serial data on the serial (<code class="systemitem">com1</code>, <code class="systemitem">com2</code> and so on) you selected in the previous step.
			</div><div class="para">
				Note the example using the <code class="systemitem">com2</code> port, the parameter <em class="parameter"><code>console=ttyS0</code></em> on the <em class="parameter"><code>vmlinuz</code></em> line us used. The behavior of every port being used as <em class="parameter"><code>console=ttyS0</code></em> is not standard Linux behavior and is specific to the Xen environment.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_creation_errors.html"><strong>Prev</strong>25.11.Â Guest creation errors</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_para_virtualized_guests.html"><strong>Next</strong>25.12.2.Â Xen serial console output from para-virt...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.5.Â Troubleshooting with the logs</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html" title="25.4.Â Important directory locations"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_serial_console.html" title="25.6.Â Troubleshooting with the serial console"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="ht
 tp://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_serial_console.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs">25.5.Â Troubleshooting with the logs</h2></div></div></div><div class="para">
			When encountering installation issues with Xen, refer to the host system's two logs to assist with troubleshooting. The <code class="command">xend.log</code> file contains the same basic information as when you run the <code class="command">xm log</code> command. This log is found in the <code class="filename">/var/log/</code> directory. Here is an example log entry for when you create a domain running a kernel:
		</div><pre class="screen">[2006-12-27 02:23:02 xend] ERROR (SrvBase: 163) op=create: Error creating domain: (0, 'Error')
Traceback (most recent call list)
File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvBase.py" line 107 in_perform val = op_method (op,req)
File
"/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomainDir.py line 71 in op_create
raise XendError ("Error creating domain: " + str(ex))
XendError: Error creating domain: (0, 'Error')
</pre><div class="para">
			The other log file, <code class="command"> xend-debug.log</code>, is very useful to system administrators since it contains even more detailed information than <code class="command"> xend.log </code>. Here is the same error data for the same kernel domain creation problem:
		</div><pre class="screen">ERROR: Will only load images built for Xen v3.0
ERROR: Actually saw: GUEST_OS=netbsd, GUEST_VER=2.0, XEN_VER=2.0; LOADER=generic, BSD_SYMTAB'
ERROR: Error constructing guest OS
</pre><div class="para">
			When calling customer support, always include a copy of both these log files when contacting the technical support staff.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Important_directory_locations.html"><strong>Prev</strong>25.4.Â Important directory locations</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_serial_console.html"><strong>Next</strong>25.6.Â Troubleshooting with the serial console</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_serial_console.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.6.Â Troubleshooting with the serial console</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_Xen.html" title="ChapterÂ 25.Â Troubleshooting Xen"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs.html" title="25.5.Â Troubleshooting with the logs"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Para_virtualized_guest_console_access.html" title="25.7.Â Para-virtualized guest console access"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" hr
 ef="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Para_virtualized_guest_console_access.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_serial_console">25.6.Â Troubleshooting with the serial console</h2></div></div></div><div class="para">
			The serial console is helpful in troubleshooting difficult problems. If the Virtualization kernel crashes and the hypervisor generates an error, there is no way to track the error on a local host. However, the serial console allows you to capture it on a remote host. You must configure the host to output data to the serial console. Then you must configure the remote host to capture the data. To do this, you must modify these options in the <code class="command">grub.conf</code> file to enable a 38400-bps serial console on <code class="command">com1</code><code class="filename">/dev/ttyS0</code>:
		</div><pre class="screen">title Fedora (2.6.23.14-107.fc8xen0)
		root (hd0,2)
		kernel /xen.gz-2.6.23.14-107.fc8 com1=38400,8n1 
		module /vmlinuz-2.6.23.14-107.fc8xen ro root=LABEL=/rhgb quiet console=xvc console=tty xencons=xvc 	
        	module /initrd-2.6.23.14-107.fc8xen.img
</pre><div class="para">
			The <code class="command">sync_console</code> can help determine a problem that causes hangs with asynchronous hypervisor console output, and the <code class="command">"pnpacpi=off"</code> works around a problem that breaks input on the serial console. The parameters <code class="command">"console=ttyS0"</code> and <code class="command"> "console=tty" </code> means that kernel errors get logged with on both the normal VGA console and on the serial console. Then you can install and set up <code class="command"> ttywatch </code> to capture the data on a remote host connected by a standard null-modem cable. For example, on the remote host you could type:
		</div><pre class="screen">ttywatch --name myhost --port /dev/ttyS0
</pre><div class="para">
			This pipes the output from <code class="command"> /dev/ttyS0 </code> into the file <code class="command"> /var/log/ttywatch/myhost.log </code>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_the_logs.html"><strong>Prev</strong>25.5.Â Troubleshooting with the logs</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Para_virtualized_guest_console_access.html"><strong>Next</strong>25.7.Â Para-virtualized guest console access</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>27.3.Â Manually loading the para-virtualized drivers</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html" title="ChapterÂ 27.Â Troubleshooting the Xen para-virtualized drivers"/><link rel="prev" 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.html" title="27.2.Â Para-virtualized guest fail to load on a Red Hat Enterprise Linux 3 guest operating system"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_
 have_successfully_loaded.html" title="27.4.Â Verifying the para-virtualized drivers have successfully loaded"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" 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.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_have_successfully_loaded.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s
 ect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers">27.3.Â Manually loading the para-virtualized drivers</h2></div></div></div><div class="para">
			If for some reason the para-virtualized drivers failed to load automatically during the boot process you can attempt to load them manually.
		</div><div class="para">
			This will allow you to reconfigure network or storage entities or identify why they failed to load in the first place. The steps below should load the para-virtualized driver modules.
		</div><div class="para">
			First, locate the para-virtualized driver modules on your system.
		</div><pre class="screen"># cd /lib/modules/`uname -r`/
# find . -name 'xen-*.ko' -print
</pre><div class="para">
			Take note of the location and load the modules manually. Substitute {LocationofPV-drivers} with the correct location you noted from the output of the commands above.
		</div><pre class="screen"># insmod \
/lib/modules/'uname -r'/{LocationofPV-drivers}/xen-platform-pci.ko
# insmod /lib/modules/'uname -r'/{LocationofPV-drivers}/xen-balloon.ko
# insmod /lib/modules/'uname -r'/{LocationofPV-drivers}/xen-vnif.ko
# insmod /lib/modules/'uname -r'/{LocationofPV-drivers}/xen-vbd.ko
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" 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.html"><strong>Prev</strong>27.2.Â Para-virtualized guest fail to load on a Re...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_have_successfully_loaded.html"><strong>Next</strong>27.4.Â Verifying the para-virtualized drivers have...</a></li></ul></body></html>

--- NEW FILE 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.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>27.2.Â Para-virtualized guest fail to load on a Red Hat Enterprise Linux 3 guest operating system</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html" title="ChapterÂ 27.Â Troubleshooting the Xen para-virtualized drivers"/><link rel="prev" href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html" title="ChapterÂ 27.Â Troubleshooting the Xen para-virtualized drivers"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers.html" title="27.3.Â Manually loading the para-virtualized drivers"/></head
 ><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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 Ente
 rprise Linux 3 guest operating system</h2></div></div></div><div class="para">
			Red Hat Enterprise Linux 3 is uses processor architecture specific kernel RPMs and because of this the para-virtualized drivers may fail to load if the para-virtualized driver RPM does not match the installed kernel architecture.
		</div><div class="para">
			When the para-virtualized driver modules are inserted, a long list of unresolved modules will be displayed. A shortened excerpt of the error can be seen below. 
<pre class="screen"># insmod xen-platform-pci.o 
Warning: kernel-module version mismatch
xen-platform-pci.o was compiled for kernel version 2.4.21-52.EL
while this kernel is version 2.4.21-50.EL
xen-platform-pci.o: unresolved symbol __ioremap_R9eac042a
xen-platform-pci.o: unresolved symbol flush_signals_R50973be2
xen-platform-pci.o: unresolved symbol pci_read_config_byte_R0e425a9e
xen-platform-pci.o: unresolved symbol __get_free_pages_R9016dd82
[...]
</pre>
			 The solution is to use the correct RPM package for your hardware architecture for the para-virtualized drivers.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html"><strong>Prev</strong>ChapterÂ 27.Â Troubleshooting the Xen para-virtuali...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers.html"><strong>Next</strong>27.3.Â Manually loading the para-virtualized drive...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-The_system_has_limited_throughput_with_para_virtualized_drivers.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>27.5.Â The system has limited throughput with para-virtualized drivers</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html" title="ChapterÂ 27.Â Troubleshooting the Xen para-virtualized drivers"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_have_successfully_loaded.html" title="27.4.Â Verifying the para-virtualized drivers have successfully loaded"/><link rel="next" href="appe-Virtualization_Guide-Xen_system_architecture_.html" title="AppendixÂ A.Â Xen system architecture"/></head><body class="draft "><p id="title"><a c
 lass="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_have_successfully_loaded.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-Virtualization_Guide-Xen_system_architecture_.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></div></div><div class="para">
			If network throughput is still limited even after installing the para-virtualized drivers and you have confirmed they are loaded correctly (refer to <a class="xref" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_have_successfully_loaded.html" title="27.4.Â Verifying the para-virtualized drivers have successfully loaded">SectionÂ 27.4, â€œVerifying the para-virtualized drivers have successfully loadedâ€</a>). To fix this problem, remove the '<code class="command">type=ioemu</code>' part of '<code class="command">vif</code>=' line in your guest's configuration file.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_have_successfully_loaded.html"><strong>Prev</strong>27.4.Â Verifying the para-virtualized drivers have...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="appe-Virtualization_Guide-Xen_system_architecture_.html"><strong>Next</strong>AppendixÂ A.Â Xen system architecture </a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Verifying_the_para_virtualized_drivers_have_successfully_loaded.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>27.4.Â Verifying the para-virtualized drivers have successfully loaded</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers.html" title="ChapterÂ 27.Â Troubleshooting the Xen para-virtualized drivers"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers.html" title="27.3.Â Manually loading the para-virtualized drivers"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-The_system_has_limited_throughput_with_para_virtualized_drivers.html" title="27.5.Â The system has limited thro
 ughput with para-virtualized drivers"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-The_system_has_limited_throughput_with_para_virtualized_drivers.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></div></div><div class="para">
			One of the first tasks you will want to do is to verify that the drivers have actually been loaded into your system.
		</div><div class="para">
			After the para-virtualized drivers have been installed and the guest has been rebooted you can verify that the drivers have loaded. First you should confirm the drivers have logged their loading into <code class="filename">/var/log/messages</code>
<pre class="screen"># grep -E "vif|vbd|xen" /var/log/messages
                    xen_mem: Initialising balloon driver
                    vif vif-0: 2 parsing device/vif/0/mac
                    vbd vbd-768: 19 xlvbd_add at /local/domain/0/backend/vbd/21/76
                    vbd vbd-768: 19 xlvbd_add at /local/domain/0/backend/vbd/21/76
                    xen-vbd: registered block device major 202
</pre>
			 You can also use the <code class="command">lsmod</code> command to list the loaded para-virtualized drivers. It should output a list containing the <code class="systemitem">xen_vnif</code>, <code class="systemitem">xen_vbd</code>, <code class="systemitem">xen_platform_pci</code> and <code class="systemitem">xen_balloon</code> modules. 
<pre class="screen"># lsmod|grep xen
xen_vbd                19168  1 
xen_vnif               28416  0 
xen_balloon            15256  1 xen_vnif
xen_platform_pci       98520  3 xen_vbd,xen_vnif,xen_balloon,[permanent]
</pre>
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-Manually_loading_the_para_virtualized_drivers.html"><strong>Prev</strong>27.3.Â Manually loading the para-virtualized drive...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_the_Xen_para_virtualized_drivers-The_system_has_limited_throughput_with_para_virtualized_drivers.html"><strong>Next</strong>27.5.Â The system has limited throughput with para...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_from_fully_virtualized_guests.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.12.3.Â Serial console output from fully virtualized guests</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html" title="25.12.Â Troubleshooting with serial consoles"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_para_virtualized_guests.html" title="25.12.2.Â Xen serial console output from para-virtualized guests"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_configuration_files.html" title="25.13.Â Guest configuration files"/></head><body class="draft "><p id="title"><a class="left" href="http://www.
 fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_para_virtualized_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_configuration_files.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_from_fully_virtualized_guests">25.12.3.Â Serial console output from fully virtualized guests</h3></div></div></div><div class="para">
				This section covers how to enable serial console output for fully virtualized guests.
			</div><div class="para">
				Fully virtualized guest serial console output can be viewed with the "<code class="command">virsh console</code>" command.
			</div><div class="para">
				Be aware fully virtualized guest serial consoles have some limitations. Present limitations include:
			</div><div class="itemizedlist"><ul><li><div class="para">
						logging output with xend is unavailable.
					</div></li><li><div class="para">
						output data may be dropped or scrambled.
					</div></li></ul></div><div class="para">
				The serial port is called <code class="systemitem">ttyS0</code> on Linux or <code class="systemitem">COM1</code> on Windows.
			</div><div class="para">
				You must configure the virtualized operating system to output information to the virtual serial port.
			</div><div class="para">
				To output kernel information from a fully virtualized Linux guest into the domain modify the <code class="filename">/boot/grub/grub.conf</code> file by inserting the line "<em class="parameter"><code>console=tty0 console=ttys0,115200</code></em>".
			</div><pre class="screen">title Fedora (2.6.23.14-107.fc8)
	root (hd0,0)
	kernel /vmlinuz-2.6.23.14-107.fc8 ro root=/dev/volgroup00/logvol00
	<em class="parameter"><code>console=tty0 console=ttys0,115200</code></em>
	initrd /initrd-2.6.23.14-107.fc8.img
</pre><div class="para">
				Reboot the guest.
			</div><div class="para">
				View the serial console messages using the "<code class="command">virsh console</code>" command. 
				<div class="important"><h2>Note</h2><div class="para">
						Serial console messages from fully virtualized domains are not logged in <code class="filename">/var/log/xen/console</code> as they are for para-virtualized guests.
					</div></div>
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_para_virtualized_guests.html"><strong>Prev</strong>25.12.2.Â Xen serial console output from para-virt...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_Xen-Guest_configuration_files.html"><strong>Next</strong>25.13.Â Guest configuration files</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Xen_serial_console_output_from_para_virtualized_guests.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>25.12.2.Â Xen serial console output from para-virtualized guests</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html" title="25.12.Â Troubleshooting with serial consoles"/><link rel="prev" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html" title="25.12.Â Troubleshooting with serial consoles"/><link rel="next" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_from_fully_virtualized_guests.html" title="25.12.3.Â Serial console output from fully virtualized guests"/></head><body class="draft "><p id="title"><a class="left
 " href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_from_fully_virtualized_guests.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="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</h3></div></div></div><div class="para">
				This section describes how to configure a virtualized serial console for Linux para-virtualized guests.
			</div><div class="para">
				Serial console output from para-virtualized guests can be received using the "<code class="command">virsh console</code>" or in the "<span class="guilabel"><strong>Serial Console</strong></span>" window of <code class="command">virt-manager</code>. Set up the virtual serial console using this procedure:
			</div><div class="procedure"><ol class="1"><li><div class="para">
						Log in to your para-virtualized guest.
					</div></li><li><div class="para">
						Edit <code class="filename">/boot/grub/grub.conf</code> as follows: 
<pre class="screen">Fedora i386 Xen (2.6.23.14-107.fc8xen)
	root (hd0, 0) kernel /boot/vmlinuz-2.6.23.14-107.fc8xen ro root=LABEL=CentOS5_i386 console=xvc0 
	initrd /boot/initrd-2.6.23.14-107.fc8xen.img
</pre>
					</div></li><li><div class="para">
						Reboot the para-virtualized guest.
					</div></li></ol></div><div class="para">
				You should now get kernel messages on the virt-manager "Serial Console" and/or "virsh console".
			</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Xen_serial_console_output_from_para_virtualized_guests-Logging_the_para_virtualized_domain_serial_console_output">Logging the para-virtualized domain serial console output</h5>
					The Xen daemon(<code class="systemitem">xend</code>) can be configured to log the output from serial consoles of para-virtualized guests.
				</div><div class="para">
				To configure <code class="systemitem">xend</code> edit <code class="filename">/etc/sysconfig/xend</code>. Change the entry:
			</div><pre class="programlisting"># Log all guest console output (cf xm console)
#XENCONSOLED_LOG_GUESTS=no
</pre><div class="para">
				to:
			</div><pre class="programlisting"># Log all guest console output (cf xm console)
XENCONSOLED_LOG_GUESTS=yes
</pre><div class="para">
				Reboot the host to activate logging the guest serial console output.
			</div><div class="para">
				Logs from the guest serial consoles are stored in the <code class="filename">/var/log/xen/console</code> file.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Troubleshooting_Xen-Troubleshooting_with_serial_consoles.html"><strong>Prev</strong>25.12.Â Troubleshooting with serial consoles</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Troubleshooting_with_serial_consoles-Serial_console_output_from_fully_virtualized_guests.html"><strong>Next</strong>25.12.3.Â Serial console output from fully virtual...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Virtualized_block_devices-Add_a_virtualized_CD_ROM_or_DVD_device_to_a_guest.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>4.4.Â Add a virtualized CD-ROM or DVD device to a guest</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Virtualized_block_devices.html" title="ChapterÂ 4.Â Virtualized block devices"/><link rel="prev" href="sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html" title="4.3.Â Configuring persistent storage"/><link rel="next" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html" title="ChapterÂ 5.Â Shared storage and virtualization"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="righ
 t" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="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</h2></div></div></div><div class="para">
			To attach an ISO file to a guest while the guest is online use <code class="command">virsh</code> with the <em class="parameter"><code>attach-disk</code></em> parameter. 
<pre class="screen"># virsh attach-disk <em class="replaceable"><code>[domain-id] [source] [target] --driver file --type cdrom --mode readonly</code></em>
</pre>
			 The <em class="replaceable"><code>source</code></em> and <em class="replaceable"><code>target</code></em> parameters are paths for the files and devices, on the host and guest respectively. The <em class="replaceable"><code>source</code></em> parameter can be a path to an ISO file or the device from the <code class="filename">/dev</code> directory.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html"><strong>Prev</strong>4.3.Â Configuring persistent storage</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Shared_storage_and_virtualization.html"><strong>Next</strong>ChapterÂ 5.Â Shared storage and virtualization</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>4.2.Â Adding storage devices to guests</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Virtualized_block_devices.html" title="ChapterÂ 4.Â Virtualized block devices"/><link rel="prev" href="chap-Virtualization_Guide-Virtualized_block_devices.html" title="ChapterÂ 4.Â Virtualized block devices"/><link rel="next" href="sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html" title="4.3.Â Configuring persistent storage"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraprojec
 t.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Virtualized_block_devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests">4.2.Â Adding storage devices to guests</h2></div></div></div><div class="para">
			This section covers adding storage devices to virtualized guest. Additional storage can only be added after guests are created. The supported storage devices and protocol include:
		</div><div class="itemizedlist"><ul><li><div class="para">
					local hard drive partitions,
				</div></li><li><div class="para">
					logical volumes,
				</div></li><li><div class="para">
					Fibre Channel or iSCSI directly connected to the host.
				</div></li><li><div class="para">
					File containers residing in a file system on the host.
				</div></li><li><div class="para">
					<span class="application"><strong>NFS</strong></span> file systems mounted directly by the virtual machine.
				</div></li><li><div class="para">
					iSCSI storage directly accessed by the guest.
				</div></li><li><div class="para">
					Cluster File Systems (<span class="application"><strong>GFS</strong></span>).
				</div></li></ul></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">Adding file based storage to a guest</h5>
				File-based storage or file-based containers are files on the hosts file system which act as virtualized hard drives for virtualized guests. To add a file-based container perform the following steps:
			</div><div class="procedure"><ol class="1"><li><div class="para">
					Create an empty container file or using an existing file container (such as an ISO file).
				</div><ol class="a"><li><div class="para">
							Create a sparse file using the <code class="command">dd</code> command. Sparse files are not recommended due to data integrity and performance issues. Sparse files are created much faster and can used for testing but should not be used in production environments.
						</div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/FileName.img bs=1M seek=4096 count=0
</pre></li><li><div class="para">
							Non-sparse, pre-allocated files are recommended for file based storage containers. Create a non-sparse file, execute:
						</div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/FileName.img bs=1M count=4096
</pre></li></ol><div class="para">
					Both commands create a 400MB file which can be used as additional storage for a virtualized guest.
				</div></li><li><div class="para">
					Dump the configuration for the guest. In this example the guest is called <em class="replaceable"><code>Guest1</code></em> and the file is saved in the users home directory.
				</div><pre class="screen"># virsh dumpxml <em class="replaceable"><code>Guest1</code></em> > ~/<em class="replaceable"><code>Guest1</code></em>.xml
</pre></li><li><div class="para">
					Open the configuration file (<em class="replaceable"><code>Guest1.xml</code></em> in this example) in a text editor. Find the entries starting with "<code class="computeroutput">disk=</code>". This entry resembles:
				</div><pre class="screen">>disk type='file' device='disk'<
        >driver name='tap' type='aio'/<
        >source file='/var/lib/libvirt/images/Guest1.img'/<
        >target dev='xvda'/<
>/disk<
</pre></li><li><div class="para">
					Add the additional storage by modifying the end of <code class="computeroutput">disk=</code> entry. Ensure you specify a device name for the virtual block device which is not used already in the configuration file. The following example entry adds file, named <code class="filename">FileName.img</code>, as a file based storage container:
				</div><pre class="screen">>disk type='file' device='disk'<
        >driver name='tap' type='aio'/<
        >source file='/var/lib/libvirt/images/Guest1.img'/<
        >target dev='xvda'/<
>/disk<
>disk type='file' device='disk'<
        >driver name='tap' type='aio'/<
	>source file='/var/lib/libvirt/images/FileName.img'/<
        >target dev='hda'/<
>/disk<
</pre></li><li><div class="para">
					Restart the guest from the updated configuration file.
				</div><pre class="screen"># virsh create Guest1.xml
</pre></li><li><div class="para">
					The following steps are Linux guest specific. Other operating systems handle new storage devices in different ways. For non Linux systems refer to your guest operating systems documentation.
				</div><div class="para">
					The guest now uses the file <code class="filename">FileName.img</code> as the device called <code class="filename">/dev/hdb</code>. This device requires formatting from the guest. On the guest, partition the device into one primary partition for the entire device then format the device.
				</div><ol class="a"><li><div class="para">
							Press <em class="parameter"><code>n</code></em> for a new partition.
						</div><pre class="screen"># fdisk /dev/hdb
Command (m for help):
</pre></li><li><div class="para">
							Press <em class="parameter"><code>p</code></em> for a primary partition.
						</div><pre class="screen">Command action
   e   extended
   p   primary partition (1-4)
</pre></li><li><div class="para">
							Choose an available partition number. In this example the first partition is chosen by entering <em class="parameter"><code>1</code></em>.
						</div><pre class="screen">Partition number (1-4): <em class="parameter"><code>1</code></em>
</pre></li><li><div class="para">
							Enter the default first cylinder by pressing <em class="parameter"><code>Enter</code></em>.
						</div><pre class="screen">First cylinder (1-400, default 1):
</pre></li><li><div class="para">
							Select the size of the partition. In this example the entire disk is allocated by pressing <em class="parameter"><code>Enter</code></em>.
						</div><pre class="screen">Last cylinder or +size or +sizeM or +sizeK (2-400, default 400):
</pre></li><li><div class="para">
							Set the type of partition by pressing <em class="parameter"><code>t</code></em>.
						</div><pre class="screen">Command (m for help): <em class="parameter"><code>t</code></em>
</pre></li><li><div class="para">
							Choose the partition you created in the previous steps. In this example it's partition <em class="parameter"><code>1</code></em>.
						</div><pre class="screen">Partition number (1-4): <em class="parameter"><code>1</code></em>
</pre></li><li><div class="para">
							Enter <em class="parameter"><code>83</code></em> for a Linux partition.
						</div><pre class="screen">Hex code (type L to list codes): <em class="parameter"><code>83</code></em>
</pre></li><li><div class="para">
							write changes to disk and quit.
						</div><pre class="screen">Command (m for help): <em class="parameter"><code>w</code></em> 
Command (m for help): <em class="parameter"><code>q</code></em>
</pre></li><li><div class="para">
							Format the new partition with the <code class="systemitem">ext3</code> file system.
						</div><pre class="screen"># mke2fs -j /dev/hdb
</pre></li></ol></li><li><div class="para">
					Mount the disk on the guest. 
<pre class="screen"># mount /dev/hdb1 <em class="replaceable"><code>/myfiles</code></em>
</pre>
				</div></li></ol></div><div class="para">
			The guest now has an additional virtualized file-based storage device.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest">Adding hard drives and other block devices to a guest</h5>
				System administrators use additional hard drives for to provide more storage space or to separate system data from user data. This procedure, <a class="xref" href="sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests.html#proc-Virtualization_Guide-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests" title="ProcedureÂ 4.1.Â Adding physical block devices to virtualized guests">ProcedureÂ 4.1, â€œAdding physical block devices to virtualized guestsâ€</a>, describes how to add a hard drive on the host to a virtualized guest.
			</div><div class="para">
			The procedure works for all physical block devices, this includes CD-ROM, DVD and floppy devices.
		</div><div class="procedure" id="proc-Virtualization_Guide-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests"><h6>ProcedureÂ 4.1.Â Adding physical block devices to virtualized guests</h6><ol class="1"><li><div class="para">
					Physically attach the hard disk device to the host. Configure the host if the drive is not accessible by default.
				</div></li><li><div class="para">
					Configure the device with <code class="command">multipath</code> and persistence on the host if required.
				</div></li><li><div class="para">
					Use the <code class="command">virsh attach</code> command. Replace: <em class="replaceable"><code>myguest</code></em> with your guest's name, <em class="parameter"><code>/dev/hdb1</code></em> with the device to add, and <em class="replaceable"><code>hdc</code></em> with the location for the device on the guest. The <em class="replaceable"><code>hdc</code></em> must be an unused device name. Use the <em class="replaceable"><code>hd*</code></em> notation for Windows guests as well, the guest will recognize the device correctly.
				</div><div class="para">
					Append the <em class="parameter"><code>--type hdd</code></em> parameter to the command for CD-ROM or DVD devices.
				</div><div class="para">
					Append the <em class="parameter"><code>--type floppy</code></em> parameter to the command for floppy devices.
				</div><pre class="screen"># virsh attach-disk <em class="replaceable"><code>myguest</code></em> <em class="parameter"><code>/dev/hdb1</code></em> <em class="replaceable"><code>hdc</code></em> --driver tap --mode readonly
</pre></li><li><div class="para">
					The guest now has a new hard disk device called <code class="filename">/dev/hdb</code> on Linux or <code class="filename">D: drive</code>, or similar, on Windows. This device may require formatting.
				</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Virtualized_block_devices.html"><strong>Prev</strong>ChapterÂ 4.Â Virtualized block devices</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html"><strong>Next</strong>4.3.Â Configuring persistent storage</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>4.3.Â Configuring persistent storage</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Virtualized_block_devices.html" title="ChapterÂ 4.Â Virtualized block devices"/><link rel="prev" href="sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests.html" title="4.2.Â Adding storage devices to guests"/><link rel="next" href="sect-Virtualization_Guide-Virtualized_block_devices-Add_a_virtualized_CD_ROM_or_DVD_device_to_a_guest.html" title="4.4.Â Add a virtualized CD-ROM or DVD device to a guest"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" al
 t="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Virtualized_block_devices-Add_a_virtualized_CD_ROM_or_DVD_device_to_a_guest.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage">4.3.Â Configuring persistent storage</h2></div></div></div><div class="para">
			This section is for systems with external or networked storage; that is, Fibre Channel or iSCSI based storage devices. It is recommended that those systems have persistent device names configured for your hosts. This assists live migration as well as providing consistent device names and storage for multiple virtualized systems.
		</div><div class="para">
			Universally Unique Identifiers(UUIDs) are a standardized method for identifying computers and devices in distributed computing environments. This sections uses UUIDs to identify iSCSI or Fibre Channel LUNs. UUIDs persist after restarts, disconnection and device swaps. The UUID is similar to a label on the device.
		</div><div class="para">
			Systems which are not running <code class="command">multipath</code> must use <a class="xref" href="sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html#form-Virtualization_Guide-Configuring_persistent_storage_in_Linux_5-Single_path_configuration" title="Single path configuration">Single path configuration</a>. Systems running <code class="command">multipath</code> can use <a class="xref" href="sect-Virtualization_Guide-Virtualized_block_devices-Configuring_persistent_storage.html#form-Virtualization_Guide-Configuring_persistent_storage_in_Linux_5-Multiple_path_configuration" title="Multiple path configuration">Multiple path configuration</a>.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Configuring_persistent_storage_in_Linux_5-Single_path_configuration">Single path configuration</h5>
				This procedure implements <a class="firstterm" href="go01.html#glos-Virtualization_Guide-LUN"><em class="firstterm">LUN</em></a> device persistence using <code class="command">udev</code>. Only use this procedure for hosts which are not using <code class="command">multipath</code>.
			</div><div class="procedure"><ol class="1"><li><div class="para">
					Edit the <code class="filename">/etc/scsi_id.config</code> file.
				</div><ol class="a"><li><div class="para">
							Ensure the <code class="command">options=-b</code> is line commented out. 
<pre class="screen"># options=-b
</pre>
						</div></li><li><div class="para">
							Add the following line:
						</div><pre class="screen">options=-g
</pre><div class="para">
							This option configures <code class="command">udev</code> to assume all attached SCSI devices return a UUID.
						</div></li></ol></li><li><div class="para">
					To display the UUID for a given device run the <code class="command">scsi_id -g -s /block/sd*</code> command. For example:
				</div><pre class="screen"># scsi_id -g -s /block/sd*
3600a0b800013275100000015427b625e
</pre><div class="para">
					The output may vary from the example above. The output displays the UUID of the device <code class="systemitem">/dev/sdc</code>.
				</div></li><li><div class="para">
					Verify the UUID output by the <code class="command">scsi_id -g -s /block/sd*</code> command is identical from computer which accesses the device.
				</div></li><li><div class="para">
					Create a rule to name the device. Create a file named <code class="filename">20-names.rules</code> in the <code class="filename">/etc/udev/rules.d</code> directory. Add new rules to this file. All rules are added to the same file using the same format. Rules follow this format:
				</div><pre class="screen">KERNEL="sd*", BUS="scsi", PROGRAM="/sbin/scsi_id -g -s", RESULT=<em class="replaceable"><code>UUID</code></em>, NAME=<em class="replaceable"><code>devicename</code></em>
</pre><div class="para">
					Replace <em class="replaceable"><code>UUID</code></em> and <em class="replaceable"><code>devicename</code></em> with the UUID retrieved above, and a name for the device. This is a rule for the example above:
				</div><pre class="screen">KERNEL="sd*", BUS="scsi", PROGRAM="/sbin/scsi_id -g -s", RESULT="3600a0b800013275100000015427b625e", NAME="rack4row16"
</pre><div class="para">
					The <code class="command">udev</code> daemon now searches all devices named <code class="filename">/dev/sd*</code> for the UUID in the rule. Once a matching device is connected to the system the device is assigned the name from the rule. In the a device with a UUID of 3600a0b800013275100000015427b625e would appear as <code class="filename">/dev/rack4row16</code>.
				</div></li><li><div class="para">
					Append this line to <code class="filename">/etc/rc.local</code>:
				</div><pre class="screen">/sbin/start_udev
</pre></li><li><div class="para">
					Copy the changes in the <code class="filename">/etc/scsi_id.config</code>, <code class="filename">/etc/udev/rules.d/20-names.rules</code>, and <code class="filename">/etc/rc.local</code> files to all relevant hosts.
				</div><pre class="screen">/sbin/start_udev
</pre></li></ol></div><div class="para">
			Networked storage devices with configured rules now have persistent names on all hosts where the files were updated This means you can migrate guests between hosts using the shared storage and the guests can access the storage devices in their configuration files.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Configuring_persistent_storage_in_Linux_5-Multiple_path_configuration">Multiple path configuration</h5>
				The <code class="command">multipath</code> package is used for systems with more than one physical path from the computer to storage devices. <code class="command">multipath</code> provides fault tolerance, fail-over and enhanced performance for network storage devices attached to Linux systems.
			</div><div class="para">
			Implementing LUN persistence in a <code class="command">multipath</code> environment requires defined alias names for your multipath devices. Each storage device has a UUID which acts as a key for the aliased names. Identify a device's UUID using the <code class="command">scsi_id</code> command.
		</div><pre class="screen"># scsi_id -g -s /block/sdc
</pre><div class="para">
			The multipath devices will be created in the <code class="filename">/dev/mpath</code> directory. In the example below 4 devices are defined in <code class="filename">/etc/multipath.conf</code>:
		</div><pre class="screen">multipaths { 
	multipath { 
	wwid		3600805f30015987000000000768a0019 
	alias		oramp1 
	} 
	multipath { 
	wwid		3600805f30015987000000000d643001a 
	alias		oramp2 
	} 
	mulitpath { 
	wwid		3600805f3001598700000000086fc001b 
	alias		oramp3 
	} 
	mulitpath { 
	wwid		3600805f300159870000000000984001c 
	alias		oramp4 
	} 
}
</pre><div class="para">
			This configuration will create 4 LUNs named <code class="filename">/dev/mpath/oramp1</code>, <code class="filename">/dev/mpath/oramp2</code>, <code class="filename">/dev/mpath/oramp3</code> and <code class="filename">/dev/mpath/oramp4</code>. Once entered, the mapping of the devices' WWID to their new names are now persistent after rebooting.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Prev</strong>4.2.Â Adding storage devices to guests</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Virtualized_block_devices-Add_a_virtualized_CD_ROM_or_DVD_device_to_a_guest.html"><strong>Next</strong>4.4.Â Add a virtualized CD-ROM or DVD device to a ...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>2.2.Â Creating guests with virt-manager</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html" title="ChapterÂ 2.Â Virtualized guest installation overview"/><link rel="prev" href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html" title="ChapterÂ 2.Â Virtualized guest installation overview"/><link rel="next" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html" title="2.3.Â Installing guests with PXE"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Pro
 duct Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager">2.2.Â Creating guests with virt-manager</h2></div></div></div><div class="para">
			<code class="command">virt-manager</code>, also known as Virtual Machine Manager, is a graphical tool for creating and managing virtualized guests.
		</div><div class="procedure" id="proc-Virtualization_Guide-Creating_guests_with_virt_manager-Creating_a_virtualized_guest_with_virt_manager"><h6>ProcedureÂ 2.1.Â Creating a virtualized guest with <span class="application"><strong>virt-manager</strong></span></h6><ol class="1"><li><div class="para">
					To start <span class="application"><strong>virt-manager</strong></span> run the following command as root:
				</div><pre class="screen"># virt-manager &
</pre><div class="para">
					The <code class="command">virt-manager</code> command opens a graphical user interface window. Various functions are not available to users without root privileges or <code class="command">sudo</code> configured, including the <span class="guibutton"><strong>New</strong></span> button and you will not be able to create a new virtualized guest.
				</div></li><li><div class="para">
					Open the <span class="guilabel"><strong>File -> Open Connection</strong></span>. The dialog box below appears. . Select a hypervisor and click the <span class="guibutton"><strong>Connect</strong></span> button:
				</div><div class="mediaobject"><img src="images/step1-1.png"/></div></li><li><div class="para">
					The <span class="application"><strong>virt-manager</strong></span> window allows you to create a new virtual machine. Click the <span class="guibutton"><strong>New</strong></span> button to create a new guest. This opens the wizard shown in the screenshot.
				</div><div class="mediaobject"><img src="images/vmm_new.png"/></div></li><li><div class="para">
					The <span class="guilabel"><strong>Create a new virtual system</strong></span> window provides a summary of the information you must provide in order to create a virtual machine:
				</div><div class="mediaobject"><img src="images/create_new.png"/></div><div class="para">
					Review the information for your installation and click the <span class="guibutton"><strong>Forward</strong></span> button.
				</div></li><li><div class="para">
					The <span class="guilabel"><strong>Choosing a virtualization method</strong></span> window appears. Choose between <span class="guilabel"><strong>Para-virtualized</strong></span> or <span class="guilabel"><strong>Fully virtualized</strong></span>.
				</div><div class="para">
					Full virtualization requires a system with <span class="trademark">Intel</span>Â® VT or AMD-V processor. If the virtualization extensions are not present the <span class="guilabel"><strong>fully virtualized</strong></span> radio button or the <span class="guilabel"><strong>Enable kernel/hardware acceleration</strong></span> will not be selectable. The <span class="guilabel"><strong>Para-virtualized</strong></span> option will be grayed out if <code class="command">kernel-xen</code> is not the kernel running presently.
				</div><div class="para">
					If you connected to a KVM hypervisor only full virtualization is available.
				</div><div class="mediaobject"><img src="images/virt_method.png"/></div><div class="para">
					Choose the virtualization type and click the <span class="guibutton"><strong>Next</strong></span> button.
				</div></li><li><div class="para">
					The <span class="guilabel"><strong>Locating installation media</strong></span> prompt asks for the installation media for the type of installation you selected. This screen is dependent on what was selected in the previous step.
				</div><ol class="a"><li><div class="para">
							The para-virtualized installation requires an installation tree accessible using one of the following network protocols: <code class="systemitem">HTTP</code>, <code class="systemitem">FTP</code> or <code class="systemitem">NFS</code>. The installation media URL must contain a Fedora installation tree. This tree is hosted using <code class="systemitem">NFS</code>, <code class="systemitem">FTP</code> or <code class="systemitem">HTTP</code>. The network services and files can be hosted using network services on the host or another mirror.
						</div><div class="para">
							Using a CD-ROM or DVD image (tagged as an <code class="filename">.iso</code> file), mount the CD-ROM image and host the mounted files with one of the mentioned protocols.
						</div><div class="para">
							Alternatively, copy the installation tree from a Fedora mirror.
						</div><div class="mediaobject"><img src="images/location_media_install.png"/></div></li><li><div class="para">
							A fully virtualized guest installation require bootable installation DVDs, CD-ROMs or images of bootable installation DVDs or CD-ROMs (with the .iso or .img file type) locally. Windows installations use DVD, CD-ROM or .iso file. Many Linux and UNIX-like operating systems use an .iso file to install a base system before finishing the installation with a network based installation tree.
						</div><div class="mediaobject"><img src="images/fullvirt_install_media.png"/></div></li></ol><div class="para">
					After selecting the appropriate installation media, click the <span class="guibutton"><strong>Forward</strong></span> button.
				</div></li><li><div class="para">
					The <span class="guilabel"><strong>Assigning storage space</strong></span> window displays. Choose a disk partition, LUN or create a file based image for the guest storage.
				</div><div class="para">
					The convention for file based images in Fedora is that all file based guest images are in the <code class="filename">/var/lib/xen/images/</code> directory. Other directory locations for file based images are prohibited by SELinux. If you run SELinux in enforcing mode, refer to <a class="xref" href="chap-Virtualization_Guide-Security_for_virtualization.html#sect-Virtualization_Guide-Security_for_virtualization-SELinux_and_virtualization" title="7.1.Â SELinux and virtualization">SectionÂ 7.1, â€œSELinux and virtualizationâ€</a> for more information on installing guests.
				</div><div class="para">
					Your guest storage image should be larger than the size of the installation, any additional packages and applications, and the size of the guests swap file. The installation process will choose the size of the guest's swap file based on size of the RAM allocated to the guest.
				</div><div class="para">
					Allocate extra space if the guest needs additional space for applications or other data. For example, web servers require additional space for log files.
				</div><div class="mediaobject"><img src="images/assign_storage.png"/></div><div class="para">
					Choose the appropriate size for the guest on your selected storage type and click the <span class="guibutton"><strong>Forward</strong></span> button.
				</div><div class="note"><h2>Note</h2><div class="para">
						It is recommend that you use the default directory for virtual machine images, <code class="filename">/var/lib/xen/images/</code>. If you are using a different location (such as <code class="filename">/xen/images/</code> in this example) make sure it is added to your SELinux policy and relabeled before you continue with the installation (later in the document you will find information on how to modify your SELinux policy).
					</div></div></li><li><div class="para">
					The Allocate memory and CPU window displays. Choose appropriate values for the virtualized CPUs and RAM allocation. These values affect the host's and guest's performance.
				</div><div class="para">
					Guests require sufficient physical memory (RAM) to run efficiently and effectively. Choose a memory value which suits your guest operating system and application requirements. Most operating system require at least 512MB of RAM to work responsively. Remember, guests use physical RAM. Running too many guests or leaving insufficient memory for the host system results in significant usage of virtual memory. Virtual memory is significantly slower causing degraded system performance and responsiveness. Ensure to allocate sufficient memory for all guests and the host to operate effectively.
				</div><div class="para">
					Assign sufficient virtual CPUs for the virtualized guest. If the guest runs a multithreaded application assign the number of virtualized CPUs it requires to run most efficiently. Do not assign more virtual CPUs than there are physical processors (or hyper-threads) available on the host system. It is possible to over allocate virtual processors, however, over allocating has a significant, negative affect on guest and host performance due to processor context switching overheads.
				</div><div class="mediaobject"><img src="images/allocate_mem_cpu.png"/></div></li><li><div class="para">
					The ready to begin installation window presents a summary of all configuration information you entered. Review the information presented and use the <span class="guibutton"><strong>Back</strong></span> button to make changes, if necessary. Once you are satisfied click the <span class="guibutton"><strong>Finish</strong></span> button and to start the installation process.
				</div><div class="mediaobject"><img src="images/ready_to_install.png"/></div><div class="para">
					A VNC window opens showing the start of the guest operating system installation process.
				</div></li></ol></div><div class="para">
			This concludes the general process for creating guests with <code class="command">virt-manager</code>. <a class="xref" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html" title="ChapterÂ 3.Â Guest operating system installation procedures">ChapterÂ 3, <i>Guest operating system installation procedures</i></a> contains step-by-step instructions to installing a variety of common operating systems.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html"><strong>Prev</strong>ChapterÂ 2.Â Virtualized guest installation overview</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html"><strong>Next</strong>2.3.Â Installing guests with PXE</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>2.3.Â Installing guests with PXE</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Virtualized_guest_installation_overview.html" title="ChapterÂ 2.Â Virtualized guest installation overview"/><link rel="prev" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager.html" title="2.2.Â Creating guests with virt-manager"/><link rel="next" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html" title="ChapterÂ 3.Â Guest operating system installation procedures"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/ima
 ge_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Installing_guests_with_PXE">2.3.Â Installing guests with PXE</h2></div></div></div><div class="para">
			This section covers the steps required to install guests with PXE. PXE guest installation requires a shared network device, also known as a network bridge. The procedures below cover creating a bridge and the steps required to utilize it the bridge for a PXE installation.
		</div><div class="procedure"><ol class="1"><li id="step-Virtualization_Guide-Installing_guests_with_PXE-Create_a_new_bridge"><p class="title"><b>Create a new bridge</b></p><ol class="a"><li><div class="para">
							Create a new network script file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. This example creates a file named <code class="filename">ifcfg-installation</code> which makes a bridge named <em class="parameter"><code>installation</code></em>
						</div><pre class="screen"># cd /etc/sysconfig/network-scripts/
# vim ifcfg-installation
DEVICE=installation
TYPE=Bridge
BOOTPROTO=dhcp
ONBOOT=yes
</pre><div class="warning"><h2>Warning</h2><div class="para">
								The line, <em class="parameter"><code>TYPE=Bridge</code></em>, is case-sensitive. It must have uppercase 'B' and lower case 'ridge'.
							</div></div></li><li><pre class="screen">Start the new bridge.
# ifup installation
</pre></li><li><div class="para">
							There are no interfaces added to the new bridge yet. Use the <code class="command">brctl show</code> command to view details about network bridges on the system.
						</div><pre class="screen"># brctl show
bridge name     bridge id               STP enabled     interfaces
installation    8000.000000000000       no
virbr0          8000.000000000000       yes
</pre><div class="para">
							The <code class="command">virbr0</code> bridge is the default bridge used by <code class="command">libvirt</code> for Network Address Translation (NAT) on the default Ethernet device.
						</div></li></ol></li><li id="step-Virtualization_Guide-Installing_guests_with_PXE-Add_an_interface_to_the_new_bridge"><p class="title"><b>Add an interface to the new bridge</b></p><div class="para">
					Edit the configuration file for the interface. Add the <code class="command">BRIDGE</code> parameter to the configuration file with the name of the bridge created in the previous steps.
				</div><pre class="screen"># Intel Corporation Gigabit Network Connection
DEVICE=eth1
BRIDGE=installation
BOOTPROTO=dhcp
HWADDR=00:13:20:F7:6E:8E
ONBOOT=yes
</pre><div class="para">
					After editing the configuration file, restart networking or reboot.
				</div><pre class="screen"># service network restart
</pre><div class="para">
					Verify the interface is attached with the <code class="command">brctl show</code> command:
				</div><pre class="screen"># brctl show
bridge name     bridge id               STP enabled     interfaces
installation    8000.001320f76e8e       no              eth1
virbr0          8000.000000000000       yes
</pre></li><li id="step-Virtualization_Guide-Installing_guests_with_PXE-Security_configuration"><p class="title"><b>Security configuration</b></p><div class="para">
					Configure <code class="command">iptables</code> to allow all traffic to be forwarded across the bridge.
				</div><pre class="screen"># iptables -I FORWARD -m physdev --physdev-is-bridged -j ACCEPT
# service iptables save
# service iptables restart
</pre><div class="note"><h2>Disable iptables on bridges</h2><div class="para">
						Alternatively, prevent bridged traffic from being processed by <code class="command">iptables</code> rules. In <code class="filename">/etc/sysctl.conf</code> append the following lines:
					</div><pre class="screen">net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
</pre><div class="para">
						Reload the kernel parameters configured with <code class="command">sysctl</code>
					</div></div><pre class="screen"># sysctl -p /etc/sysctl.conf
</pre></li><li id="step-Virtualization_Guide-Installing_guests_with_PXE-Restart_libvirt_before_the_installation"><p class="title"><b>Restart libvirt before the installation</b></p><div class="para">
					Restart the <code class="command">libvirt</code> daemon.
				</div><pre class="screen"># service libvirtd reload
</pre></li></ol></div><div class="para">
			The bridge is configured, you can now begin an installation.
		</div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installing_guests_with_PXE-PXE_installation_with_virt_install">PXE installation with virt-install</h5>
				For <code class="command">virt-install</code> append the <code class="command">--network=bridge:BRIDGENAME</code> installation parameter where installation is the name of your bridge. For PXE installations use the <em class="parameter"><code>--pxe</code></em> parameter.
			</div><div class="example" id="exam-Virtualization_Guide-Installing_guests_with_PXE-PXE_installation_with_virt_install"><div class="example-contents"><pre class="screen"># virt-install --accelerate --hvm --connect qemu:///system \
    --network=bridge:installation --pxe\
    --name EL10 --ram=756 \
    --vcpus=4
    --os-type=linux --os-variant=rhel5
    --file=/var/lib/libvirt/images/EL10.img \
</pre></div><h6>ExampleÂ 2.3.Â PXE installation with virt-install</h6></div><br class="example-break"/><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Installing_guests_with_PXE-PXE_installation_with_virt_manager">PXE installation with virt-manager</h5>
				The steps below are the steps that vary from the standard virt-manager installation procedures. For the standard installations refer to <a class="xref" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html" title="ChapterÂ 3.Â Guest operating system installation procedures">ChapterÂ 3, <i>Guest operating system installation procedures</i></a>.
			</div><div class="procedure"><ol class="1"><li id="step-Virtualization_Guide-Installing_guests_with_PXE-Select_PXE"><p class="title"><b>Select PXE</b></p><div class="para">
					Select PXE as the installation method.
				</div><div class="mediaobject"><img src="images/bridgePXE.png"/></div></li><li id="step-Virtualization_Guide-Installing_guests_with_PXE-Select_the_bridge"><p class="title"><b>Select the bridge</b></p><div class="para">
					Select <span class="guilabel"><strong>Shared physical device</strong></span> and select the bridge created in the previous procedure.
				</div><div class="mediaobject"><img src="images/bridgeshare.png"/></div></li><li id="step-Virtualization_Guide-Installing_guests_with_PXE-Start_the_installation"><p class="title"><b>Start the installation</b></p><div class="para">
					The installation is ready to start.
				</div><div class="mediaobject"><img src="images/bridgefinish.png"/></div></li></ol></div><div class="para">
			A DHCP request is sent and if a valid PXE server is found the guest installation processes will start.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Guide-Virtualized_guest_installation_overview-Creating_guests_with_virt_manager.html"><strong>Prev</strong>2.2.Â Creating guests with virt-manager</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Guest_operating_system_installation_procedures.html"><strong>Next</strong>ChapterÂ 3.Â Guest operating system installation pr...</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Xen_live_migration-Configuring_guest_live_migration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>14.2.Â Configuring guest live migration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Xen_live_migration.html" title="ChapterÂ 14.Â Xen live migration"/><link rel="prev" href="chap-Virtualization_Guide-Xen_live_migration.html" title="ChapterÂ 14.Â Xen live migration"/><link rel="next" href="chap-Virtualization_Guide-KVM_live_migration.html" title="ChapterÂ 15.Â KVM live migration"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Docume
 ntation Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Xen_live_migration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-KVM_live_migration.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Xen_live_migration-Configuring_guest_live_migration">14.2.Â Configuring guest live migration</h2></div></div></div><div class="para">
			This section covers offline migration of Xen guests to other servers running Linux. Further, migration is performed in an offline method (using the <code class="command">xm migrate</code> command). Live migration can be done from the same command. However there are some additional modifications that you must do to the <code class="command">xend-config </code> configuration file. This example identifies the entries that you must modify to ensure a successful migration:
		</div><div class="variablelist"><dl><dt><span class="term"><em class="parameter"><code>(xend-relocation-server yes)</code></em></span></dt><dd><div class="para">
						The default for this parameter is 'no', which keeps the relocation/migration server deactivated (unless on a trusted network) and the domain virtual memory is exchanged in raw form without encryption.
					</div></dd><dt><span class="term"><em class="parameter"><code>(xend-relocation-port 8002)</code></em></span></dt><dd><div class="para">
						This parameter sets the port that <code class="command">xend </code> uses for migration. Use this value unless your network environment requires a custom value. Remove the comment symbol to enable it.
					</div></dd><dt><span class="term"><em class="parameter"><code>(xend-relocation-address )</code></em></span></dt><dd><div class="para">
						This parameter is the address that listens for relocation socket connections, after you enable the <code class="command">xend-relocation-server </code>. The Xen hypervisor only listens for migration network traffic on the specified interface.
					</div></dd><dt><span class="term"><em class="parameter"><code>(xend-relocation-hosts-allow )</code></em></span></dt><dd><div class="para">
						This parameter controls the host that communicates with the relocation port. If the value is empty, then all incoming connections are allowed. You must change this to a space-separated sequences of regular expressions (for example, <code class="command">xend-relocation-hosts-allow- '^localhost\\.localdomain$' </code>). A host with a fully qualified domain name or IP address that matches these expressions are accepted.
					</div></dd></dl></div><div class="para">
			After you configure these parameters, you must reboot the host for the Xen hypervisor load the new parameters.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Xen_live_migration.html"><strong>Prev</strong>ChapterÂ 14.Â Xen live migration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-KVM_live_migration.html"><strong>Next</strong>ChapterÂ 15.Â KVM live migration</a></li></ul></body></html>

--- NEW FILE sect-Virtualization_Guide-Xen_networking-Laptop_network_configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>9.2.Â Laptop network configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css"/><meta name="generator" content="publican"/><meta name="package" content="Fedora-Virtualization_Guide-12-en-US-1-2"/><link rel="home" href="index.html" title="Virtualization Guide"/><link rel="up" href="chap-Virtualization_Guide-Xen_networking.html" title="ChapterÂ 9.Â Xen networking"/><link rel="prev" href="chap-Virtualization_Guide-Xen_networking.html" title="ChapterÂ 9.Â Xen networking"/><link rel="next" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html" title="ChapterÂ 10.Â Xen Para-virtualized Drivers"/></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"/></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documenta
 tion Site"/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Xen_networking.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-Virtualization_Guide-Xen_networking-Laptop_network_configuration">9.2.Â Laptop network configuration</h2></div></div></div><div class="important"><h2>Manually adding network bridges</h2><div class="para">
				This section describes manually adding network bridges. This procedure is not required or recommended newer versions of Fedora. For newer versions use "<span class="guilabel"><strong>Virtual Network</strong></span>" adapters when creating guests in <code class="command">virt-manager</code>. NetworkManager works with virtual network devices by default in newer versions of Fedora.
			</div><div class="para">
				An example of a virsh XML configuration file virtual network device:
			</div><pre class="screen"><interface type='network'>
	<mac address='AA:AA:AA:AA:AA:AA'/>
	<source network='default'/>
	<target dev='vnet0'/>
	<model type='virtio'/>
</interface>
</pre><div class="para">
				In <code class="command">xm</code> configuration files, virtual network devices are labeled "<code class="systemitem">vif</code>".
			</div></div><div class="para">
			The challenge in running the Xen hypervisor on a laptop is that most laptops will connected to the network via wireless network or wired connections. Often these connections are switched multiple times a day. In such an environment, the system assumes it has access to the same interface all the time and it also can perform <code class="command">ifup</code> or <code class="command">ifdown</code> calls to the network interface it is using. In addition wireless network cards do not work well in a virtualization environment due to Xen's (default) bridged network usage.
		</div><div class="para">
			This setup will also enable you to run Xen in offline mode when you have no active network connection on your laptop. The easiest solution to run Xen on a laptop is to follow the procedure outlined below:
		</div><div class="itemizedlist"><ul><li><div class="para">
					You will be configuring a 'dummy' network interface which will be used by Xen. In this example the interface is called <code class="command">dummy0</code>. This will also allow you to use a hidden IP address space for your guests.
				</div></li><li><div class="para">
					You will need to use static IP address as DHCP will not listen on the dummy interface for DHCP requests. You can compile your own version of DHCP to listen on dummy interfaces, however you may want to look into using dnsmasq for DNS, DHCP and tftpboot services in a Xen environment. Setup and configuration are explained further down in this section/chapter.
				</div></li><li><div class="para">
					You can also configure NAT and IP masquerading in order to enable access to the network from your guests.
				</div></li></ul></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Linux_5.0_Laptop_network_configuration-Configuring_a_dummy_network_interface">Configuring a dummy network interface</h5>
				Perform the following configuration steps on your host:
			</div><div class="procedure"><ol class="1"><li><div class="para">
					create a dummy0 network interface and assign it a static IP address. In our example I selected 10.1.1.1 to avoid routing problems in our environment. To enable dummy device support add the following lines to <code class="filename">/etc/modprobe.conf</code>
				</div><pre class="screen">alias dummy0 dummy
options dummy numdummies=1
</pre></li><li><div class="para">
					To configure networking for dummy0 edit/create <code class="filename">/etc/sysconfig/network-scripts/ifcfg-dummy0</code>:
				</div><pre class="screen">DEVICE=dummy0
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
IPV6INIT=no
PEERDNS=yes
TYPE=Ethernet
NETMASK=255.255.255.0
IPADDR=10.1.1.1
ARP=yes
</pre></li><li><div class="para">
					Bind <code class="systemitem">xenbr0</code> to <code class="systemitem">dummy0</code>, so you can use networking even when not connected to a physical network. Edit <code class="filename">/etc/xen/xend-config.sxp</code> to include the <code class="computeroutput">netdev=dummy0</code> entry:
				</div><pre class="screen">(network-script 'network-bridge bridge=xenbr0 netdev=dummy0')
</pre></li><li><div class="para">
					Open <code class="filename">/etc/sysconfig/network</code> in the guest and modify the default gateway to point to <code class="systemitem">dummy0</code>. If you are using a static IP, set the guest's IP address to exist on the same subnet as <code class="systemitem">dummy0</code>.
				</div><pre class="screen">NETWORKING=yes
HOSTNAME=localhost.localdomain
GATEWAY=10.1.1.1
IPADDR=10.1.1.10
NETMASK=255.255.255.0
</pre></li><li><div class="para">
					Setting up NAT in the host will allow the guests access Internet, including with wireless, solving the Xen and wireless card issues. The script below will enable NAT based on the interface currently used for your network connection.
				</div></li></ol></div><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Linux_5.0_Laptop_network_configuration-Configuring_NAT_for_virtualized_guests">Configuring NAT for virtualized guests</h5>
				Network address translation (NAT) allows multiple network address to connect through a single IP address by intercepting packets and passing them to the private IP addresses. You can copy the following script to <code class="filename">/etc/init.d/xenLaptopNAT</code> and create a soft link to <code class="filename">/etc/rc3.d/S99xenLaptopNAT</code>. this automatically starts NAT at boot time. 
				<div class="note"><h2>NetworkManager and wireless NAT</h2><div class="para">
						The script below may not work well with wireless network or <span class="application"><strong>NetworkManager</strong></span> due to start up delays. In this case run the script manually once the machine has booted.
					</div></div>
			</div><pre class="screen">#!/bin/bash
PATH=/usr/bin:/sbin:/bin:/usr/sbin
export PATH
GATEWAYDEV=`ip route | grep default | awk {'print $5'}`
iptables -F
case "$1" in
start)
	if test -z "$GATEWAYDEV"; then
	echo "No gateway device found"
    else
	echo  "Masquerading using $GATEWAYDEV"
	/sbin/iptables -t nat -A POSTROUTING -o $GATEWAYDEV -j MASQUERADE
fi
	echo "Enabling IP forwarding"
	echo 1 > /proc/sys/net/ipv4/ip_forward
	echo "IP forwarding set to `cat /proc/sys/net/ipv4/ip_forward`"
	echo "done."
	;;
*)
echo "Usage: $0 {start|restart|status}"
;;
esac
</pre><div class="formalpara"><h5 class="formalpara" id="form-Virtualization_Guide-Linux_5.0_Laptop_network_configuration-Configuring_dnsmasq_for_the_DNS_DHCP_and_tftpboot_services">Configuring dnsmasq for the DNS, DHCP and tftpboot services</h5>
				One of the challenges in running virtualization on a laptop (or any other computer which is not connected by a single or stable network connection) is the change in network interfaces and availability. Using a dummy network interface helps to build a more stable environment but it also brings up new challenges in providing DHCP, DNS and tftpboot services to your virtual machines/guests. The default DHCP daemon shipped with Fedora will not listen on dummy interfaces, your DNS forwarded information may change as you connect to different networks and VPNs.
			</div><div class="para">
			One solution to the above challenges is to use dnsmasq which can provide all of the above service in a single package and will also allow you to control its service only being available to requests from your dummy interface. Below is a short write up on how to configure <code class="command">dnsmasq</code> on a laptop running virtualization:
		</div><div class="itemizedlist"><ul><li><div class="para">
					Get the latest version of dnsmasq from <a href="http://www.thekelleys.org.uk/dnsmasq/">here</a>.
				</div></li><li><div class="para">
					Document for dnsmasq can be found <a href="http://www.thekelleys.org.uk/dnsmasq/doc.html">here</a>.
				</div></li><li><div class="para">
					Copy the other files referenced below from <a href="http://et.redhat.com/~jmh/tools/xen/">http://et.redhat.com/~jmh/tools/xen/</a> and grab the file <code class="filename">dnsmasq.tgz</code>. The tar archive includes the following files:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="filename">nm-dnsmasq</code> can be used as a dispatcher script for NetworkManager. It will be run every time NetworkManager detects a change in connectivity and force a restart/reload of dnsmasq. It should be copied to <code class="filename">/etc/NetworkManager/dispatcher.d/nm-dnsmasq</code>
						</div></li><li><div class="para">
							<code class="filename">xenDNSmasq</code> can be used as the main start up or shut down script for <code class="filename">/etc/init.d/xenDNSmasq</code>
						</div></li><li><div class="para">
							<code class="filename">dnsmasq.conf</code> is a sample configuration file for <code class="filename">/etc/dnsmasq.conf</code>
						</div></li><li><div class="para">
							<code class="filename">dnsmasq</code> is the binary image for <code class="filename">/usr/local/sbin/dnsmasq</code>
						</div></li></ul></div></li><li><div class="para">
					Once you have unpacked and build dnsmasq (the default installation will be the binary into <code class="filename">/usr/local/sbin/dnsmasq</code>) you need to edit your dnsmasq configuration file. The file is located in <code class="filename">/etc/dnsmaqs.conf</code>
				</div></li><li><div class="para">
					Edit the configuration to suit your local needs and requirements. The following parameters are likely the ones you want to modify:
				</div><div class="itemizedlist"><ul><li><div class="para">
							The <code class="computeroutput">interface</code> parameter allows <code class="systemitem">dnsmasq</code> to listen for <code class="systemitem">DHCP</code> and <code class="systemitem">DNS</code> requests only on specified interfaces. This could be dummy interfaces but not your public interfaces as well as the local loopback interface. Add another <code class="computeroutput">interface</code> line for more than one interface. <code class="computeroutput">interface=dummy0</code> is an example which listens on the <code class="systemitem">dummy0</code> interface.
						</div></li><li><div class="para">
							<code class="computeroutput">dhcp-range</code> to enable the integrated <code class="systemitem">DHCP</code> server, you need to supply the range of addresses available for lease and optionally a lease time. If you have more than one network, you will need to repeat this for each network on which you want to supply <code class="systemitem">DHCP</code> service. An example would be (for network 10.1.1.* and a lease time of 12hrs): <code class="computeroutput">dhcp-range=10.1.1.10,10.1.1.50,255.255.255.0,12h</code>
						</div></li><li><div class="para">
							<code class="computeroutput">dhcp-option</code> to override the default route supplied by dnsmasq, which assumes the router is the same machine as the one running dnsmasq. An example would be <code class="computeroutput">dhcp-option=3,10.1.1.1</code>
						</div></li></ul></div></li><li><div class="para">
					After configuring dnsmasq you can copy the script below as <code class="filename">xenDNSmasq</code> to <code class="filename">/etc/init.d</code>
				</div></li><li><div class="para">
					If you want to automatically start dnsmasq during system boot you should register it using chkconfig(8):
				</div><pre class="screen">chkconfig --add xenDNSmasq
</pre><div class="para">
					Enable it for automatic start up:
				</div><pre class="screen">chkconfig --levels 345 xenDNSmasq on
</pre></li><li><div class="para">
					To configure <code class="filename">dnsmasq</code> to restart every time <span class="application"><strong>NetworkManager</strong></span> detects a change in connectivity you can use the supplied script <code class="command">nm-dnsmasq</code>.
				</div><div class="itemizedlist"><ul><li><div class="para">
							Copy the <code class="filename">nm-dnsmasq</code> script to <code class="filename">/etc/NetworkManager/dispatcher.d/</code>
						</div></li><li><div class="para">
							The <span class="application"><strong>NetworkManager</strong></span> dispatcher will execute the script (in alphabetical order if you have other scripts in the same directory) every time there is a change in connectivity
						</div></li></ul></div></li><li><div class="para">
					<code class="filename">dnsmasq</code> will also detect changes in your <code class="filename">/etc/resolv.conf</code> and automatically reload them (that is, if you start up a VPN session for example).
				</div></li><li><div class="para">
					Both the <code class="filename">nm-dnsmasq</code> and <code class="filename">xenDNSmasq</code> script will also set up NAT if you have your virtualized guests on a hidden network to allow them access to the public network.
				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Guide-Xen_networking.html"><strong>Prev</strong>ChapterÂ 9.Â Xen networking</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Guide-Xen_Para_virtualized_Drivers.html"><strong>Next</strong>ChapterÂ 10.Â Xen Para-virtualized Drivers</a></li></ul></body></html>